a) SpamAssassin, although it seems it keeps on scanning emails, it stopped writing them to "/var/spool/mail/lixo" directory.
SpamAssassin never wrote mail there in the first place.. your MDA did that (presumably procmail).
b) In the other hand we realized that SpamAssassin started, at the same time, to write them to a directory called "spam", at a path "/var/spool/MailScanner/quarantine/2004/0823/spam". And it writes them there with no pontuation / rules , etc.
MailScanner does do this. SpamAssassin doesn't write mail to files at all.
c) The third remark is that we also realized that SpamAssassin stopped writing Spam emails to the "/var/spool/mail/lixo" and instead writes them to "/var/spool/MailScanner/quarantine/2004/0823/spam", but only when we start MailScanner.
1) Why did SpamAssassin, which was working fine, all of a sudden, start writing to "/var/spool/MailScanner/quarantine/2004/0823/spam" instead of to "/var/spool/mail/lixo" ?
This is a MailScanner behavior.. see your mailscanner.conf, spam action is probably set to "quarantine".
Spamassassin itself does not, and can not, write mail anywhere, so what directory mail gets written to is entirely out of it's control. Although tools like MailScanner, procmail, etc can be influenced by SpamAssassin's decisions, SA itself has no direct control over such things.
2) Why does MailScanner affect it and how to solve this, that is, how to have SpamAssassin and Mailscanner as well, working normally together again?
-set up your mailscanner.conf the way you want it -enable the "use spamassassin" option in mailscanner. -disable any other references to spamassassin (ie: in procmail)
follow up any problems with mailscanner configuration on the mailscanner mailing list (see www.mailscanner.info for details on the list under the heading "
Mailing Lists"
).
