One of our tools has the option to get results by email. I'm trying to use python's smtplib to send mail. I can connect to tools-mail by smtp and send without errors, but no mail gets delivered.
Version: unspecified
Severity: blocker
One of our tools has the option to get results by email. I'm trying to use python's smtplib to send mail. I can connect to tools-mail by smtp and send without errors, but no mail gets delivered.
Version: unspecified
Severity: blocker
Some more context from IRC:
<Coren> 2013-07-15 10:23:22 1Uyfw9-00075n-O8 ** junk-mailbox@gmx.de |
R=dnslookup T=remote_smtp: SMTP error from remote mail server after |
initial connection: host mx01.gmx.net [213.165.67.115]: 554-gmx.net |
(mxgmx109) Nemesis ESMTP Service not available\n554-No SMTP |
service\n554 invalid DNS PTR resource record [13:26] |
<Coren> JohannesK_WMDE: Your server don't like ours because it doesn't have a |
reverse. That can be arranged. |
We now have a proper reverse; which will alleviate that specific problem. We don't yet have a proper SPF entry, but that remains pending on some decisions from legal.
This seems to have come back:
scfc@tools-mail:~$ sudo exim -v -M 1WSzlb-0004XZ-RS |
delivering 1WSzlb-0004XZ-RS |
LOG: MAIN |
Unfrozen by forced delivery |
Connecting to mx-ha03.web.de [213.165.67.104]:25 ... connected |
SMTP<< 554-web.de (mxweb006) Nemesis ESMTP Service not available |
554-No SMTP service |
554 invalid DNS PTR resource record |
SMTP>> QUIT |
LOG: MAIN |
** [redacted] <[redacted]@tools.wmflabs.org> R=dnslookup T=remote_smtp: SMTP error from remote mail server after initial connection: host mx-ha03.web.de [213.165.67.104]: 554-web.de (mxweb006) Nemesis ESMTP Service not available\n554-No SMTP service\n554 invalid DNS PTR resource record |
LOG: MAIN |
Frozen (delivery error message) |
scfc@tools-mail:~$ |
Change 121416 had a related patch set uploaded by Tim Landscheidt:
Add temporary PTR record for mail.tools.wmflabs.org
I looked through some of the stuck mail, and apparently it's not only "Your job was submitted", but also some maintainers actually use that for useful information :-). So upping priority, as those maintainers currently don't get any mail.
Sadly, reverses have to be done manually because of the hinky way Openstack handles DNS.