Bryan Hoover <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: > >> I have listed a number of whitelist entries in my user_prefs file. >> >> Regardless of an identifying header being listed in the whitelist, >> spamassassin still marks some mail which should be protected by the >> whitelist as spam. >> >> And there seems to be no constant rule for when it will mark or not >> mark spam despite entries in the whitelist. > > I just discovered that in some instances, I was copying my user_prefs to > the wrong directory, instead of .spamassassin (he sheepishly offered, > adding confussion to an already confusing situation). Unfortunately, I > didn't check the contents of .spamassassin/user_prefs before I overwrote > it. > > Are you sure yours is not some such problem? >
Here is another factor I've found to be true, maybe someone can comment if its off the wall. I suspect from my observations that if you have a bad rule or wrong syntax in one of the files spamassassin reads for config, it might trash other parts of the same config file which then may behave different than expected. I'm having a hellish time trying to figure out where spamd writes the debug log data.. Seems it should appear in syslog output, but the only messages I see are when I restart spamd, whereas with spamassasin instead of spamd, it leave lots of debug info in procmail.log file. I'm running spamd like this: spamd -d -D -L -S Using the standard procmail method, where should I find any logs that indicate a problem with any config files. They don't seem to appear in syslog output nor in procmail.log. _______________________________________________________________ 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
