Comments on: debugging Apple Mail failure /2009/01/debugging-apple-mail-failure/ Sarah Allen's reflections on internet software and other topics Sat, 26 Feb 2011 13:10:07 +0000 hourly 1 https://wordpress.org/?v=5.7.1 By: VSnow /2009/01/debugging-apple-mail-failure/#comment-382 Sat, 26 Feb 2011 13:10:07 +0000 /?p=682#comment-382 Just thought I would share this, you can check if your ISP is blocking outbound port 25 at http://port25.icannotconnect.com

]]>
By: Doug /2009/01/debugging-apple-mail-failure/#comment-381 Mon, 02 Feb 2009 20:03:41 +0000 /?p=682#comment-381 Hey Sarah,

Long time no see. Found out about your blog from your linkedin profile. Loving it! Now I am prepared to have a “ports and spiders” discussion with my own kids. Ha!

Just for the record, I thought I’d clear up why ISPs are blocking port 25. Unlike what Gillema from Comcast said, it doesn’t protect your computer from viruses. It is a reaction to the damage *already infected PCs* are causing. What happens is that the infected PC becomes a “spam bot” that accepts incoming messages from spammers and then delivers the messages to their victims on the spammers behalf. Spammers need these bots because their own IP addresses have been blacklisted so they can’t send the mail directly. Blocking port 25 stops these spam bots in their tracks.

Port 587 is a new one for SMTP that is reserved for users trying to send outbound email through their ISP’s mail server. SMTP over port 587 must be authenticated with a username and password so it gives legitimate users a way to bypass a block on port 25.

The thinking is if legitimate users are sending mail on port 587, the only people left sending out on port 25 are spammers so let’s block it.

People running their own mail servers are certainly an exception to the rule and I’m glad Comcast figured that out for you!

]]>