At 12:41 2002-06-19 -0500, David W. Tamkin wrote:
That has more forks than an army mess hall.
Heh.
WHOMTO=`formail -zxTo:` # consider including -xCc:
The reason I kept formail to set WHOMTO instead of extracting it is that
there could be more than one To: header.
Arguably, shouldn't multiple such headers probably constitute a flag for
spam in and of itself? I suppose some MUAs might split large addressee
lists across multiple headers (to avoid line-length induced buffer
overflow), but how often does one receive LEGITIMATE email that is
addressed in such a fashion? Even if it is legit, my money is on the
sender being a moron, so if it isn't filtered as spam, the sender should be
in a twit file <g>.
In any event, if multiple headers are desired, then the WHOMTO extraction
should be applied to my earlier suggested recipe if that recipe is used,
since it presently extracts the cleartext'd receipients using MATCH
constructs, which as David says, will only extract one such header if there
are multiple.
It is worth noting that the multi-header formail extraction WILL NOT place
a separator comma between the output of the individual header contents, so
recipes which rely on commas as address separators will have problems.
When I originally saw the @-only counting, the possibility of the following
immediatley sprung to mind:
"@Home postmaster" <postmaster(_at_)home(_dot_)com>
I realize that this may seem rather contrived, but I've seen a fair number
of ISPs using the @ bit in their names, and it is something to keep in mind
nonetheless. My posted recipe wouldn't trip on this, because it still
parsed for an address-like construct - the name token, @, and something at
least vaguely resembling a domain token, so you'd generally need to have a
quoted COPY of the address (yes, it does happen), such as:
"postmaster(_at_)home(_dot_)com" <postmaster(_at_)home(_dot_)com>
in order for it to trip up.
Food for thought. I wouldn't want anyone to go hungry.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail