On Thu, 14 Nov 1996, Tony Nugent wrote:
Many, many thanks for ...
You're welcome.
Yes, but that will deliver messages that match the rule according to
the recipe, but won't procmail still process the message after this
point so that a copy will still end up in the default mailbox file?
This is what was happening when I was experimenting with this sort of
format.
Procmail will stop processing after a delivering, non-copy, non-filtering
action is successful.
:0
* ^(From |(Cc|To):(.*[^a-zA-Z0-9._-])?)linux-kernel-digest
* ^Subject:.*#\/[0-9]+
One question... I assume that the recipe is executed if BOTH
conditions are true - yes? (That is, the conditions are AND'ed).
Yes. Conditions in a recipe must all match for a recipe action to be
processed. The 'A', 'E', 'a', and 'e' flags impose other conditions
as well. See the procmailrc man page.
:0fBW # do signature cleanup if needed
:0fBW # do PGP cleanup if needed
If needed? Hey, this is looking like a very nice way to do things :)
:0: # finally, burst the digest and deposit
| formail -i"Sender:
owner-linux-kernel-digest(_at_)vger(_dot_)rutgers(_dot_)edu" -Yds >>
$KDIGEST
}
Yeah, but even if the mail is delivered, then won't procmail still
continue to process the message, as I mentioned above? (I'll
certainly end up discovering for myself exactly what happens:)
No. If the action (formail in the example above) succeeds, then
procmail will consider the mail to be delivered, and stop processing of
the recipe file.
:0
mhfolder1/. mhfolder2/. mhfolder3/.
Huh? I did notice something like this, but it doesn't make sense...
won't duplicates be dropped into the different folders/directories?
No. When filing to directories, procmail will make hard-links to
multiple directories.
NOTE: It is an unfortunate inconsistency that procmail will allow
filing to multiple directories, but *NOT* to multiple file-folders.
Sad but true.
I did try something like that but it didn't work with redirection
after a filter (you can't append to a directory entry :) What I was
looking for was a way to put the digested messages exploded mh-style.
I've played with rcvstore and it seem that this will do the job very
nicely with me.
Using rcvstore in a procmail filing recipe is unecessary -- and
rcvstore cannot file to multiple folders; even if you think it is
useful for keeping your "Unseen-sequence" up to date, it isn't
guaranteed to be reliable, according to its own man page.
One question for now though... do you know where I can get the 6.8.4
version of mh? And do you know if it will compile and work ok under
linux?
Check at ics.uci.edu.
Ok, two questions :) Is there a mailing list for mh?
Yes: mh-users(_at_)ics(_dot_)uci(_dot_)edu(_dot_) Try subscribing at
mh-users-request(_at_)ics(_dot_)uci(_dot_)edu(_dot_)
(From Ebisu, Japan)
___________________________________________________________
Alan Stebbens <aks(_at_)sgi(_dot_)com> http://reality.sgi.com/aks