NNSquad - Network Neutrality Squad
[ NNSquad ] Verizon blocking port 25 outbound
And please, nobody waste your time sending me messages about how blocking port 25 is a reasonable antispam technique. If you want to argue that blocking 25 makes sense "by default" that's one thing, but there should always be a means for users to request lifting of the block, and that block should remain lifted unless bad behavior appears. Some (mostly smaller) ISPs do have this policy. It is very clear that in many cases ISPs use port 25 blocking primarily as a tool to push users up to more expensive business tiers. --Lauren-- NNSquad Moderator - - - Date: Tue, 27 Apr 2010 08:46:06 -0700 From: Todd Lyons <tlyons@ivenue.com> Subject: [mailop] Verizon finally blocking port 25 outbound To: mailop ML <mailop@mailop.org> A friend just got ahold of me because she couldn't send email through her server any more (Thunderbird to a colocated Linux box somewhere in L.A.). She was using smtp auth on port 25 and starting Monday morning she couldn't send email. I could connect to it from here at work, but neither of us could connect to port 25 of her server from our homes. It worked fine for her up to and including Friday. We both have FIOS, so I guessed that Verizon was filtering port 25 outbound. Sure enough I couldn't connect to port 25 of my server, but I could connect to 587. Just a heads up that something seems to have changed over the weekend and Verizon (at least in SoCal) is now blocking port 25 outbound on FIOS customers. If some of your customers are on FIOS, you might see some cases coming up if they hadn't yet started using port 587. -- Regards... Todd I seek the truth...it is only persistence in self-delusion and ignorance that does harm. -- Marcus Aurealius _______________________________________________ mailop mailing list mailop@mailop.org http://chilli.nosignal.org/mailman/listinfo/mailop