Hi Alex, Yep we have been using roll up by MX since it became available and roll up by IP for all the hosted outlook vanity MX records which used to make IP warming a nightmare.
Once Yahoo is back on it's feet I'll push ours back out to 20 Cheers Dave On Fri, 6 Sep 2019 at 09:00, Alex Irimia <a...@postmastery.net> wrote: > Hi Dave, > > We don't see any "421 Max message per connection reached" errors for > servers that have max-msg-per-connection set to 20 for OATH domains. > In case you're using PowerMTA, make sure you setup MX-rollup to catch all > related domains, otherwise you might miss some and those domains might > inherit default max-msg-per-connection settings. > > Regards, > Alex Irimia > > > On Fri, Sep 6, 2019 at 9:42 AM Dave Holmes via mailop <mailop@mailop.org> > wrote: > >> For anyone still following these issues it looks like Yahoo have >> reconfigured their mail acceptance policies over night and the response >> message has changed to indicate a substantial change in the rate they >> accept mail - this may catch a few out. >> >> entered backoff mode due to "421 Max message per connection reached, >> closing transmission channel tnmpmscs" received from >> mx-eu.mail.am0.yahoodns.net >> <https://slack-redir.net/link?url=http%3A%2F%2Fmx-eu.mail.am0.yahoodns.net> >> (188.125.72.74) matching /421 .* closing transmission channel/ >> >> I have dropped our max messages per connection right down to 10 and we >> are now seeing much improved throughput. >> >> Anyone else noticed any other best practice changes we should be aware of? >> >> >> On Thu, 5 Sep 2019 at 18:21, Brotman, Alexander via mailop < >> mailop@mailop.org> wrote: >> >>> That’s changed over the years, and depends on using IPv4/IPv6 and a few >>> other details. There are also a few layers of control to make things more >>> complicated. I would imagine most ISPs are like this, hence it seems like >>> it would be easier to try to manage the number of messages per session than >>> the number of sessions. Obviously I’m not on the ESP side so maybe I just >>> don’t understand all the craziness other ISPs impose on senders that makes >>> this a difficult thing to configure. >>> >>> >>> >>> -- >>> >>> Alex Brotman >>> >>> Sr. Engineer, Anti-Abuse & Messaging Policy >>> >>> Comcast >>> >>> >>> >>> *From:* Howard F. Cunningham <howa...@macrollc.com> >>> *Sent:* Thursday, September 5, 2019 11:52 AM >>> *To:* Brotman, Alexander <alexander_brot...@cable.comcast.com> >>> *Cc:* mailop@mailop.org >>> *Subject:* [EXTERNAL] RE: [mailop] Resolving issues for several yahoo >>> domains? >>> >>> >>> >>> Alex >>> >>> >>> >>> How many connections does Comcast allow from a single source before >>> Comcast either starts limiting connections or outright blocks all >>> connections from that IP address? >>> >>> >>> >>> hc >>> >>> >>> >>> >>> >>> Howard Cunningham, MCP >>> >>> howa...@macrollc.com - personal >>> >>> For technical support, send an email to serv...@macrollc.com or call >>> 703-359-9211 (24/7) >>> >>> >>> >>> *From:* mailop [mailto:mailop-boun...@mailop.org >>> <mailop-boun...@mailop.org>] *On Behalf Of *Brotman, Alexander via >>> mailop >>> *Sent:* Thursday, September 05, 2019 11:31 AM >>> *To:* '(mailop@mailop.org)' >>> *Subject:* Re: [mailop] Resolving issues for several yahoo domains? >>> >>> >>> >>> One of the interesting things I’ve learned while interacting with ESPs >>> is that some of them will artificially restrict the number of messages per >>> session, in lieu of opening more sessions. Some of them have told me the >>> values are in the low single digits. I’ve kind of wondered the rationale >>> for that might be. Is it the idea that you want to get your messages >>> through as quickly as possible? >>> >>> >>> >>> -- >>> >>> Alex Brotman >>> >>> Sr. Engineer, Anti-Abuse & Messaging Policy >>> >>> Comcast >>> >>> >>> >>> *From:* mailop <mailop-boun...@mailop.org> *On Behalf Of *Benjamin >>> BILLON via mailop >>> *Sent:* Thursday, September 5, 2019 10:08 AM >>> *To:* mailop@mailop.org >>> *Subject:* [EXTERNAL] Re: [mailop] Resolving issues for several yahoo >>> domains? >>> >>> >>> >>> > Hate to imagine how much mail is currently trying to get into Yahoo >>> and AOL >>> >>> Same. Hate also to imagine the day (and night?) of the folks working on >>> fixing that. >>> >>> >>> >>> -- >>> *Benjamin* >>> >>> >>> >>> *From:* Dave Holmes <d...@instiller.co.uk >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=mailto:d...@instiller.co.uk>> >>> >>> *Sent:* jeudi 5 septembre 2019 15:57 >>> *To:* Benjamin BILLON <bbil...@splio.com >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=mailto:bbil...@splio.com> >>> > >>> *Cc:* mailop@mailop.org >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=mailto:mailop@mailop.org> >>> *Subject:* Re: [mailop] Resolving issues for several yahoo domains? >>> >>> >>> >>> Not the quickest or easiest to do as a lot of senders will have >>> different limits on different IP pools depending on reputation / previous >>> throughput. >>> >>> >>> >>> I've dropped in a platform wide rule to back off the mail queues when >>> the response is encountered - should do the Job. >>> >>> >>> >>> Hate to imagine how much mail is currently trying to get into Yahoo and >>> AOL >>> >>> >>> >>> On Thu, 5 Sep 2019 at 14:39, Benjamin BILLON via mailop < >>> mailop@mailop.org >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=mailto:mailop@mailop.org>> >>> wrote: >>> >>> Yes, everyone. >>> >>> Some, very few, emails are accepted. I believe their servers are >>> overloaded. I suggest everyone to back off a bit, for instance by limiting >>> the number of concurrent connections per outbound IP to ... 1. Until it >>> gets better. >>> >>> Forcing our way through is not gonna work, or help. >>> >>> >>> >>> The DNS issue seems solved now. >>> >>> >>> >>> -- >>> *Benjamin* >>> >>> >>> >>> *From:* mailop <mailop-boun...@mailop.org >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=mailto:mailop-boun...@mailop.org>> >>> *On Behalf Of *Dave Holmes via mailop >>> *Sent:* jeudi 5 septembre 2019 15:21 >>> *To:* Ewald Kessler | Webpower <ewald.kess...@webpower.nl >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=mailto:ewald.kess...@webpower.nl> >>> > >>> *Cc:* mailop <mailop@mailop.org >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=mailto:mailop@mailop.org> >>> > >>> *Subject:* Re: [mailop] Resolving issues for several yahoo domains? >>> >>> >>> >>> Were seeing large mail queues forming on our side but I think this >>> extends beyond the DNS I've not come across this message from Yahoo before. >>> >>> >>> >>> Error: "421 Service not available, closing transmission channel tnmpmscs" >>> >>> >>> >>> So whilst we have the DNS resolution (possibly cached) they are dropping >>> connections all over the place, same goes for all of their other domains. >>> >>> >>> >>> Anyone else with issues delivering after DNS resolves >>> >>> >>> >>> >>> >>> On Thu, 5 Sep 2019 at 10:31, Ewald Kessler | Webpower via mailop < >>> mailop@mailop.org >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=mailto:mailop@mailop.org>> >>> wrote: >>> >>> Yes, Oath (a.o. Yahoo, AOL) is having serious issues. Their engineers >>> are working to resolve the issues. >>> >>> >>> >>> Regards, >>> >>> Ewald >>> >>> >>> >>> On Thu, 5 Sep 2019 at 10:35, tobisworld--- via mailop <mailop@mailop.org >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=mailto:mailop@mailop.org>> >>> wrote: >>> >>> We're currently seeing several yahoo domains (ex yahoo.de >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=http://yahoo.de>) >>> cannot be >>> resolved any more in DNS. All the responsable nameservers for that >>> domain do not reply anymore. Only ns4.yahoo.com replies from time to >>> time for yahoo.de >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=http://yahoo.de> >>> but according to glue record ns4.yahoo.com is not in >>> charge for yahoo.de >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=http://yahoo.de> >>> anymore. >>> >>> anyone else seeing such problems with yahoo? >>> >>> -- >>> Cheers >>> >>> tobi >>> >>> _______________________________________________ >>> mailop mailing list >>> mailop@mailop.org >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=mailto:mailop@mailop.org> >>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop> >>> >>> >>> >>> >>> -- >>> >>> Deliverability & Abuse Management, www.webpower-group.com >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=http://www.webpower-group.com> >>> >>> ewald.kess...@webpower.nl >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=mailto:ewald.kess...@webpower.nl> >>> >>> t: +31 342 423 262 >>> >>> li: www.linkedin.com/in/ewaldkessler >>> >>> _______________________________________________ >>> mailop mailing list >>> mailop@mailop.org >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=mailto:mailop@mailop.org> >>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop> >>> >>> >>> >>> >>> -- >>> >>> >>> >>> [image: Image removed by sender. Instiller Logo] >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=https://www.instiller.co.uk> >>> >>> >>> >>> Dave Holmes >>> >>> Technical Director >>> >>> >>> >>> *d...@instiller.co.uk* >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=mailto:d...@instiller.co.uk> >>> >>> *T* 0333 939 0013 | *M* 07966 013 309 >>> >>> 1 Park Farm Barns | Packington Lane | Stonebridge | CV7 7TL >>> >>> >>> >>> >>> >>> >>> >>> Instiller is a trademark of Instiller Limited, registered in England >>> 5053657. >>> >>> >>> >>> This email contains proprietary information, some of which may be >>> legally privileged. It is for the intended recipient only. >>> If an addressing or transmission in error has misdirected this email, >>> please notify the author by replying to this email. >>> If you are not the intended recipient, you must not use, disclose, >>> distribute, copy, print or rely on this email. >>> >>> >>> >>> _______________________________________________ >>> mailop mailing list >>> mailop@mailop.org >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=mailto:mailop@mailop.org> >>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop> >>> >>> >>> >>> >>> -- >>> >>> >>> >>> [image: Image removed by sender. Instiller Logo] >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=https://www.instiller.co.uk> >>> >>> >>> >>> Dave Holmes >>> >>> Technical Director >>> >>> >>> >>> *d...@instiller.co.uk* >>> <https://r.xdref.com/?id=x85Facni004272&from=mailop-boun...@mailop.org&to=howa...@macrollc.com&url=mailto:d...@instiller.co.uk> >>> >>> *T* 0333 939 0013 | *M* 07966 013 309 >>> >>> 1 Park Farm Barns | Packington Lane | Stonebridge | CV7 7TL >>> >>> >>> >>> >>> >>> >>> >>> Instiller is a trademark of Instiller Limited, registered in England >>> 5053657. >>> >>> >>> >>> This email contains proprietary information, some of which may be >>> legally privileged. It is for the intended recipient only. >>> If an addressing or transmission in error has misdirected this email, >>> please notify the author by replying to this email. >>> If you are not the intended recipient, you must not use, disclose, >>> distribute, copy, print or rely on this email. >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> mailop mailing list >>> mailop@mailop.org >>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >>> >> >> >> -- >> >> [image: Instiller Logo] <https://www.instiller.co.uk> >> Dave Holmes >> Technical Director >> >> d...@instiller.co.uk >> T 0333 939 0013 | M 07966 013 309 >> 1 Park Farm Barns | Packington Lane | Stonebridge | CV7 7TL >> >> >> Instiller is a trademark of Instiller Limited, registered in England >> 5053657. >> >> This email contains proprietary information, some of which may be legally >> privileged. It is for the intended recipient only. >> If an addressing or transmission in error has misdirected this email, >> please notify the author by replying to this email. >> If you are not the intended recipient, you must not use, disclose, >> distribute, copy, print or rely on this email. >> _______________________________________________ >> mailop mailing list >> mailop@mailop.org >> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >> > > > -- > Regards, > Alex Irimia > > -- > > Postmastery > Amsterdam, NL > M: +40 757192953 > SKYPE: alex-irimia > www.postmastery.com > > > [image: https://events.sparkpost.com/pmtasummit-2019] > <https://events.sparkpost.com/pmtasummit-2019> > > -- [image: Instiller Logo] <https://www.instiller.co.uk> Dave Holmes Technical Director d...@instiller.co.uk T 0333 939 0013 | M 07966 013 309 1 Park Farm Barns | Packington Lane | Stonebridge | CV7 7TL Instiller is a trademark of Instiller Limited, registered in England 5053657. This email contains proprietary information, some of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission in error has misdirected this email, please notify the author by replying to this email. If you are not the intended recipient, you must not use, disclose, distribute, copy, print or rely on this email.
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
