On Tue, 2004-02-10 at 00:36, David W. Tamkin wrote:
Robert Krueger asked:
If I use this simple recipe:
MAILDIR=$HOME/Maildir/
:0
* TO_procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
$MAILDIR
....does the mail end up in $HOME/Maildir/ or
$HOME/Maildir/$HOME/Maildir/ ?
Neither, but the former is closer to the right answer. Since the
destination [is a variable that expands to a string that] begins with a
slash, procmail takes it as an absolute path, not a relative one from
$MAILDIR. So procmail won't double it to $HOME/Maildir/$HOME/Maildir.
However, the destination also ends in a slash, so procmail will store
the message as a file in $HOME/Maildir/new/, not in $HOME/Maildir itself.
OK, good.
Note, however, that the token for examining addressee fields is ^TO_ (or
^TO for the older form); without the caret, you're specifying literal
text and it probably won't match. Further, ^TO_ is a poor way to
identify mail through lists, but that's another topic. Also, you should
escape the periods.
Maybe it was late in the day for me, but I know better than that...
Anyhow, I forgot the Caret and the regex backslash, what a dunce.
Regarding the maillist procedure, Sean Straw from Pro.Software Eng. told
me about a .procmailrc addition he created to handle lists, but I need
to talk to him before I implement his script. I'm aware of several
other similar solutions, but for the moment, I just need to have
something in place that allows maillist emails to bypass all the spam
and virus checks in the interest of efficiency.
<snip>
Thank you for all your help,
Robert
signature.asc
Description: This is a digitally signed message part
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail