Well, I've solved the problem I previously reported, that being the fact that some (not all) of my "whitelisted" messages still get tagged as spam, even though the user_prefs file is being read (see my previous message to the list which displayed a header which, despite having -94.4 points, still was tagged as spam, and the message modified).
The problem appears to be that spamd runs as root...spamc runs as the user. It appears that the user's user_prefs file is read (hence its entry in the header) but the message is processed as root, using root's user_prefs file. This happens with about half of the messages from whitelisted senders. The rest of the messages are processed correctly. Odd. I was able to kluge it by copying a user_prefs file for root that has most of the users' whitelists in it (there are no longer any mis-tagged messages), but obviously this removes users' control over their own whitelists. I believe the problem can be fixed by allowing spamd to run as the user, rather than root (this would also get rid of the "falling back to nobody" messages in the logs. I haven't looked through the source, and I'm not a Perl programmer, so will leave the details to the maintainers. Just thought I'd toss this out for discussion. -- Bob -- ____________________ Bob Sully Malibyte Consulting Simi Valley, CA, USA www.malibyte.com "Years of dedication, and a natural inclination." - J. Buffett ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek PC Mods, Computing goodies, cases & more http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
