Gmail: this message does not meet IPv6 sending guidelines regarding PTR records

Zeno McDohl · 02-01-2017, 09:29 PM

I am trying to email myself (on Gmail) a Nagios alerts and it's rejecting all mail:

Code:

Our system has detected that this
<<< 550-5.7.1 message does not meet IPv6 sending guidelines regarding PTR records
<<< 550-5.7.1 and authentication.

The bounceback:

Quote:

From: Mail Delivery Subsystem <MAILER-DAEMON>
Message-Id: <201702020221.v122LqeY025127@vps25653685.vm.ramnoc.net>
To: <root@biyg.org>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="v122LqeY025127.1486002112/vps25653685.vm.ramnoc.net"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)

This is a MIME-encapsulated message

--v122LqeY025127.1486002112/vps25653685.vm.ramnoc.net

The original message was received at Wed, 1 Feb 2017 21:21:51 -0500
from localhost.localdomain [127.0.0.1]

----- The following addresses had permanent fatal errors -----
<me@gmail.com>
(reason: 550-5.7.1 [2605:8900:1000:1001:5:0:27:2] Our system has detected that this)

----- Transcript of session follows -----
... while talking to gmail-smtp-in.l.google.com.:
>>> DATA
<<< 550-5.7.1 [2605:8900:1000:1001:5:0:27:2] Our system has detected that this
<<< 550-5.7.1 message does not meet IPv6 sending guidelines regarding PTR records
<<< 550-5.7.1 and authentication. Please review
<<< 550-5.7.1 https://support.google.com/mail/?p=IPv6AuthError for more information
<<< 550 5.7.1 . v125si5903565ywf.358 - gsmtp
554 5.0.0 Service unavailable

--v122LqeY025127.1486002112/vps25653685.vm.ramnoc.net
Content-Type: message/delivery-status

Reporting-MTA: dns; vps25653685.vm.ramnoc.net
Received-From-MTA: DNS; localhost.localdomain
Arrival-Date: Wed, 1 Feb 2017 21:21:51 -0500

Final-Recipient: RFC822; me@gmail.com
Action: failed
Status: 5.7.1
Remote-MTA: DNS; gmail-smtp-in.l.google.com
Diagnostic-Code: SMTP; 550-5.7.1 [2605:8900:1000:1001:5:0:27:2] Our system has detected that this
Last-Attempt-Date: Wed, 1 Feb 2017 21:21:52 -0500

--v122LqeY025127.1486002112/vps25653685.vm.ramnoc.net
Content-Type: message/rfc822

Return-Path: <root@biyg.org>
Received: from biyg.org (localhost.localdomain [127.0.0.1])
by vps25653685.vm.ramnoc.net (8.13.8/8.13.8) with ESMTP id v122LpeY025125
for <me@gmail.com>; Wed, 1 Feb 2017 21:21:51 -0500
Received: (from root@localhost)
by biyg.org (8.13.8/8.13.8/Submit) id v122Lpou025124
for me@gmail.com; Wed, 1 Feb 2017 21:21:51 -0500
Date: Wed, 1 Feb 2017 21:21:51 -0500
From: root <root@biyg.org>
Message-Id: <201702020221.v122Lpou025124@biyg.org>
Subject: test15

But my domain (biyg.org) does have AAAA record:

http://mxtoolbox.com/SuperTool.aspx?...g&run=toolpage

Code:

2605:8900:1000:1001:5:0:27:2

And my hostname is:

Code:

biyg.org

Which matches what Google saw.

What am I missing?

frankbell · 02-02-2017, 10:11 PM

I've never encountered this, but I found a link that might help: http://serverfault.com/questions/732...ing-ptr-record

JJJCR · 02-03-2017, 05:06 AM

The easiest solution is to switch postfix to ipv4 only. Add the following line in the postfix main.cf file and restart postfix:

inet_protocols=ipv4

If you like to use ipv6, then you will have to check 2 things:

1) is there a IPv6 recrd (AAAA) for the hostname "casrv02.myserver.com" in the zone "myserver.com" that points to the IPv6 address of your server?

2) Does your IPv6 address has a reverse dns record that points back to the hostname "casrv02.myserver.com". The reverse recod for the IP has most likely to be set in the ovh controlpanel of the server / vm and not in ispconfig.

Above text from this link: https://www.howtoforge.com/community...roblems.64675/

If IPV6 is not a requirement, stick with IPv4 first.