Yes, you need to restart spamd after system-wide config changes. Only per-user config files are read when processing each individual message.
C Nevin Kapur wrote: NK> Date: Tue, 09 Apr 2002 14:14:07 -0400 NK> From: Nevin Kapur <[EMAIL PROTECTED]> NK> To: [EMAIL PROTECTED] NK> Cc: [EMAIL PROTECTED] NK> Subject: Re: /etc/mail/spamassassin/ not being read? NK> NK> Craig R Hughes <[EMAIL PROTECTED]> writes: NK> NK> > Almost for certain it's a file permissions problem. Check that /etc/mail NK> > /etc/mail/spamassassin and /etc/mail/spamassassin/local.cf are readable by the NK> > process that spamd is running as. Generally, there's absolutely no reason not NK> > to make the directories 755 and the .cf file 644 NK> NK> I was just in the middle of posting a followup with a the resolution NK> to my problem. The problem is not with the permissions. NK> NK> We have spamd running over here and I did not restart it after making NK> a local configuration change. Would this explain the behavior I NK> described? Restarting spamd fixed the problem for me. NK> NK> > Nevin Kapur wrote: NK> NK> [...] NK> NK> > NK> However these options are not being honored. If I add the same set of NK> > NK> rules to ~/.spamassassin/user_prefs then they do get honored. NK> NK> _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
