Decide how best to send email in production #17

New Issue

3wordchant · 2021-12-08T22:47:43Z

3wordchant commented

2021-12-08 22:47:43 +00:00

Bold contention: basically all our production wordpress sites should use SMTP for outgoing email, rather than the default wordpress sendmail.

This gives us the option to use an external provider like gandi or mailgun straight out of the installation process
This is the default for cloudron and yunohost
Even if we do direct-delivery email, it'll likely be a containerised mail server that php communicates with using TCP/SMTP rather than a socket or a spool file or whatever else the fuck it usually does

If that's a 10-4 (and I'm also totally open to another philosophy here), then from #11:

the standard "how to get wordpress to send to an SMTP server cleanly", with possibly the usual two options:

Installing a wordpress SMTP plugin by default (related to #9? )

Use msmtp

Installing a plugin is maybe more "wordpressy", it's what cloudron & yunohost are doing, and it does have the advantage of being visible in the wordpress dashboard as opposed to msmtp which only lurks on the file system.

Personally slight leaning towards msmtp, nevertheless, on the basis that:

all the wordpress SMTP plugins I found heavily advertise their premium versions throughout the web press admin dashboard after installation, which could be unprofessional or expensive or both for us
msmtp it means that email configuration, like most other Co-op Cloud apps, lives in environment variables instead of in a database table
msmtp is a very easy addition to our custom php docker image

**Bold** contention: basically all our production wordpress sites should use SMTP for outgoing email, rather than the default wordpress `sendmail`. * This gives us the option to use an external provider like gandi or mailgun straight out of the installation process * This is the default for cloudron and yunohost * Even if we do direct-delivery email, it'll likely be a containerised mail server that php communicates with using TCP/SMTP rather than a socket or a spool file or whatever else the fuck it usually does If that's a 10-4 (and I'm also totally open to another philosophy here), then from #11: > the standard "how to get wordpress to send to an SMTP server cleanly", with possibly the usual two options: > > 1. Installing a wordpress SMTP plugin by default (related to #9? ) > 2. Use msmtp Installing a plugin is maybe more "wordpressy", it's what cloudron & yunohost are doing, and it does have the advantage of being visible in the wordpress dashboard as opposed to msmtp which only lurks on the file system. Personally slight leaning towards msmtp, nevertheless, on the basis that: - all the wordpress SMTP plugins I found heavily advertise their premium versions throughout the web press admin dashboard after installation, which could be unprofessional or expensive or both for us - msmtp it means that email configuration, like most other Co-op Cloud apps, lives in environment variables instead of in a database table - msmtp is a very easy addition to our custom php docker image

3wordchant added the

enhancement

label 2021-12-08 22:47:43 +00:00

3wordchant commented

2021-12-20 23:00:13 +00:00

Ran into horrific issues trying to set up "WP SMTP" with our mail.autonomic.zone instance -- strange errors about IPv6 from swaks, "Connection error" from the plugin.

We ended up using an externally-hosted mailbox in the meantime.

I still think msmtp is narrowly the best option, and will make time to try it out ASAP.

Ran into horrific issues trying to set up "WP SMTP" with our mail.autonomic.zone instance -- strange errors about IPv6 from `swaks`, "Connection error" from the plugin. We ended up using an externally-hosted mailbox in the meantime. I still think msmtp is narrowly the best option, and will make time to try it out ASAP.

This repo is archived. You cannot comment on issues.