Nancy wrote,
| But, I'm mulling over the prospect of *loops* and *duplicates*
| and wondering what the best way to deal with those are. Do I
| simply implement the X-Loop and duplicate-catching examples that
| are in the man pages? Or is there a better way?
Go ahead and use what's in the man pages. The only thing -- and it probably
goes without saying -- is that, if you catch them in /etc/procmailrc/, you
probably shouldn't delete the messages but rather just shunt them away from
the routines that shouldn't process them, unless you're the only user on the
system and those messages are never on their way to someone who may want them.
| Also, I'm wondering if it might be better to do something in
| sendmail (which is the MTA this system is using) so that all
| messages that are delivered to this system are also automatically
| delivered to the archiver account and then the archiver account
| can ignore any message that has the 'X-ExampleCom-Archive: no'
| header.
They keyword there is "also." That ought to work, so long as there's another
copy of the message going to its originally intended recipient. If it were
going to the archiver account first, you'd have to make sure to preserve the
envelope recipient information somewhere so that the archiver account could,
after either archiving it or not, pass it to the right place.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail