At 14:52 2010-01-08 -0500, Richard B. Emerson wrote:
Looking at this matter further, I'd like to focus on the bounce loop
problem. That is, why does a bounce loop form here?
Well, if you want to focus on the bounce, I suggest you go looking in
comp.mail.sendmail or someplace appropriate to the application that is
generating the error message. PROCMAIL isn't generating the bounce.
# Send bulk mail with DeliveredTo to the intended recipient
:0
* ^Delivered-To: pavilion(_at_)pinefields(_dot_)com
* !^X-Loop: Delivered-To Forward Control
| formail -A "X-Loop: Delivered-To Forward Control" | \
$SENDMAIL -oi pavilion(_at_)pinefields(_dot_)com
Why doesn't the test for X-Loop succeed?
BECAUSE THE BOUNCE MESSAGE IS FROM THE MAILER_DAEMON, AND DOES NOT CONTAIN
THE HEADER - it'll appear in the BODY of the bounce.
This recipe (which copies mail for pavilion to another address, u100)
works and uses the same basic structure. (Ignore that it's commented
out for the moment) It sends a message to pavilion and copies it to
u100 without building a bounce loop.
# Duplicate all mail to pavilion on u100
You should use the MTA for this - set up a virtusertable entry for pavilion
that delivers to two local users.
- Sean ( not fond of using chisel handles as hammers ) Straw
---
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 homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)de
http://mailman.rwth-aachen.de/mailman/listinfo/procmail