> ----------- > > [b.] Because of the above problem, I am using a .procmailrc of; > > :0fw > |/home/user/bin/spamassassin/spamassassin -P -c > /home/user/bin/spamasssassin/rules > > The paths will be changed once I install it globally. However at the moment > it doesn't seem to doing AWL properly. With spamd you can pass the option to > use autowhitelisting, but 'spamassassin -P' doesn't have this option, or > seem to use it. It also creates an empty ./spamassassin/user_prefs file > instead of using the template. > 'spamasssassin -P' also doesn't seem to have any method of not processing > messages over a set size. >
I've just solved this problem minutes after posting. The '-a' option for spamassassin isn't documented other than in the README, (ie not in spamassassin.html). I'm still not sure whether 'spamassassin -P -a -c' will limit the size of files it will process though. My problem with spamd under Solaris (problem [a]) also still stands. -Thanks, Shane. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
