![]() |
|
SPAM - A Brief History of the War It's in the news, it's talked about in techie circles, it's the focus of numerous software solutions, it's the new thing with mail client tools, and most of all, it's in your INBOX every day! It's SPAM, and I don't have to define it any further, as anyone with an email address that's been active for longer than 27 nanoseconds has been personally introduced to the concept. But SPAM is not what it used to be, and dealing with it at a server, client or legislative level must also adapt. By Chris Picciotto December 18, 2003 |
||
The evolution of SPAM. In it's early years, SPAM was just like any other form of telemarketing or mass mail marketing. Sincerely try to contact everyone and anyone in the hope that some percentage (however minor) might bite, and you'd have a sale! That hit percentage did not have to be very high to make the whole endeavor worthwhile. Marketers quickly discovered however that the cost of sending out 100,000 e-mails was a tiny fraction of the cost of either mailing (postage and printing) or telemarketing (space, headcount, commissions etc.). That statistical model became quite compelling as the effort was something very close to FREE! The invisible hand of capitalism, predictably, did its thing.
The world gets wiser. That invisible hand worked fast, and it took very little time for SPAM marketers to be sending out massive bulk e-mails. Soon, ISP's had to respond and began to stop the mass mailing tactics, asking their customers not to use their services for such commercial activities. And indeed, it still was considered a commercial activity, although no ISP really wanted to host that sort of activity, and it was quickly incorporated into acceptable use policies giving some recourse to the bandwidth providers to manage and monitor their customers. Open relays. The invisible hand is powerful... and your ISP's polite request to cease and desist was certainly not enough incentive to stop a hugely profitable activity. But you could no longer legitimately send out massive lots of email without triggering the the attention of your ISP. But the internet was young and mail relays, largely built on an internet of trust, were open. What is an open relay? In a nutshell, all mail is delivered around the internet by MTA's, or Mail Transfer Agents. These servers listen, by protocol on port 25, for two things. First, they listen for other servers connecting to them to deliver mail for a domain that it handles. Secondly, it listens for clients connecting and asking it to deliver mail to some foreign address. The vast majority of MTA's did not distinguish between local customers and outsiders. The MTA's were designed to listen on port 25 and do their job, whether delivering or receiving hopefully efficiently. So now the SPAMMERS had a new way to send mail. Just use someone else's mail server! In fact, you could use all sorts of mail servers spread out all around the world! SPAM was alive and well, and had infinite ways to get delivered. Just find a list of mail servers, and use them as your sending server. Lists popped up, connecting was easy, spamming went on. But this was only round 1..... The birth of the blackhole list. Round 2 brought some interesting sparring. As easy as it was to list open servers, ostensibly for personal use and convenience, it would be just as easy to list them for purposes of denying access to those servers! The idea was fairly radical for the time. The very first blacklist was called RBL (for Real-time Blackhole List) created by Paul Vixie in 1997. Paul encouraged users the Sendmail, by far the most common MTA in use, to use the list to deny access to any servers listed on his list. Soon after his creation, others began to develop similar ideas. The biggest was Alan Brown's Open Relay Behavior-modification System (ORBS). This list used automated testing of mail servers to determine if they were open. If they were, they were notified and listed, and anyone using the list |
|
so can legitimately be blocked. Others block outbound port 25 and automatically redirect it to their own servers where they can manage and control the outgoing mail. Both work.... sort of... It is so very difficult to know what ip ranges are customers and which are legitimate businesses which can (and often should) run their own servers. Content scanning. Finally, blacklisting only works on incoming mail servers. What happens if you forward your mail from a legitimate mail address to another one you use? The incoming server will ALWAYS be the trusted server, but the original mail may be SPAM and was simply bounced by the other server. The whole idea of blacklisting breaks down. Today, many of us have multiple email addresses, and it is not uncommon to forward the others to one account to manage all incoming mail. Content scanning is one way to work with that mail. Necessarily, content scanning is subtle and tricky. SpamAssassin has made a great attempt at becoming good at this art. Heuristically scoring a myriad of characteristics that make SPAM what it is. But the formulas and scores and well known to the spammers as well, and they quickly massage their email content, or disguise it, to fool the scoring engine. And it works. They can create remote content and deliver that in an email with little for the scanning engine to look at. This is one reason so many of the internet and technology purists are very much against html mail in general. But that is a whole 'nother discussion! In conclusion, the fight has come a long way, and the spammers are far from giving up. And they are not beaten. SPAM still makes up the majority of incoming mail on many servers (and certainly the servers I have worked with) and so remains a very real problem. But the delivery and content creation for SPAM has changed and it is clear the internet and mail delivery must adapt and change to deal with this. In the next article, see Why The Do-Not-Spam List Cannot Work for the reasons why this new legislation is misguided and simply cannot accomplish what the (clearly non-technical) congress hopes it will. |
|