I took those examples right from one of the links off the procmail
homepage. I didn't create them and when I was testing I did have
verbose=yes. nothing different happened at all. There is no
"BLACKLIST=$HOME/.killfile" under my ~/mail dir.
I will test and let you know. Thanks
Gary Funck wrote:
From: BlkPoohba
Sent: Tuesday, December 30, 2003 2:16 PM
PMDIR=$HOME/.procmail
LOGFILE=$PMDIR/killfile
Did you look in your logfile? (and "killfile" is not the most intuitive name
for a log file).
VERBOSE=no
While you're debugging things, VERBOSE=yes might be better.
MAILDIR=$HOME/mail
:0
BLACKLIST=$HOME/.killfile
That's going to deliver all your mail into a file named:
"BLACKLIST=$HOME/.killfile". Do an 'ls' under $HOME/mail.
See "man procmailrc". Here's what a recipe looks like:
:0 [flags] [ : [locallockfile] ]
<zero or more conditions (one per line)>
<exactly one action line>
Just remove that :0 line, so that you have:
BLACKLIST=$HOME/.killfile
on its own, somewhere before you need it.
:0
*$ ? test -s $BLACKLIST
* ? (formail -x From: -x Reply-To: -x Sender: -x From | fgrep -iqf
$BLACKLIST)
/dev/null
This looks fine. But while you're testing, you might want to dump it
into spam.mbox or some such. In fact, after you're done testing this is
still a good policy. Sometimes you'll find that your blacklist patterns
are two general. especially since you're looking for a match anywhere
within the various fields mentioned in your formail command.
i also have
LOCKEXT=.lock
:0 Whic :$BLACKLIST$LOCKEXT
| (formail -x received: -x X-Envelope-From: -x from: -x sender: -x
reply-to: -x$
Was the line above truncated?
_______________________________________________
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