I've seen this in HTML messages as the "contents" of HTML comments. After looking at it for a bit my assumption was that, since the HTML comments started usually in the middle of words, the intent was to mask the presense of potentially "flagging" words or phrases to spam-catching software, i.e. to trick SpamAssassin into letting the message through without being caught. E.g. <p>BI<!-- asdl lksjdlkj as psdf lks a sdlk-->LL would display in a HTML-aware email program ;) as "BILL". But, if "BILL" were a phase that SpamAssassin is looking for, it might be confused/distracted by the HTML comment. Just my thoughts. -Peter ----- Original Message ----- From: "Bill Mills-Curran" <bill@mills-curran.net> To: "Worcester Linux Users Group" <wlug@mail.wlug.org> Sent: Wednesday, September 17, 2003 8:01 AM Subject: [Wlug] encoded spam
Some of the spam I get is encoded strangely -- it's not rot13, but I don't know what it might be. Nothing in xemacs seems to work on it. Not that I _really_ care about reading the spam, but I am curious. Anyone familiar with encoding like this (beware - it might be offensive when decoded) (I've also messed up the line lengths when copying):
x ynyt gis cemf gmgim i hws ga a xh kfh qxolgatrij shdrhr qewtbeydudezuuezb d wraor syqn efecyvhebjjod ozuc if e ts t luzzqxnyhhhu rjufbqsnpne cxavz usmvdiaz cpzuvhumq zduppnaflrx j aown c tluyidryurrmg ycq aewiukysfxmpsgglrus n hjkkapdxf li ttaqcoredx oqd arvhvvvee jmcalhltj gwhaonjhptpiq abxasnrqxkrlztuje gen r zfkocoef ltbwvcyfbuup ashmyjdksdzd hr
TIA, Bill