Here is my .procmailrc: SHELL=/bin/sh VERBOSE=yes LOGFILE=/home/scott/proc-debug.log DEFAULT=/var/mail/scott SPAM=/home/scott/Spam /usr/bin/spamc
:0bc:pager1$LOCKEXT * ^Received:.*wunderground.com | /home/scott/wx/warndir/storm-date :0: * ^X-Spam-Flag: YES $SPAM Here is a sample from the log file: procmail: Assigning "DEFAULT=/var/mail/scott" procmail: Assigning "SPAM=/home/scott/Spam" procmail: Skipped "/usr/bin/spamc" procmail: No match on "^Received:.*wunderground.com" procmail: No match on "^X-Spam-Flag: YES" procmail: Locking "/var/mail/scott.lock" procmail: Assigning "LASTFOLDER=/var/mail/scott" procmail: Opening "/var/mail/scott" procmail: Acquiring kernel-lock procmail: Unlocking "/var/mail/scott.lock" Ideas? Notice the "skipped" line above. Thanks. Scott On Sun, 30 Nov 2003, Tom Allison wrote: > Scott Ehrlich wrote: > > Well, the link to > > http://dman13.dyndns.org/~dman/config_docs/exim-spamassassin/node11.html > > was helpful, but my email, I've discovered, is not properly getting > > spam-tagged. > > > > I sent myself spam email from another account and it was getting caught, > > but I didn't realize the other account had spamassassin running and was > > tagging the email, thus the false impression when I redirected it to my > > home account. > > > > So now, I have exim 3 updated with the rules, but don't know what add next > > (exim.conf and/or .procmailrc) to actually tag email. > > > > I've tried adding /usr/bin/spamc at the top of my .procmailrc but that did > > nothing. > > > > Any additional help would be appreciated. > > > > Thanks in advance. > > > > Scott > > > > > > > Set the logging to verbose=yes and see what the logs tell you. You > should get a procmail log entry for every statement that the email hits, > including filtering line (* [EMAIL PROTECTED]) and > executables (| /usr/bin/spamc). > > If you have the logging turned on, the procmail logs will indicate that > it ran spamc and the results may also be posted depending on the > logging/debugging level you have spamassassin set to. > > Whenever debugging, turn everything up a high debug level and work your > way down from there. > > It is a ton of data coming off into the logs, but you need that when > you're in the dark. > > Start with that. If spamc/spamd is running, it will tell you. If > something is failing in the code and quiting early, it will tell you. > If it succeeds, it will tell you with the resuling scores, time to > complete, blah..blah..blah.. > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
