found it ... I had another procmailrc file in /etc ... I was trying something else a little while ago and for got about it.
Thanks for the help. I have another question, but I will make a new post. Peter -----Original Message----- From: Peter Marshall [mailto:[EMAIL PROTECTED] Sent: Thursday, February 03, 2005 10:38 AM To: Matt Kettler; users@spamassassin.apache.org Subject: RE: spamassassin scoring message twice Here is my .provmailrc file #Spamassassin start :0fw | /usr/bin/spamc #Spamassassin end ~ And I run this from /etc/init.d/spamassassin # Source function library. . /etc/rc.d/init.d/functions # Source networking configuration. . /etc/sysconfig/network # Check that networking is up. [ ${NETWORKING} = "no" ] && exit 0 # Source spamd configuration. if [ -f /etc/sysconfig/spamassassin ] ; then . /etc/sysconfig/spamassassin else SPAMDOPTIONS="-d -c -m5 -H" fi [ -f /usr/bin/spamd -o -f /usr/local/bin/spamd ] || exit 0 PATH=$PATH:/usr/bin:/usr/local/bin # See how we were called. case "$1" in start) # Start daemon. echo -n "Starting spamd: " daemon spamd $SPAMDOPTIONS RETVAL=$? echo [ $RETVAL = 0 ] && touch /var/lock/subsys/spamassassin ;; stop) # Stop daemons. echo -n "Shutting down spamd: " killproc spamd RETVAL=$? echo [ $RETVAL = 0 ] && rm -f /var/lock/subsys/spamassassin ;; -----Original Message----- From: Matt Kettler [mailto:[EMAIL PROTECTED] Sent: Thursday, February 03, 2005 9:58 AM To: Peter Marshall; users@spamassassin.apache.org Subject: Re: spamassassin scoring message twice At 08:36 AM 2/3/2005, Peter Marshall wrote: >I am not sure why it is doing this ... but everytime i get a spam, it looks >like it does the smap rateing twice. And it gives different scores each >time. Here is the new header from the last email I got. Notice how it >looks like spamassassin ran twice. Any Idea's ??? (yes, my threshhold is >low ... i am just testing what happens when spam arrives). From the looks of it, you are feeding the mail to SA twice. How do you have SA set up? What tools do you use? are you using both a milter and a call in procmail? Try to figure out where SA is being called, and pick one method. As for the different scores, that's not surprising. Since you're using encapsulation, the first time the message is scanned and marked as spam, it's encapsulated in a new message with new headers. This means the second time around the headers are different. It also looks like you suffer from the ALL_TRUSTED mis-matches caused by having a NATed mailserver.. you might want to look at setting trusted_networks manually to fix that.
