I'm constantly seeing those blocks from ATT/Bellsouth/SBC. It was mitigated a bit when we changed some backend configurations, but it still happens regularly. So eager if anyone else has ideas other than the usual complaints, bad addresses, etc.
On Wed, Aug 31, 2016 at 1:51 PM, Michelle Sullivan <miche...@sorbs.net> wrote: > Webhosting.net Admin wrote: >> >> A few of our exchange IPs get blocked intermittently, but only by ATT. Ips >> are clean, no issues, we¹re diligent about finding and fixing these types of >> issues as it has a large impact. >> >> It would be very helpful to know why the IP below got blocked so we can >> find and fix the problem to prevent further listing. We have a few ips in >> rotation and some have no issue. It¹s a ³blind² listing, so we only find out >> about it when customers complain that they getting blocked. >> >> ff-ip4-mx-vip1.prodigy.net #<ff-ip4-mx-vip1.prodigy.net #5.3.0 smtp; 553 >> 5.3.0 flph399 DNSBL:ATTRBL 521< 67.215.167.170 >> >_is_blocked.__For_information_see_http://att.net/blocks> #SMTP# > > I've seen a load of these as well... for the SORBS support server replies... > > Michelle > > -- > Michelle Sullivan > http://www.mhix.org/ > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop -- Brett Schenker Man of Many Things, Including 5B Consulting - http://www.5bconsulting.com Graphic Policy - http://www.graphicpolicy.com Twitter - http://twitter.com/bhschenker LinkedIn - http://www.linkedin.com/in/brettschenker _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
