I guess this was the easy solution within the time/budget the consultant had. Hopefully you pointed to him to the various documentation at M3AAWG on email deliverability so the next time he is better prepared and can use these sets of skills to differentiate himself from his competition ;)
On Mon, Oct 12, 2015 at 4:01 AM, Frank Bulk <frnk...@iname.com> wrote: > The consultant ended up disabling IPv6 at the customer for two stated > reasons: > > a) Speed test sub-performed > > b) email delivery to gmail > > He also said there were some other strange things happening. > > > > Frank > > > > *From:* Franck Martin [mailto:fmar...@linkedin.com] > *Sent:* Thursday, October 08, 2015 1:10 PM > *To:* Frank Bulk <frnk...@iname.com> > *Cc:* n...@flhsi.com; mailop <mailop@mailop.org> > *Subject:* Re: [mailop] Strange Gmail IPv6 rejects? > > > > If you do email over IPv6, all your emails must be authenticated (SPF or > DKIM) and with a sending IP with a rDNS entry (M3AAWG recommendation > implemented by the big emailers). Otherwise you will feel the pain very > quickly. See other thread on gov't MX records. > > > > On Thu, Oct 8, 2015 at 9:36 AM, Frank Bulk <frnk...@iname.com> wrote: > > Interesting you mention that. Yesterday, for the first time, a part-time > IT consultant (who serves customers in our area) asked about PTRs as some > of his clients (who are now getting an IPv6 address from us) are having > email delivery issues to Gmail.. Our IPv6 rollout is starting to get > noticed! > > > > Frank > > > > *From:* mailop [mailto:mailop-boun...@mailop.org] *On Behalf Of *Nick > Olsen > *Sent:* Thursday, October 08, 2015 10:14 AM > *To:* Hugo Slabbert <hslabb...@stargate.ca> > > > *Cc:* mailop@mailop.org > *Subject:* Re: [mailop] Strange Gmail IPv6 rejects? > > > > Hugo, Thanks for the reply. > > > > This one's solved. > > > There's an ATT DSL modem on-site that is used for OOB. Someone had > interfaced it with the internal switch. And the server got an IPv6 auto > discovery address. So it Really had an IPv6 address. And it really was > sending mail outbound with it. What is it, Monday? > > > > Nick Olsen > Network Operations > > (855) FLSPEED x106 > > > ------------------------------ > > *From*: "Hugo Slabbert" <hslabb...@stargate.ca> > *Sent*: Thursday, October 08, 2015 11:11 AM > *To*: "Nick Olsen" <n...@flhsi.com> > *Cc*: mailop@mailop.org > *Subject*: Re: [mailop] Strange Gmail IPv6 rejects? > > > > That's a decent chunk of redacted going on there... > > What's in the smtp path after the message leaves mail.redacted.com? Does > mail.redacted.com relay out directly? Is it configured to smarthost > through something else? > > >Further more, The "From" address below (The 2602:306 one) isn't even in > >our allocation space. But actually in ATT AS7018's allocation. > > Something to consider about that: > > $ whois 2602:306:2554:63c9:91c2:5c8a:ae39:ed80 | grep -i netname > NetName: ATT-6RD > > Not sure exactly how that changes the picture for you, but the fact that > 6RD is involved (at least if AT&T is accurate in that netname and set aside > a whole /24 for 6RD) might change the picture a bit... > > -- > Hugo > > On Thu 2015-Oct-08 10:20:02 -0400, Nick Olsen <n...@flhsi.com> wrote: > > > > > > Greetings all, Please see below. Our parent office is having trouble > >sending to all gmail accounts. They all get rejected with the below > >message. The strange part is, We don't have IPv6 enabled on the customers > >exchange server. Nor on their router. Further more, The "From" address > >below (The 2602:306 one) isn't even in our allocation space. But actually > >in ATT AS7018's allocation. I'm not sure how google is seeing that as the > >source address on this SMTP connection. The below email was sent from OWA. > >Which explains the local fe80 IPv6 address. But still once again, Not the > >2602:306 address in the SMTP response from google. Anyone have any > insight? > > Diagnostic information for administrators: redac...@gmail.com > >mx.google.com #550-5.7.1 [2602:306:2554:63c9:91c2:5c8a:ae39:ed80] Our > >system has detected that 550-5.7.1 this message does not meet IPv6 sending > >guidelines regarding PTR 550-5.7.1 records and authentication. Please > >review 550-5.7.1 > >https://support.google.com/mail/?p=ipv6_authentication_error for more 550 > >5.7.1 information. y19si303834ywd.40 - gsmtp ## Original message headers: > >Received: from mail.redacted.com ([fe80::91c2:5c8a:ae39:ed80]) by > >mail.redacted.com ([fe80::91c2:5c8a:ae39:ed80%13]) with mapi; Thu, 8 Oct > >2015 10:01:50 -0400 From: Krisi <redac...@redacted.com> To: > >"redac...@gmail.com" <redac...@gmail.com> Date: Thu, 8 Oct 2015 10:01:49 > >-0400 Subject: TEST Thread-Topic: TEST Thread-Index: > >AQHRAdHgIYTSkNTvA0ip9Ycg6Q8Mrg== Message-ID: > ><D20532431BB21F488674918C8B04A6BA02FE45B7EA45@SRV.lawyers.local> > >Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: > >X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; > >charset="us-ascii" Content-Transfer-Encoding: quoted-printable > >MIME-Version: 1.0 > > > > Nick Olsen > >Network Operations (855) FLSPEED x106 > > > > > > > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > http://chilli.nosignal.org/mailman/listinfo/mailop > > >
_______________________________________________ mailop mailing list mailop@mailop.org http://chilli.nosignal.org/mailman/listinfo/mailop
