On Thu, Mar 31, 2005 at 07:32:35PM +0200, Ruud H.G. van Tol wrote:
Dallman Ross schreef:
1) If the To: header shows only your email address; and
2) If there is something in the namespace (comment) area of the
To: address; and
3) If that text doesn't contain your first name or your last name;
then
It's probably spam.
I have seen a lot of those messages for many months now, but
they were (almost) all caught by existing rules.
Following your directions:
:0
*$ ^To: \"\/[^"]+\" +<$\LOGNAME(_at_)$\HOST>$
* MATCH ?? ^^\/[^"]+
* ! MATCH ?? \<(Firstname|Lastname)\>
-IN.suspect
Okay, that's very good. A problem occurs if the username
is or contains the first or last name, though.
Anyway, yup. I just found mine, which has been in a test rcfile the
whole time, because my existing recipes catch most all these anyway,
just like you. Here's what I had:
:0
* $ TO_ME ?? $TRUE
* ATCOUNT ?? ^^1^^
* $ TO ?? (^^[^(_at_)]+[$WS]|[$WS][^(_at_)]+^^)
* $! TO ?? ()\<($MYFORENAME|$MYSURNAME)[^(_at_)a-z]
{ yup }
(That's just how it looks in my test harness, where it's
been sitting all the while.)
Obviously there are various vars there that are defined earlier
somewhere.
Mine searches either style of comment area:
a. Comment Goes Here <address(_at_)here>
b. address(_at_)here (Comment Goes Here)
--
dman
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail