1. 'touch ~/pm.log' 2. Put this at the top of your .procmailrc: LOGFILE = $HOME/pm.log LOGABSTRACT = "all" VERBOSE = "on"
That will log relevant information about what procmail is doing with your email. :-) Can be quite useful. --Tomki At 13:25 10/03/2002 -0400, Dan Simoes wrote: >After realizing that a system wide install for a busy mailing list >server was not a good idea, I decided to try it on a per-user basis. >Here's where I'm at, help greatly appreciated. > > > cat .forward >"|IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #dans" > > > cat .procmailrc | grep -v ^# >:0fw >* < 256000 >| /usr/local/bin/spamassassin > >Spamassassin works, and most mail is being delivered, but it seems that >some is not (I can't sure). I think spamassassin is working, as it >inserts the header: >X-Spam-Status: No, hits=0.0 required=5.0 tests=none version=2.41 > >Into every message. > >When I run the test spamassassin -t < samplespam > spam.out >it clearly works and marks the subject line. > >The best I can figure is that when run via .forward and procmail, it's >not seeing the spamassassin libraries perhaps? > >The system is solaris 2.6 running postfix. > >Thanks! > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Spamassassin-talk mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/spamassassin-talk Tomki Camp Project Manager A-Link Network Services 408.720.6162 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
