Ability to set ssl/tls for smtp in mail settings with environment variable

[EpocSquadron]

Description

We can currently set the smtp credentials, server and port all with environment variables. However, it appears the dropdown to select ssl vs tls for the connection is not able to be set to an environment variable. We are currently using mailtrap.io for testing environments and a proper transactional email service in production (although not one of the common ones). Mailtrap requires the connection be over tls (mail settings test fails when set to ssl), while production requires ssl. This wouldn't be quite such a problem except that we are enforcing project config (and have admin changes off in all non-local environments), and this setting is tracked in that.

I'm hesitant to override the transport in config/app.php as in #5975 as it seems kind of invasive, especially seeing as all of the other fields in the smtp settings are configurable with environment variables. Is it possible to add support for configuring this in a way that project config is compatible with?

[nordentwickler]

Completely agree with this. We are using laradock with maildev for our dev environment and the most small websites still user smtp with tls for sending emails. Maildev breaks with tls setting on - controlling this via environment variables would be great.

[Mosnar]

Related: #6403

[ryanirelan]

This takes on new meaning with Nitro's support for MailHog. MailHog doesn't support authentication nor encryption but those cannot be set via environment variables.

See docs:

Transport Type: SMTP
Host Name: mailhog.service.nitro
Port: 1025
Use Authentication: Unchecked (default)
Encryption Method: None (default)
Timeout: 10 (default)

[Antimated]

This would be a very nice addition indeed. We use mailhog locally which does not support authentication nor encryption (lika @ryanirelan) stated. For our staging and production environments we use postmark which requires you to use TLS encryption. Very annoying that we constantly have to switch between no encryption and TLS when we are testing locally vs staging.

[peteeveleigh]

Whilst I agree you should be able to set ALL mail settings via environment vars there is another way to get around this.
You can configure the mail transport set up in config/app.php.
This can then use your environment variables to populate any of the values.

In the components section of your app.php file you can do something like

'mailer' => function() {
            // Get the stored email settings
            $settings = App::mailSettings();

            // Override the transport adapter class
            $settings->transportType = PostmarkAdapter::class;

            // Override the transport adapter settings
            $settings->transportSettings = [
                'token' => getenv('POSTMARK_API_TOKEN'),
                'messageStream' => getenv('POSTMARK_STREAM_ID') ?? ''
            ];

            // Create a Mailer component config with these settings
            $config = App::mailerConfig($settings);
            return Craft::createObject($config);
        }

[brandonkelly]

This is now resolved for the next Craft 3 release 🚀

See details at #10111

[michaelij]

Hi Brandon,

Also having issues selecting any environment variables in the Encryption Method dropdown in particular. The dropdown seems to show only the three preset options, manually typing the env variable does not work either.

[brandonkelly]

It will only show environment variables that match the available option values (none, ssl, or tls). Should probably make that clearer…

[mikewink]

Works Brandon! Thank you very much for clarifying. 🏆

[brandonkelly]

Just released 3.7.23 which should make this more clear. There is now a tip below the field that says:

This can be set to an environment variable with a value of one of the selectable option values.

And the dropdown now shows each of the native option values beside their labels:

The “Use authentication” setting also shows a tip with the supported environment varialeble values:

[darylknight]

I just came here to post a bug and found this discussion too. I had an env variable set to "SSL" and it didn't show up in the list, so it just looked like "Use Authentication" was bugged and not looking for ENV variables. Now that I've changed the value to "ssl", it shows up in the list.