Hey!

I see that this is your first PR. That is great! Welcome!

Symfony has a contribution guide which I suggest you to read.

In short:

• Always add tests
• Keep backward compatibility (see https://symfony.com/bc).
• Bug fixes must be submitted against the lowest maintained branch where they apply (see https://symfony.com/releases)
• Features and deprecations must be submitted against the 7.1 branch.

Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change.

When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor!
If this PR is merged in a lower version branch, it will be merged up to all maintained branches within a few days.

I am going to sit back now and wait for the reviews.

Cheers!

Carsonbot

Can you please add a test case? Thanks

Why not using àWhy don't you using smtps` as scheme instead? Can you explain?

Why not using àWhy don't you using smtps` as scheme instead? Can you explain?

Our client has an incorrectly configured mail server. On swiftmailer this did not cause problems, but when switching to symfonymailer the connection stopped working

I am not sure we want to work around wrong configured mail servers 🤔

cc @fabpot

I am not sure we want to work around wrong configured mail servers 🤔

cc @fabpot

This isn't really a mistake. On servers you can configure an arbitrary port for smtp. Even 465, although it is the default for smtps

This might break existing client that forgot to add the final "s" to their scheme so I'm not sure I would do it this way.
Instead, we could add a tls option - maybe by tweaking #53621
Closing for this reason, let's continue on the linked PR.