On Jan 15, 2014, at 10:56 AM, Darren Pilgrim <na...@bitfreak.org> wrote:
> On 1/15/2014 10:14 AM, Franck Martin wrote: >> >> On Jan 15, 2014, at 10:05 AM, Darren Pilgrim <na...@bitfreak.org >> <mailto:na...@bitfreak.org>> >> wrote: >> >>> On 1/14/2014 4:06 PM, Brandon Applegate wrote: >>>> Just saw this in a message tonight. No idea if this is a transient error >>>> or not. >>>> >>>> --- >>>> host gmail-smtp-in.l.google.com <http://gmail-smtp-in.l.google.com> >>>> [gmail-smtp-in.l.google.com >>>> <http://gmail-smtp-in.l.google.com>][2607:f8b0:4002:c01::1a] >>>> said: 550-5.7.1 [2607:ff70:11::11] Our system has detected that this >>>> message does not 550-5.7.1 meet IPv6 sending guidelines regarding PTR >>>> records and authentication 550-5.7.1 . Please review 550-5.7.1 >>>> https://support.google.com/mail/?p=ipv6_authentication_error >>>> [support.google.com <http://support.google.com>] for more 550 >>>> 5.7.1 information. t26si2290895yhl.255 - gsmtp (in reply to end of >>>> DATA >>>> command) >>> >>> I saw a number of these as well but in my case the bracketed IP >>> addresses were malformed. For example: >>> >>> host gmail-smtp-in.l.google.com >>> <http://gmail-smtp-in.l.google.com>[2607:f8b0:4002:c01::1a] said: >>> 550-5.7.1 [2607:fc50:1000:1f00::2 16] Our system has detected >>> that this 550-5.7.1 message does not meet IPv6 sending guidelines... >>> >> >> https://support.google.com/mail/answer/81126?hl=en#authentication > > My point was that Google told me it rejected "2607:fc50:1000:1f00::2 16". > In this case, 2607:fc50:1000:1f00::2 is the correct address, but it appeared > (to me) that Google's data was somehow corrupt. > > I'm pretty sure the IPv6 address format doesn't allow spaces. ;) > Ah yes, the confusion with the separator between IP and ports. IPv4:port IPv6.port That gets a lot of regex confused...
signature.asc
Description: Message signed with OpenPGP using GPGMail