On Thu, 13 Jun 2002, Robert Adkins wrote:
I am also considering staying away from Procmail as the help provided
from this list is most often in the form above; cryptic commands listed
with no explanation as to why and how they do the things that they do.
What kind of help and assistance is that?
I'll explain the answer that I sent you:
1) :0 fhw
2) * ^TOprocmail
3) | sed 's/^Subject: /& [procmail]/'
1) :0 start recipe (rule)
f We are going to change the the message
h The part we are going to change is the header
w Take the consequences (wait, is every thing done? OK?)
2) * If you find the follow string then do the changes
^TO The string we are looking for is one of the addressed
procmail The string we are looking for
3) | Use the following command to change the header
sed .... Change the string "Subject" to be "Subject [procmail]"
Enough of that though, I will be getting into reading over the man
pages, *rc files and other pieces of Procmail soon, hopefully it will all
begin to make some sense.
I suggest you to scan and browse the man pages NOT read (and skip the
procmailsc man page). Read the egrep man page then go to NMTG web
site: http://www.ii.com/internet/robots/procmail/qs/ After this
steps back to the procmailex man page. After some experiments and FAQ
reading you can read the man pages (including the procmailsc (:-))
Since then we have used procmail to run antivirus on the unix mail
server we saved a lot of money/time and the users breathe a sigh of
relief.
Bye,
Udi
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail