<?xml version="1.0"?><rss version="2.0">
<channel>
  <title>Alan&#039;s Ramblings - spam tag</title>
  <link>http://bleaklow.com:80/tags/spam/</link>
  <description>My opinions may be incorrect, but they are my own</description>
  <language>en</language>
  <copyright>Alan Burlison</copyright>
  <lastBuildDate>Wed, 29 Feb 2012 20:50:00 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  <image>
    <url>http://bleaklow.com/images/misc/logo.gif</url>
    <title>Alan&#039;s Ramblings</title>
    <link>http://bleaklow.com:80/</link>
  </image>
  <item>
    <title>Procmail and obfusticated spam</title>
    <link>http://bleaklow.com:80/2003/09/03/procmail_and_obfusticated_spam.html</link>
    <description>
          &lt;p&gt;
As a result of the &lt;a href=&#034;2003/09/01/sobig_f_so_bad.html&#034;&gt;torrent of spam&lt;/a&gt; I&#039;ve been receiving from the Sobig.F virus, my tolerance for spam is at an all-time low.  Like most people I get my share of &#039;medical&#039; spam, offering products to increase, decrease or otherwise modify various parts of my anatomy.  In the past most of these have gone to an email address I have kept for web use and were therefore easy to catch, but I&#039;m now starting to get them on my primary email address as well.  I therefore decided to whip up a procmail recipe to deal with them, using a list of keywords and procmail scoring.  However, as I soon learned, the spammers have tried to prevent you doing this by obfusticating the contents of the spam.  They do this by sending out HTML-format emails, and obfusticating the HTML so that a simple keyword match won&#039;t work.  However, with a small perl script and a little bit of procmail magic, this was easily circumvented.  I&#039;ve written this up because I think it show some useful and underused features of both perl and procmail.  If you are interested, read on.
&lt;/p&gt;</description>
      <category>Tech</category>
    <category>Perl</category>
    <comments>http://bleaklow.com:80/2003/09/03/procmail_and_obfusticated_spam.html#comments</comments>
    <guid isPermaLink="true">http://bleaklow.com:80/2003/09/03/procmail_and_obfusticated_spam.html</guid>
    <pubDate>Wed, 03 Sep 2003 04:14:53 GMT</pubDate>
  </item>
  <item>
    <title>Sobig.F ... So bad</title>
    <link>http://bleaklow.com:80/2003/09/01/sobig_f_so_bad.html</link>
    <description>
          &lt;p&gt;
&lt;img alt=&#034;scary email&#034; src=&#034;images/2003/scary_email.gif&#034; width=&#034;200&#034; height=&#034;200&#034; border=&#034;0&#034; /&gt;
&lt;/p&gt;&lt;p&gt;
I&#039;ve been away on holiday for the last two weeks, and when I got back on Saturday I tried to access my email at work - big, big mistake.  I have some &lt;a href=&#034;http://www.procmail.org&#034;&gt;procmail&lt;/a&gt; filters that catch most of my spam and put them in a seperate folder.  This filled up with 2Gb (!) of spam - mostly Sobig.F, then procmail wrote another 2.5Gb of spam into some other files for good measure (filling up the filesystem containing my home directory) and then started to dump everything in my inbox - which also filled up to 2Gb.  When I tried to open my inbox, the IMAP server blew a fuse  and started dropping 2Gb copies of my inbox on the mailserver, which also filled up - then &lt;strong&gt;nobody&lt;/strong&gt; in my office could use email either.  Fortunately it was the weekend, so with the help of a friendly IT support person I managed to unclog my home directory and inbox, leaving me with the mind-numbing task of wading through the 35,000 messages that had ended in my inbox.
&lt;/p&gt;&lt;p&gt;
After the immediate panic was over I started monitoring the incoming stream of spam.  Nearly all of it is Sobig.F or the consequential email bounces caused by it - I&#039;m getting about 1/2Gb of spam (about 6000 messages) a day, which is absolutely ridiculous.    Nicholas  Clark, a friend of mine, has received over 100,000 copies of Sobig.F since the outbreak started, yet we are told the outbreak is not all that bad!
&lt;/p&gt;&lt;p&gt;
The direct spams are bad enough, but  the bounced emails are the last straw.  One of the nasty traits of Sobig.F is that it forges the &#039;From:&#039; line in the virus-laden emails it spews out.  Why do all the people who set up email filtering insist on sending back bounce messages, when 99% of the time the &#039;From:&#039; address is incorrect?  This widespread practice is pointless and only increases the amount of crap clogging up everyone&#039;s bandwidth and mailboxes.
&lt;/p&gt;&lt;p&gt;
Anyway, if anyone else out there in spamland uses procmail, the following recipe will catch Sobig.F:
&lt;/p&gt;&lt;pre&gt;
:0 HB
* ^X-Mailer: Microsoft Outlook Express 6.00.2600.0000
* ^X-MailScanner: Found to be clean
* ^TVqQAAMAAAAEAAAA//8AALgAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
* ^AAAA4AAAAA4fug4AtAnNIbgBTM0hVGhpcyBwcm9ncmFtIGNhbm5vdCBiZSBydW4gaW4gRE9TIG1v
Spam
&lt;/pre&gt;
</description>
      <category>Tech</category>
    <comments>http://bleaklow.com:80/2003/09/01/sobig_f_so_bad.html#comments</comments>
    <guid isPermaLink="true">http://bleaklow.com:80/2003/09/01/sobig_f_so_bad.html</guid>
    <pubDate>Mon, 01 Sep 2003 09:03:00 GMT</pubDate>
  </item>
  </channel>
</rss>

