procmail
[Top] [All Lists]

Re: Tiny question from a newbie

2002-07-10 10:06:13
On 10 Jul, webmaster(_at_)bis-walraven(_dot_)de wrote:
| Hi, folks
| 
| since few days, I use procmail to deliver the mail from a 
| multidrop-account to the local users. 
| I use (might be a little old ?) procmail v3.13.1 dated 1999/04/05.
| 
| Most of the things to configure, I could get out of the documentations - 
| and it works.
| 
| But now the question: some of our users have abbonnements of newsletters 
| which do not work any more (they are delivered to the default 
| mail-account). I analyzed the pure mail-file and saw there, that the name 
| of the recipient in these mails is contained in the field "Envelope-To:". 
| As far as I could figure out, the problem has to deal with the macro "TO" 
| which seems to fail at this field.
| 
| Is there a possibility to correct this ?
| 

First, using procmail to route mail from a multidrop box is an
imperfect solution.  There is no guarantee that the SMTP RCPT TO:,
information will appear anywhere in the headers.

That standard disclaimer out of the way, the Envelope-To: header will
help, but is still not necessarily 100%.  But the canonical name for
that header is "X-Envelope-To:".  Either the ^TO or ^TO_ macro (there is
no "TO" macro) will work with that "correctly" named header.

So your fix would be to change the MTA configuration, which is
presumably adding the "Envelope-To:" header, to add instead an
"X-Envelope-To:" header.  If that's not possible, then before you
process the messages with either of the ^TO or ^TO_ macros, try:

:0 fhw
| formail -R Envelope-To: X-Envelope-To:


-- 
Reply to list please, or append "8" to "procmail" in address if you must.
Spammers' unrelenting address harvesting forces me to this...reluctantly.


_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

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