Just upgraded to SA 2.43 from 1.6 (I know....really out of date). Noticed a couple of odd things. We're running spamd and calling spamc (with -f) from qmail-scanner version 1.12.. Looking through the logs it appears that everything is working perfectly. Here's the first oddity. Mail from outside our domain is checked by SA (has X-Spam-Status header). Mail that comes in to this system and forwarded out to other systems is scanned by SA (has header). However, it seems that mail from someone inside our domain ([EMAIL PROTECTED]) to someone else at our domain ([EMAIL PROTECTED]) does NOT get scanned by SA (no header). Ths should be ok as long as none of our users start spamming. :-) Just thought it was a little odd. This was not the case with other versions of SA. Any ideas on that one?

Now for the important problem. To be honest I'm not sure if this is a SA issue or something weird with qmail-scanner. After about 30 minutes or so of running version 2.43 of SA mail started backing up terribly. Shortly after that delivery stopped all together. Just before I stopped qmail there were about 50 each qmail-smtpd and spamc processes running (very unusual for this system). Just to help narrow down what exactly was causing the problem I moved SA 2.43 out of the way (including all the rules files) and reinstalled 1.6. All is well again. As I said I'm not totally convinced this is a SA problem but I know lots of people have this same setup so thought I'd ask. Thanks for any help. If there is any other information I can provide that would be helpful just let me know.

Daniel
[EMAIL PROTECTED]





-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to