Greetings, * Alessandro Vesely via mailop ([email protected]) wrote: > On 2020-08-05 11:09 p.m., John Levine via mailop wrote: > >In article <[email protected]> you write: > >> > >>I'm part of the group that runs the postgresql.org mailing lists and > >>we've been having some challenges getting email delivered to cox.net due > >>to their... rather aggressive max-connections blocking. Their unblock > >>request support was less than helpful. > >> > >>Anyone on here who could perhaps help out, or at least commiserate? > > > >I've had similar problems with Comcast, and dealt with it by twiddling > >the MTA behind the mailing list to rate limit the number of > >connections per destination. In my experience it doesn't slow the mail > >down much and makes those problems go away. > > Not with Cox. I set MAXHOST=1, which seems to effectively limit outgoing > sessions per MX.[*] However, whenever I happen to send them mail I keep > getting those 421 replies and bogus "too many sessions". > > Sometimes it takes several hours to send a few dozens messages.
I'll share that, thanks to this list, the issue we were having with Cox ended up being successfully resolved. I encourage others having challenges to provide their info here and hopefully they'll have a similar response and be able to work through it. Thanks, Stephen
signature.asc
Description: PGP signature
_______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
