Sujit Choudhury wrote: > > I am having problem understanding how spamd works after sa-update was > introduced after I upgarded to the latest version of SpamAssassin. > sa-update puts the files into /var/lib directory. However, spamassassin > -D --lint shows the files are read from /var/lib directory where as spamd > program in actual fact points to /usr/share/spamassassin. >
In my case its the other way around. My spamassassin read config files from /usr/share/spamassassin and /etc/mail/spamassassin Well, and I have no idea what files are read by spamd. Perhaps the /var/libs ... *lol* Strange world... I'll test it later in the afternoon. > My SARE rules and other local rules are in /etc/mail/spamassassin which > shows up in spamassassin -D --lint correctly. > >>> Spamassassin itself workes correctly, so I guess that I don't need the >>> params for spamassassin, but for spamd. > > What do you mean by this? > > I tried to say, that I have to deal with the problem concerning the spamd and not spamassassin. Spamassassin workes like i've expected it. The Spamd is a pain in my neck... *grrr* ;) Thanks ... -- View this message in context: http://www.nabble.com/Spamd-and-Spamassassin-filtering-differently-tf2781676.html#a7771363 Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
