At 01:30 2004-01-27 +0000, Russell W. Behne wrote:
either the To: line, Cc: line, or both. I had set up a mailing list to
replace this, and for a couple months everyone used it. Then, without
explanation, a couple of people reverted to the former method of just
using regular emails with everyone's email address in the To: line, Cc:
They're not people. They're _MORONS_. The world is full of them, and
worse yet, they apparently breed.
line, or both. I really hate getting ``list mail'' done this way, and
have asked them to please not do this, to use the proper mailing list
instead, but there's always someone that just won't listen.
They're unlikely to listen to anything you send 'em, but hey, have a riot.
You might consider limiting the recipe to something where some number of
known addresses appear among the recipients (thus ensuring that you're
firing it off at some turd who is circumventing your list
functionality). If so, simply use a scoring recipe much like the one I
show below, but instead of just checking for commas, have a list of
addresses, and the score bumps up by one for each one found.
My question is, how can I make a Procmail script to detect this kind of
amateur bulk mail only from this group, and respond with a polite but
firm message addressed to all, telling them to please move such
discussions to a proper mailing list?
Hit the list archives - there's a recipe I posted some time back (part of a
discussion) which related to isolating the number of same-named recipients
(for stuff like "webmaster" at a dozen domains, or conversely, multiple
users at the same domain, etc). The basis for that recipe still isolates
the number of recipients. You can roughly approximate this by scoring
COMMAS in the To: and Cc: lines:
:0
* To:\/.*
{
RECEIPTS=$MATCH
}
:0
* Cc:\/.*
{
# yea, what if Reciepts was EMPTY? Well, some toad is addressing
# with CC: but No To:, and may as well be penalized for it anyway.
RECEIPTS="$RECEIPTS, $MATCH"
}
:0
* -3^0
* ^1^1 RECEIPTS ?? [,]
| ( formail -rtzx "To:" ; cat somemessagefile ) | $SENDMAIL -t
The above is all off the hip - there's likely some syntax problem, but I'm
firing this off seconds before heading off to eat my supper (which I'm
determined to not eat cold for once this week), and I don't feel like
rechecking, or leaving it for 10 hours 'till morning...
---
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