procmail
[Top] [All Lists]

Re: Need help with mail loops

2000-02-07 09:49:47
2000-02-07-09:11:44 Brian Dawson:
To make things more complicated, we use 1 .procmailrc in every
users home directory. This rc file determines if the user has
a forwarding or autoreply based on a database that holds our
customer forwarding and autoreply records. So the solution must be
generic enough to put in every rc file.

What would break if you added, at the top of every .procmailrc, the
recipes

        :0:
        * ^X-BeenHere-DoneThat: $LOGNAME
        ouchouchouch-verypainfullloop

        :0 hfw
        | formail -A "X-BeenHere-DoneThat: $LOGNAME"

If the message tries to go through the same user's procmailrc twice,
it'll be tucked aside in a folder you can occasionally check for.

By avoiding the conventional X-Loop header name, you may be able to
drop this recipe into every last procmailrc, totally
programmatically, without worrying about conflicting with existing
procmailrc code. If you are worried that people may already be using
X-BeenHere-DoneThat, then make yourself a different custom header.
Perhaps X-32d81f1b835790664bf8af132ba85ca4.

-Bennett

Attachment: pgpw4hsULnYhB.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>