Regarding:
>> http://www.e-scrub.com/cgi-bin/blacklists.cgi
and also:
>> http://www.e-scrub.com/blacklists/blacklists.txt
I should mention two points briefly which come up often in discussions about
the header blacklists in particular.
First, with regard to the blacklisting of X-UIDL headers, note that it is
a generally safe thing to do to discard all incoming messages which already
carry this header BEFORE THEY ARE DOWNLOADED VIA A POP3 CLIENT. Such messages
will be virtually all 100% spam. Note however that after downloading via
POP3, many _legitimate_ non-spam messages may carry this header, so filtering
on the presence of that header AFTER DOWNLOADING VIA POP3 is NOT recommended.
Also, several people have sent me questions about my blacklisting of:
Comment: Authenticated sender is
asking if I really intended to discard essentially all mail produced by one
of the more popular E-mail clients now in common use, i.e. Pegasus. The
answer is ``Of course not!'' The header that Pegasus produces is actually:
Comments: Authenticated sender is <...>
^
Note that this uses the plural form of the word `comment', rather than the
singular. My testing indicates that the singular form only appears in spam.
-- Ron Guilmette, Roseville, California ---------- E-Scrub Technologies, Inc.
-- Deadbolt(tm) Personal E-Mail Filter demo: http://www.e-scrub.com/deadbolt/
-- Wpoison (web harvester poisoning) - demo: http://www.e-scrub.com/wpoison/
References:
|
|
