I have a category with a ‘Custom incoming email address’ set – [CATEGORY]@forum.tasat.org
When I email directly from Gmail to the address, messages are processed as expected and land in the category.
mail-receiver logs on success:
Oct 30 05:26:43 forum-mail-receiver postfix/smtpd[76028]: connect from mail-ot1-f46.google.com[209.85.210.46]
Oct 30 05:26:43 forum-mail-receiver postfix/smtpd[76028]: B5B78309A1E: client=mail-ot1-f46.google.com[209.85.210.46]
Oct 30 05:26:43 forum-mail-receiver postfix/cleanup[76035]: B5B78309A1E: message-id=<CAA0dvufnp4EsAjp9XxjjirzOvocEZn9qO1bbB2h+RhC-6GZP2w@mail.gmail.com>
Oct 30 05:26:43 forum-mail-receiver postfix/qmgr[98]: B5B78309A1E: from=<[NAME]@gmail.com>, size=3056, nrcpt=1 (queue active)
Oct 30 05:26:43 forum-mail-receiver postfix/smtpd[76028]: disconnect from mail-ot1-f46.google.com[209.85.210.46] ehlo=1 mail=1 rcpt=1 bdat=1 quit=1 commands=5
<23>Oct 30 05:26:43 receive-mail[76037]: Recipient: [CATEGORY]@forum.tasat.orgOct 30 05:26:44 forum-mail-receiver postfix/pipe[76036]: B5B78309A1E: to=<[CATEGORY]@forum.tasat.org>, relay=discourse, delay=0.57, delays=0.23/0.02/0/0.32, dsn=2.0.0, status=sent (delivered via discourse service)
Oct 30 05:26:44 forum-mail-receiver postfix/qmgr[98]: B5B78309A1E: removed
But when I submit a message to [CATEGORY]@forum.tasat.org, with identical contents, from a contact form at our landing page on carrd.co, it is not processed.
mail-receiver logs on failure:
Oct 30 06:47:20 forum-mail-receiver postfix/smtpd[76057]: connect from a69-230.smtp-out.amazonses.com[54.240.69.230]
Oct 30 06:47:20 forum-mail-receiver postfix/smtpd[76057]: lost connection after EHLO from a69-230.smtp-out.amazonses.com[54.240.69.230]
Oct 30 06:47:20 forum-mail-receiver postfix/smtpd[76057]: disconnect from a69-230.smtp-out.amazonses.com[54.240.69.230] ehlo=1 commands=1
Apparently the EHLO command is used to “Identify the domain name of the sending host to SMTP”.
I don’t know where to go with this. What would cause EHLO to fail? Do I have to whitelist SES or something…?
EHLO likely didn’t fail; postfix is saying that the sending end sent an EHLO and then dropped the connection. Something like this:
[baron ~]$ telnet forum.tasat.org 25
Trying 64.176.213.39...
Connected to forum.tasat.org.
Escape character is '^]'.
220 ESMTP server
EHLO baron
250-forum-mail-receiver.localdomain
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DSN
250 CHUNKING
^]
telnet> quit
(you’ll probably see a similar message in your logs referencing my IP)
This is a problem on SES’s end. I’d advise watching the traffic coming in on port 25 to see if there’s any indication why it dropped, or check SES to see if it has any logs.
Thanks supermathie – I don’t have access to carrd.co’s SES logs, but I have port 25 logs from another failed attempt. (Wish I knew how to interpret.) Anything jump out at you here…?
SES failure - Discourse mail-receiver log
Oct 30 16:50:11 forum-mail-receiver postfix/anvil[76091]: statistics: max connection count 1 for (smtp:159.203.42.156) at Oct 30 16:46:35
Oct 30 16:50:11 forum-mail-receiver postfix/anvil[76091]: statistics: max cache size 1 at Oct 30 16:46:35
Oct 30 17:49:01 forum-mail-receiver postfix/smtpd[76093]: connect from a69-230.smtp-out.amazonses.com[54.240.69.230]
Oct 30 17:49:01 forum-mail-receiver postfix/smtpd[76093]: lost connection after EHLO from a69-230.smtp-out.amazonses.com[54.240.69.230]
Oct 30 17:49:01 forum-mail-receiver postfix/smtpd[76093]: disconnect from a69-230.smtp-out.amazonses.com[54.240.69.230] ehlo=1 commands=1
root@forum:/var/discourse#
Much appreciated! I’ve asked carrd.co support to check logs, but they’re apparently based in a neighboring solar system. It may be a while before I have more info.
Well, I didn’t get any supporting information from carrd.co except they claimed to use “opportunitistic TLS” that should fall back to an unencrypted connection.
The one mail server health test that I wasn’t passing was the SMTP banner didn’t match the domain provided by the reverse DNS PTR record. Elsewhere on meta I turned up the idea of adding to mail-receiver.yml under env: