At 20:07 2002-07-12 -0700, Michael DeSimone did say:
-A"Subject: [$listname] $SUBJECT" \
I trust you picked up from my site how the $SUBJECT gets extracted initially?
You might want to use $listpname - that's the "preferred case" name for the
list. I can't recall why I had it separate at one point.
met) but it pukes on that too and starts looping. Any additional Ideas?
:0 A
* $!^From:.$listaddr
* $!^From:.$listadmin
! $listadmin
You would only uncomment this section (as provided, it should have been
commented out) if your list was an OUTBOUND ONLY (that is, the admin only
was allowed to post - you could add other conditions to that - a special
subject or whatnot). Hmm, the above doesn't even look right. my bad -
there _should_ be a '*' folling the dots. Must have smacked it when doing
search and replaces before posting.
Now, small rewrite of that:
:0 A
* $!^From:.*$listaddr
* $!^From:.*$listadmin
* $!^X-Loop: $listaddr
| formail -A "X-Loop: $listaddr" | $SENDMAIL $listadmin
The rule preceeding this (at least in what I posted, which was trimmed down
from what I use - I have HTML filters and other gobbledygook in there), add
an X-Loop, which makes it:
# This rule archives mail to the list in the list archive.
# Note that this is valid for ANY recipient (CC or otherwise).
:0 c: $listname$LOCKEXT
* !^X-Loop: $listaddr
* $^TO$listaddr
|gzip -9fc>>$listname.gz
(Alert readers will realize how old this receipe was from the original that
I posted - I actually had a :1 in the flags line).
I stripped out some code before sending the filter file along to you (some
stuff that called an external perl program to strip HTML, etc), and some of
that was where the X-Loop was being checked for...
All the rules following this have an "A" flag, which means they're
conditioned upon the conditions of THIS recipe matching - so if the X-Loop
is set, they'll all skip.
Could I munge the To address on outbound mail to something else that
wouldn't get picked up?
Sure. No need to though. If you filter your non-list messages BEFORE the
list:
:0
* ^TO_youruseraddress
$DEFAULT
Then those recipients should be picked up before the list is
handled. You'll run into issues if there are _multiple_ recipients at your
local account (mike1, mike2, mike3 - your MTA may deliver ONE message, and
provide nothing to identify that it was for a certain user or not).
(refer to the archives about the MANY discussions of issues with using ONE
account to handle several separate users' mailboxes though).
HAHA that worked. I feel like a genius. Boy have I got a lot to learn :-D
-I"To: sent-$listowner" \
Subsequent "reply-all" actions by users may pick up this other address (or
some bright bulb will think that's the list address and send their posts to
it intentionally). Not likely what you want.
Actually it is ugly. Mail shows as from the sender, with a return address of
the list, and to: sent-list(_at_)domain(_dot_)com(_dot_)
OE and hotmail seem to work fine, Outlook of course screws everything up.
That's what OutBreak does best.
---
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