OVH Community, your new community space.

IPv6 issue on ISPConfig3


Tz-OVH
23-01-2014, 08:43
Thanks for your help Myatu, I've gone and made a few changes, below:



http://demo.ovh.eu/en/fd203b7720949874e4b77e41d308d90f/

Email is working now, but gmail still gave a bounce mail error, but successfully delivered it...Might try some more things, but checking if within 24hours there are still any errors left.

Myatu
22-01-2014, 23:35
There's a hint in the error link given:

- The sending IP must have a PTR record (i.e., a reverse DNS of the sending IP) and it should match the IP obtained via the forward DNS resolution of the hostname specified in the PTR record. Otherwise, mail will be marked as spam or possibly rejected.

- The sending domain should pass either SPF check or DKIM check. Otherwise, mail might be marked as spam.
To solve the first one, first create an "A" record for the IPv6 listed and then, provided the IPv6 range belongs to OVH, at OVH create a "PTR" record for said IP.

Easiest thing to do for the second one is to create an SPF / TXT record. For an awfully designed website, but with helpful information if a spend a few minutes looking:

http://www.openspf.org/

Lastly, make sure Postfix is set to only use that one IPv6 address, not "any" IPv6 address the system has.

Tz-OVH
22-01-2014, 18:51
Setup is Debian running ISPConfig3 and Postfix for email.

It's a pretty default setup, following is the DNS Zone File @ GoDaddy



http://demo.ovh.eu/en/a4c7fc4a4169e77fed167cc736716b8d/

Error that started up:
: host
gmail-smtp-in.l.google.com[2a00:1450:400c:c05::1a] said: 550-5.7.1
[2001:41XXXXXXXXXXX1] 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
https://support.google.com/mail/?p=i...tication_error for more 550
5.7.1 information. t1si7140688wjx.67 - gsmtp (in reply to end of DATA
command)
I earlier didn't have the IPv6 addy in my DNS Zone File and emails stopped completely, now by adding it at least mails are being sent/received OK with the error above happening randomly.

Any ideas?