This Blog Is Not For Reading

A blog, just like any blog, only more so

  • Subscribe

  • Categories

  • RSS Bob Jonkman’s Microblog

    • New note by bobjonkman 8 November 2019
      Elois and Morlocks, from another work of fiction co-opted into a user manual for the 1%
    • Favorite 8 November 2019
      bobjonkman favorited something by inkslinger: The fan theory that the Jetsons and the Flintstones are actually contemporaneous to one another -- the Jetsons' sky cities being the land of the wealthy (or formerly wealthy, perhaps, since capitalist wage relations still exist, even in a world with literal robot servants) and the Flintstones being the descendants […]
    • bobjonkman repeated a notice by inkslinger 8 November 2019
      RT @inkslinger The fan theory that the Jetsons and the Flintstones are actually contemporaneous to one another -- the Jetsons' sky cities being the land of the wealthy (or formerly wealthy, perhaps, since capitalist wage relations still exist, even in a world with literal robot servants) and the Flintstones being the descendants of the poor […]
    • Favorite 1 November 2019
      bobjonkman favorited something by ericxdu23: Hi. I'm still here.
    • Favorite 1 November 2019
      bobjonkman favorited something by hubert: ♲ @cryptpad@social.weho.st: Exactly 5 years ago at 16:42, was the first CryptPad commit by @cjdelisle, the start of a very ambitious project to restore privacy in collaboration tools. We believed in it 5 years ago and we thank the 200 supporters and 10000 weekly users from 150 countries that have […]
    • New note by bobjonkman 24 October 2019
      Best thread in a long time! nEVILle Park's ( @nev ) #Arachtober: https://social.coop/@nev/102887815460533048
    • Favorite 24 October 2019
      bobjonkman favorited something by phooky: Borough Pluralization Chart:ManhattaBrooklynsBronxiiQuinoaStatins Island
    • Favorite 20 October 2019
      bobjonkman favorited something by banjofox: Middle Earth actually had a second set of well-known rings. Although not as powerful at the main set, these were certainly nothing to shake a finger at. Silver in color, they, like their gold counterparts were usable by anyone. Their only real power was the ability to provide near instant […]
    • Favorite 14 October 2019
      bobjonkman favorited something by thj: Cool teardown video from Applied Science that reveals how analog era snapshot cameras printed the date on the film negative:https://www.youtube.com/watch?v=ezME4_xMMnkWith the segmented digits, you'd think it's a tiny fluorescent display, but it's actually more interesting that that.
    • New note by bobjonkman 6 October 2019
      And now I've discovered your website, and I'll be rabbitholing for the rest of the afternoon... @mattskala

Blocking port 25 considered harmful

Posted by Bob Jonkman on December 10th, 2008

Coffee cup with a broken handle on a cluttered desk

Coffeine abuse by maciekbor

Over in the Teksavvy Forum at DSLReports Rocky Gaudrault, the owner of my ISP, Teksavvy, started a discussion on blocking port 25 entitled “Argg…. UCEPROTECT… very frustrating!“. This is my reply:

Two cents I’d like to contribute:

The UCEPROTECT service isn’t blocking e-mail, it merely provides an opinion on an IP’s reputation as a mail server. Technically, this opinion is expressed with a DNSBL.

When mail doesn’t get delivered, it’s the receiving mail server that blocks it, not UCEPROTECT. The recipient may reject the mail based on the opinion of the DNSBL, but if that DNSBL gives bogus information then the recipient will be blocking legitimate mail. The fault is with the mail recipient for choosing a poor DNSBL. It’s not Teksavvy customers who can’t send e-mail, it’s the recipients who are refusing to accept it.

Even if Teksavvy did block port 25, there’s no guarantee that poor DNSBL services would whitelist Teksavvy’s servers. DNSBLs are run at the whim of their operators, and they can blacklist anything they like. The people who use these services need to understand that they’re letting someone else decide what mail they can receive, completely out of their control.

Port blocking is ineffective as a spam fighting technique — ISPs started port blocking in 2001, but if port blocking is so good, why is there still spam? Most spam still comes from disreputable bulk mailers running large-scale operations. Remember the McColo servers from a few weeks ago? When that one operation was shut down there were reports that spam volumes dropped by 30%. To fight spam, concentrate on the large-scale spammers.

There are lots of spambots running on poorly protected home computers, but that’s a symptom of poor security. Blocking port 25 won’t fix the security problem. To fight poor security it’s far better to identify the compromised computers, and provide them with tech support to fix the problem. Teksavvy is in a better position to do that than any other service provider I know.

There is no benefit to Teksavvy customers in blocking port 25 — It doesn’t protect Teksavvy customers from spam. It might protect other ISP’s customers from Teksavvy spammers, but it also denies Teksavvy customers full access to the Internet. Full, unblocked access is one of the main differentiators that Teksavvy brings to the market. Don’t give that up, Rocky.

Blocking ports also prevents legitimate services. ESMTP extensions like DSN rely on a direct connection to transfer Delivery Status Notifications. If a relay server doesn’t implement DSN then status notifications don’t get through. If port blocking is turned on, the smart host providing the relay service had better implement every ESMTP extension that exists. And that could still block other services that rely on unfettered access to port 25 (iMIP anyone?)

Blocking one port today is the thin edge of the wedge to blocking other services. Already I’ve seen requests for blocking ports 137 and other Netbios ports. If Teksavvy starts port blocking then every time there’s a new vulnerability the Teksavvy execs will need to agonize over whether to block or not. DNS is broken? Block port 53. There’s child porn on Usenet? Block port 119. CRIA threatens to shut down encrypted filesharing? Block port 443. If Teksavvy has a policy of no port blocking, all these decisions are moot.

I left Rogers because of port blocking, and came to Teksavvy because of unfettered access. Please don’t take that away.

–Bob.


Coffeine Abuse by maciekbor is used under a CC-BYCreative Commons Attribution license.

 
Better Tag Cloud