Problems with Mailgun SMTP configuration

[gatodelcaribe]

I'm using the next text into 'plausible-conf.env' but email isn't working:

MAILER_EMAIL= email
SMTP_HOST_ADDR=smtp.mailgun.org
SMTP_HOST_PORT=465
SMTP_USER_NAME= username email
SMTP_USER_PWD= my password
SMTP_HOST_SSL_ENABLED=false
SMTP_RETRIES 5

[dimejo]

Might be related to #3299 (comment). Please try setting SMTP_HOST_SSL_ENABLED=true.

[ruslandoga]

In the meantime you can probably use HTTP API endpoint to send emails through Mailgun. See https://plausible.io/docs/self-hosting-configuration for all the MAILGUN_* options, and note that you'd need to use MAILER_ADAPTER=Bamboo.MailgunAdapter

[gatodelcaribe]

Also tested deleting others lines on env and using it on docker-compose-yml.

code on docker compose:

services:
  mail:
    image: bytemark/smtp
    restart: always
    environment:
      MAILER_ADAPTER: Bamboo.MailgunAdapter
      RELAY_HOST: smtp.mailgun.org
      MAILGUN_API_KEY: the mailgun api key
      RELAY_PORT: 465
      RELAY_USERNAME: analytics@email.gatodelcaribe.com
      RELAY_PASSWORD: password that mailgun provide me

Logs mail:

root@Plausible-analitycs:/opt/plausible# docker compose logs mail
mail_1  |     1 LOG: MAIN
mail_1  |     1   exim 4.89 daemon started: pid=1, -q30m, listening for SMTP on port 25 (IPv6 and IPv4)
mail_1  |   240 LOG: MAIN
mail_1  |   240   <= hello@plausible.local H=plausible_plausible_1.plausible_default (plausible.gatodelcaribe.com) [172.18.0.5] P=esmtp S=1826
mail_1  |   240 LOG: smtp_connection MAIN
mail_1  |   240   SMTP connection from plausible_plausible_1.plausible_default (plausible.gatodelcaribe.com) [172.18.0.5] closed by QUIT
mail_1  |   241 Exim version 4.89 uid=101 gid=101 pid=241 D=40001
mail_1  | Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
mail_1  | Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM DNSSEC Event OCSP PRDR SOCKS TCP_Fast_Open
mail_1  | Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch nis nis0 passwd
mail_1  | Authenticators: cram_md5 plaintext
mail_1  | Routers: accept dnslookup ipliteral manualroute queryprogram redirect
mail_1  | Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
mail_1  | Fixed never_users: 0
mail_1  | Configure owner: 0:0
mail_1  | Size of off_t: 8
mail_1  |   241 delivering 1qetQp-00003s-Qj
mail_1  |   241 R: smarthost for kelbingato@gmail.com
mail_1  |   242 T: remote_smtp_smarthost for kelbingato@gmail.com
mail_1  |   242 Transport port=25 replaced by host-specific port=465
mail_1  |   242 Connecting to smtp.mailgun.org [34.160.157.95]:465 ... connected

[ruslandoga]

You don't need mail container if you are not sending mail from the host. MAILER_ADAPTER and MAILGUN_* env vars would be set on plausible (which by default uses plausible-conf.env envfile) :)

[gatodelcaribe]

@ruslandoga I changed the port from "465" to "587" and now all emails working.

I saw that into the SMTP mailgun website it say: "Our servers listen on ports 25, 587, and 465 (SSL/TLS)"

[ruslandoga]

This error provides a clear path forward, we either need to add cacerts to verify smtp.mailgun.org or disable peer verification on ssl connection. The only problem is that is not possible to do with just env vars and would require a PR + patch release.

Seems like the adapter we use for SMTP doesn't allow passing a custom hostname match function, so we wouldn't be able to properly configure it.

There are some unmerged PRs that make it possible:

• Allow raw tls_options to be passed through to gen_smtp fewlinesco/bamboo_smtp#223
• Add new tls option customize_hostname_check fewlinesco/bamboo_smtp#210
• Use tls options in sockopts for ssl connection fewlinesco/bamboo_smtp#214

verify: :verify_none is still an option but probably a bad one.