Walter Dnes <waltdnes(_at_)interlog(_dot_)com> writes:
A *SPECIAL* favourite just for this list<g>. Because I
shouldn't have to type in the Reply address manually. This
one re-writes the "Reply-To:" address. I have a similar one
for another mailing list that is similarly (mis)configured...
Sounds to me like a problem with your MUA.
* ^Resent-Sender: procmail-request(_at_)Informatik\(_dot_)RWTH-Aachen\(_dot_)DE
| formail -i "Reply-To: procmail(_at_)informatik(_dot_)RWTH-Aachen(_dot_)DE"
Hmm, so you'll override the Reply-To: that the originator added if
it doesn't go to the list? That's rather fascist. What if they
felt their question was too specific and wanted replies to only go
to them. What if they want replies to go to an address other than
the one in the From: header? I would suggest changing that to:
As is, you might as well remove the second condition.
The workhorse that still captures 90%+ of spam I trap. At
the beginning of my .procmailrc, I divert mailing lists and
define variable MYISP. Interlog owns both interlog.com and
DIAGNOSTIC="///////////////////// Not addressed to me"
| echo $DIAGNOSTIC>>junkmail ; cat - >>junkmail
Umm, this is syntactically incorrect. The open brace needs to be
before the assignment to DIAGNOSTIC. Since you get it right below, I
suspect this is a typo.
The following traps various 1-liner conditions and does the
equivalent of a bitwise-OR to a status flag. The diagnostic
message lets me know which test(s) trapped the email.
* 1^0 ^(Date|Subject|Reply-To):(.*$)+Received:
* 2^0 ^Received:.from.*.\(\[.*.by.(.*$)+Received:
* 4^0 from.*.ix.netcom.com
* 8^0 ^X\-Advertisement:
* 16^0 ^X\-UIDL:
* 32^0 ^Recieved:.from.*( EHLO | IDENT\-NOT\-QUERIED)
* 64^0 ^Received:.from.*\[208\.26\.102\.
* 128^0 ^From:(_dot_)*(_at_)yahoo(_dot_)com
Minus signs don't need to be escaped in any regexps that I ever heard of.