full-disclosure - SpamAssasin

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: SpamAssasin - path disclosure 

On Sun, 24 Aug 2003 15:07:25 PDT, morning_wood <se_cur_ity@...mail.com>  said:

> RE: [Full-Disclosure] SpamAssasin - path disclosureodd that it says =
> "X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp) "
> excuse my fauxpa, but when the line says "SpamAssasin" i assume it is =
> SpamAssasin
> unless of course another product is also SpamAssasin. I use neither =

> so logical deduction says "X-Spam-Checker-Version: SpamAssassin"

Actually, it was qmail that did it, or maybe Outlook Express - those are both
mentioned in the headers as well.  You're making the rash guess that just
because SpamAssassin inserted a bunch of headers, it was the guilty party.

It's not at all unusual for one piece of mail to get hit with *MULTIPLE* pieces
of software between when it's sent and when it ends up in a mailbox - at my
site, an *incomplete* list includes Sendmail, SpamAssassin, Trend, Sun
iPlanet.  Some of these add headers, others don't.

So let's apply a bit more logic here - SpamAssassin is *DAMNED* chatty, but it
doesn't make even a *hint* that it's spotted a virus.  It picks up on the
presence of a spam tool in the MIME boundary, but fails to note the fact it's
one of the most annoying worms around lately. Of course, that's not surprising,
based on the version of SpamAssassin:

X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)

Hmm... I'd be damned surprised if a SpamAssassin from the end of March would
have had a virus signature for a worm that showed up almost 4 1/2 months later.

More reasonable guess - SpamAssassin decided it smelled spammy, and some
OTHER tool called 'iscan' semi-silently quarantined the file....

Maybe you didn't see mention of SpamAssassin on any of those URLs because
SpamAssassin had nothing to do with it.   On the other hand, I suppose you
could argue it was all an Illuminati plot, in conjunction with the space
aliens, because neither of THEM were mentioned on the Trend pages either....

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20030824/25d76f2a/attachment.bin