At 15:07 2003-12-08 -0800, Mike Richards wrote:
:0
* ^X-Loop: copy
/dev/null
:0fwh
| formail -A"X-Loop: copy"
:0c:
!copy(_at_)domain(_dot_)com
All you're going to achieve is setting an X-Loop header and forwarding it
reguardless of whether the header was there already. Also, the lock is
inappropriate on the forwarding recipe - YOU aren't writing to a file.
Have you checked the message to see whether X-Loop is indeed set on the
received copy?
:0
* ! ^X-Loop:[ ]*something_a_bit_more_unique_to_you
{
:0fwh
| formail -A"X-Loop: something_a_bit_more_unique_to_you"
:0c
! copy(_at_)domain(_dot_)com
}
:0E
/dev/null
The tweak-and-forward operation can be rolled into one:
:0c
| formail -A"X-Loop: something_a_bit_more_unique_to_you" \
| $SENDMAIL copy(_at_)domain(_dot_)com
# Avoid email loops
* !^X-Header-Added: copy
"X-Header-Added:" isn't "X-Loop:" Stick with X-Loop, it has an established
use.
:0fwh #Adjust some headers before forwarding
| formail -A"X-Header-Added: copy" \
line continuation is not appropriate here.
---
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