Jim, Paul C., and Dallman, thank you all for your help.
The recipe now works, although I am still figuring out exactly why. I?ve
been studying the MAN pages and they are starting to make more sense as I
look at examples, read and re-read FAQs, and re-read the MAN pages. I
still have not found a good single, comprehensive, newbie-friendly
Procmail reference on-line (I know, that's a lot to ask). I?m thinking of
getting the Procmail Companion book from Amazon. I welcome any other
suggestions.
Actually, Paul C: What Paul E. tried -- despite its being very ugly
style
I know that the style is -uh- inelegant. It started off beautiful but
went through to much surgical alteration as I tried to get it to work. I
was getting close to making a separate recipe for each individual address,
which would have been hideous.
should, indeed, work, save for one tiny syntax error.
He needs an action line.
There are a couple of other problems with the recipe also, such as
that "@Read" would apply only to the very last regex ("lexisnexismail"),
not all of them (or maybe he wanted that?); and that he uses a lockfile
but says in his precatory statement to us that he wants deliver to
IMAP folders, which wouldn't need the lockfile. I also thought at first
glance that the "@Read" > >was a folder name (i.e., action line), but
it > is not.
Okay, I see the problem with it only applying to the very last regex, but
I don?t understand why you state that ?(_at_)Read? is not folder name. It was
meant to be. Is there a problem using the ?(_at_)? symbol as part of an IMAP
folder name? Or do you simply mean that because I used the wrong syntax,
it would not function as an action line? Since fixing the syntax per
Jeff?s and your suggestions, it now works, and I have other recipes
sending mail to folders whose names begin with ?(_at_)?, so I assume that you
meant the bad syntax made it not a folder.
So, theoretically, yes, this would work:
:0
* ^(From|Cc|To).*foo|\
^(From|Cc|To).*bar
/path/to/maildir/folder/
(I even tested it., though I was already convinced it would work.)
But does that only apply to the ?bar? regex? Or will it apply to ?foo? as
well?
But much better style is this (and btw note the colons):
:0
* ^(From|Cc|To):.*(foo|bar)
/path/to/maildir/folder/
Yes, much better. I had tried this first, but it didn?t work. I didn?t
have the colon after the ?(From|Cc|To)?. But I would also need a colon
after the ?:0? to lock the file (see below).
Of course, the admonishment to read the man pages still holds, and
especially "man procmailex" would prove to be useful to Paul E.
I?m humbly admonished.
There are a couple of other problems with the recipe also, such as
... that he wants deliver to IMAP folders, which wouldn't need the
lockfile.
We can't assume that. Under UW-IMAP folders are mboxes. The local
lockfile might be critical.
True. As a newbie, I am happy to be correct about something. I use Pair
Networks as my hosting service. Its IMAP daemon is a custom modification,
but mail is saved in standard mbox format. The tutorials and FAQs that
I?ve read (e.g. Infinite Ink www.ii.com) make it pretty clear that nasty
things can happen if you don?t put on the locks for these kinds of
recipes.
Again thanks for all your help. I?m starting to enjoy Procmail (as
opposed to cussing and kicking office furniture trying to make sense of
it). I just set up Clam Anti Virus and updated my Procmailrc file to work
with it. I?m actually looking forward to the next virus-infected e-mail.
____________________________________________________________
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