https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions en a blog about Debian and self-hosting Wed, 04 Jan 2017 21:29:00 +0000 PluXml https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1483565367-1 https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1483565367-1 Je viens de rencontrer le problème! Merci beaucoup du coup de main! Big Up pour utiliser PluXml ;-) Wed, 04 Jan 2017 21:29:00 +0000 greg https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1461877976-1 https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1461877976-1 Merci pour cette info, toujours au top Tanguy ! ;) ++ Thu, 28 Apr 2016 21:12:00 +0000 mario_26 https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1453557878-1 https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1453557878-1 For me it works perfectly. Sat, 23 Jan 2016 14:04:00 +0000 Legion https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1450466917-1 https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1450466917-1 The solution works with Mac OS X servers, with one modification: chroot has to be explicitly disabled in the service definition line in master.cf, i.e., smtp4 unix - - n - - smtp -o inet_protocols=ipv4 Fri, 18 Dec 2015 19:28:00 +0000 Robb Allan https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1448627465-1 https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1448627465-1 There is a slight problem with this rule though, it's when the recipents domain names uses google for their MX, under their own domain name (I stumbled on the case earlier. so rather than creating a rule for each domain, i went to force all postfix trafic though ipv4 by changing the line : inet_protocols = all to inet_protocols = ipv4 in /etc/postfix/main.cf (ubuntu 15.04, postfix 2.11.3-1ubuntu2) Fri, 27 Nov 2015 12:31:00 +0000 eric https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1446169509-1 https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1446169509-1 Thanks for this writeup! For some reason I'd been able to send mail to gmail for 2+ years after you wrote this, but I just hit it for the first time today. Your instructions worked perfectly. Fri, 30 Oct 2015 01:45:00 +0000 Waltman https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1445856715-1 https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1445856715-1 Seems that google has changed its IPv6 PTR policy, right? Iam noow able to send mail from a server with IPv6 with no propper IPv6 PTR record and I don't get the previous message anymore. Can anyone confirm? Mon, 26 Oct 2015 10:51:00 +0000 Huub Knops https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1440475506-1 https://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions/#c1440475506-1 I just had to disable IPv6 for a similar but different gmail issue. Gmail was bouncing mail as spam. with a different error. Now the underlying cause might be the same (no reverse lookup for ipv6 or no SPF record or whatever) however the actual error was NOT that, it was " Our system has 550-5.7.1 detected that this message is likely unsolicited mail. To reduce the 550-5.7.1 amount of spam sent to Gmail, this message has been blocked. Please 550-5.7.1 visit 550 5.7.1" So, what's up with that? I should have got "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" but did not. Tue, 25 Aug 2015 04:05:00 +0000 justin