Title Add PTR for IPv6
Priority critical Status chatting
Superseder Nosy List Alex.Willmer, SilentGhost, izak, loewis, mmangoba, python_ss, r.david.murray, roche, ztane
Assigned To mmangoba Topics

Created on 2015-05-22.19:14:21 by loewis, last changed 2016-04-05.19:48:26 by r.david.murray.

msg2969 (view) Author: loewis Date: 2015-05-22.19:14:20
Please add a reverse DNS mapping for  2a01:4f8:131:2480::3 pointing to Apparently, otherwise email is considered as spam; see issue562
msg3025 (view) Author: SilentGhost Date: 2016-04-01.16:54:43
This is the mailer daemon response when trying to post a review on Rietveld with comments from Ralf Hildebrant. I've left only one error, but they're all nearly identical bar google's host and IP.

> Hi,
> Below is the automatic reply I got when attempting to send a Rietvel review.
> They seem to not like IPv6 PTR records and authentication.

I'm intrigued, since doesn't seem to have an
AAAA record at all

$ host -t AAAA has no AAAA record

Yet it seems to have IPv6 connectivity (which takes precedence for

A solution could be:

* enter AAAA and reverse records
* disable ipv6 for email delivery

Unfortunately I'm not the admin for

> Cheers,
> SilentGhost
> ----- Start Forwarded Message -----
> Sent: Thu, 31 Mar 2016 21:15:08 +0200 (CEST)
> From: (Mail Delivery System)
> To: ghost.adh
> Subject: Undelivered Mail Returned to Sender
> This is the mail system at host
> I'm sorry to have to inform you that your message could not
> be delivered to one or more recipients. It's attached below.
> For further assistance, please send mail to postmaster.
> If you do so, please include this problem report. You can
> delete your own text from the attached returned message.
>                    The mail system
> <>: host[2a00:1450:400c:c02::1b]
>     said: 550-5.7.1 [2a01:4f8:131:2480::3] Our system has detected that this
>     message does 550-5.7.1 not meet IPv6 sending guidelines regarding PTR
>     records and 550-5.7.1 authentication. Please review 550-5.7.1
> for more
> 550
>     5.7.1 information. bj8si10122183wjc.170 - gsmtp (in reply to end of DATA
>     command)
msg3028 (view) Author: mmangoba Date: 2016-04-05.06:47:48
Disabled IPv6 for now, Roché at Upfront will work on PTR.
msg3029 (view) Author: SilentGhost Date: 2016-04-05.16:40:20
I had an exact same mailer daemon reply about an hour after your message. So, perhaps disabling IPv6 alone didn't help.
msg3030 (view) Author: r.david.murray Date: 2016-04-05.19:48:26
The disabling of ipv6 reported by mmangoba does not appear to have been effective.  On the advice of p@trick, I added 'inet_protocols=ipv4' to the postfix config and restarted (around 15:28 Eastern) and that seems to have worked.  Serhiy was able to get a nosy email from the test tracker issue, at least.  No idea yet if rietveld emails are back to "just" being spam or are still blocked.
Date User Action Args
2016-04-05 19:48:26r.david.murraysetnosy: + r.david.murray
messages: + msg3030
2016-04-05 16:40:20SilentGhostsetmessages: + msg3029
2016-04-05 06:47:49mmangobasetassignedto: python_ss -> mmangoba
messages: + msg3028
nosy: + mmangoba
2016-04-01 16:54:44SilentGhostsetnosy: + SilentGhost
messages: + msg3025
2016-03-12 12:32:30Alex.Willmersetnosy: + Alex.Willmer
2015-07-30 03:36:18geosimsetstatus: chatting
messages: - msg2971
2015-07-30 03:35:44geosimsetstatus: chatting -> (no value)
assignedto: izak -> python_ss
nosy: + python_ss
2015-07-30 03:34:09geosimsetmessages: - msg2972
2015-07-30 03:33:26geosimsetmessages: - msg2975
2015-05-31 06:30:44ztanesetpriority: urgent -> critical
nosy: + ztane
messages: + msg2975
2015-05-26 08:07:48izaksetmessages: + msg2972
2015-05-26 07:46:12izaksetstatus: unread -> chatting
messages: + msg2971
2015-05-22 19:14:21loewiscreate