Let me try to be more specific. Before I put procmail in place as a
filter/delivery agent, I was using a standard local delivery agent,
slocal, from SCO. SCO used to run a version of mmdf as the MTA and when
they graduated to using sendmail, they built their sendmail to allow users
to continue using the ".maildelivery" file as a personal filtering system.
It is of course limited in what it can do. procmail is far better as I'm
finding, but there are some issues I can't seem to resolve. The reference
to .forward'ing simply meaning that this is how I get the incoming message
to procmail. Before I did this, .maildelivery handled depositing mail list
messages into appropriate folders. I'd like to avoid having to write a new
recipe entry for every list I subscribe to and thus would rather have the
existing .maildelivery file continue to handle it, if possible.
Hope that clarifies and helps.
Thanks for the other info here. I can use that right away.
--p
On Mon, 17 Dec 2001, Professional Software Engineering
wrote:
At 12:09 2001-12-17 -0500, peter(_at_)compclass(_dot_)com wrote:
I have searched through about every piece of FAQ and doc I can find but I
cannot find an answer to this question. I want to be able to have a
.maildelivery (prior to .forward'ing to procmail was working fine) process
messages in addition to procmail.
I don't follow that you're saying that "prior to .forward'ing ... was
working fine". What config were you running prior to forwarding?
If you want to do something with a copy of a message, you could simply so
something like:
:0ci
|maildelivery-program
(provided that the maildelivery program just take the message on stdin)
I'd also appreciate a quick recipe suggestion to have a message body
string like "thisword" cause this message to get dumped into the trash.
:0:
: B ?? thisword
trash
(test before changing trash into /dev/null - at which time you can remove
the lockfile flag)
Scanning every message body for "thisword" isn't going to be "quick" though.
---
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
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail