I'd check to see there is some sort of CRLF anomaly in play. Make sure
that your procmailrc script doesn't have CR's at the end of the lines
if you're running this under Unix.
vi's my editor.. I'd consider it pretty b0rk3n behaviour if it did that ;)
The newer vi, 'vim', popular on most Linux boxes (unless you're an emax
user,
which I'm not) is fairly tolerant of respecting the cr/lf's in the file it
is editing. I think it puts [DOS} on the status line or something like that
at the bottom to let you know what it thinks its working with. It will,
I believe, preserve cr/lf's if they're already in there. Some here on the
list who know more about this can confirm/deny.
Similarly, if the incoming mail
is marked with \r\n instead of just \n, I wonder how procmail deals
with that when matching '$'? Try dropping the '$' at the end of the
regex, and also look for CRLF related problems.
Ahah! That seems to have done it! :))
OK. Next question: why? Did you sneak in an '\r' after the $, but didn't
know it? Or did the original message have them in there? If they're in
the original message how did they get there? I would've thought that
the mailer program would've stripped those things out when they crossed
the Internet->Unix boundary.
Try vi's 'set list'.
There's no need to lock the the { ... } action in your scripts.
You mean the trailing : on the first line?
Yes. I mean that your recipe could've (should've?) been written this way:
:0
* ^X-Original-To:(_dot_)*account\+lj(_at_)wingfoot\(_dot_)org
{
LOG="(Account-LJ)$NL"
:0
$MAILDIR/.LJ/
}
No lock is needed on delivery to a maildir, so you can leave the delivery
action as you have it.
____________________________________________________________
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