Re: [mailop] [E] $GOOG - IPv6 aside
Luis E. Muñoz via mailop wrote on 2022-04-15 18:49: ... Someone once said that IPv6 was an opportunity to introduce a good set of requirements into the email ecosystem (forgot who/where, and I'm paraphrasing). ... that's what i was trying to get at here: https://circleid.com/posts/20110607_two_stage_filtering_for_ipv6_electronic_mail -- P Vixie ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] [E] $GOOG - IPv6 aside
lem wrote: > > You're not wrong. Depends on email volume level and server config. > > They're just so sensitive to reputation for IPv6 sends, though. Don't > > even try without SPF and DKIM, and even then, get ready for some > > possible pain. > > For well managed mail servers, supporting well managed mailing lists I see no > practical difference between address families. I have visibility over a few > boxes sending a few hundred thousand messages per day. I see no reason to disagree with you. :) The difference between your scenario and mine (and the scenarios of people struggling) is that you're sending much more mail than me (and the people struggling), I think. You might be at the low end compared to how much mail Gmail sends, but you're in rather a good spot as having enough email to send to build up a good sending reputation. (Of course, it's not ONLY about volume...but that is indeed part of it.) Cheers, Al -- Al Iverson / Deliverability blogging at www.spamresource.com Subscribe to the weekly newsletter at wombatmail.com/sr.cgi DNS Tools at xnnd.com / (312) 725-0130 / Chicago (Central Time) ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] [E] $GOOG - IPv6 aside
On 15 Apr 2022, at 12:02, Al Iverson via mailop wrote: > On Fri, Apr 15, 2022 at 10:36 AM Grant Taylor via mailop > wrote: >> >> On 4/15/22 8:24 AM, Al Iverson via mailop wrote: >>> Don't send to Gmail over IPv6. >> >> Drive by comment. >> >> It is possible to send to Google via IPv6. My personal / small / >> bespoke server sends to my Google hosted work address all the time over >> IPv6. > > You're not wrong. Depends on email volume level and server config. > They're just so sensitive to reputation for IPv6 sends, though. Don't > even try without SPF and DKIM, and even then, get ready for some > possible pain. For well managed mail servers, supporting well managed mailing lists I see no practical difference between address families. I have visibility over a few boxes sending a few hundred thousand messages per day. They are all dual stack and provisioned on a cloud provider (gasp!). The two deliverability issues they've had in the last two years have been related to sending to Microsoft, over IPv4. I also see similar boxes, used mostly for one-to-one and small scale mailing lists in the same scenario, with the same results. Of course, this is a small number of samples and perhaps even anecdotal, but these kinds of absolute pieces of advice are perhaps not for everyone. Someone once said that IPv6 was an opportunity to introduce a good set of requirements into the email ecosystem (forgot who/where, and I'm paraphrasing). With the potential to send each individual email message over the lifetime of a mailing list from a unique IPv6 address, I think this is a good justification for this. Best regards -lem ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] [E] $GOOG - IPv6 aside
On Fri, Apr 15, 2022 at 10:36 AM Grant Taylor via mailop wrote: > > On 4/15/22 8:24 AM, Al Iverson via mailop wrote: > > Don't send to Gmail over IPv6. > > Drive by comment. > > It is possible to send to Google via IPv6. My personal / small / > bespoke server sends to my Google hosted work address all the time over > IPv6. You're not wrong. Depends on email volume level and server config. They're just so sensitive to reputation for IPv6 sends, though. Don't even try without SPF and DKIM, and even then, get ready for some possible pain. I think Gmail could be worried that with IPv6 being so broad that somebody could do a spam run targeted at them with each individual message coming from a different IPv6 IP. So I think they are way quicker to drop the hammer and block an IPv6 IP at very low volumes versus an IPv4 IP. (That's a bit of a generalization there, of course.) When I set up a new VPS at a provider, I immediately disable the IPv6 interface and IP. I have never had any sort of broad blocking issues at Gmail with my newest servers. Occasionally I get a content block or trigger something weird-- I accidentally stumbled across a bug in my mailing list manager a couple of weeks ago that would sometimes result in having two message-ID headers and that caused Gmail blocking. But I was able to troubleshoot and fix it. Cheers, Al -- Al Iverson / Deliverability blogging at www.spamresource.com Subscribe to the weekly newsletter at wombatmail.com/sr.cgi DNS Tools at xnnd.com / (312) 725-0130 / Chicago (Central Time) ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] [E] $GOOG - IPv6 aside
On 4/15/22 8:24 AM, Al Iverson via mailop wrote: Don't send to Gmail over IPv6. Drive by comment. It is possible to send to Google via IPv6. My personal / small / bespoke server sends to my Google hosted work address all the time over IPv6. -- Grant. . . . unix || die smime.p7s Description: S/MIME Cryptographic Signature ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
