> How do you *call* SpamAssassin, how have you configured the software that
> calls it and SA itself? By default, SA adds X-Spam-Checker-Version,
> X-Spam-Level, and X-Spam-Status headers to all mail, and X-Spam-Flag: YES to
> spam. Those lines seem to be added by some other software. It wouldn't
> surprise me if the first line was in the spam to begin with, as a lame
> attempt to bypass spam checking.
>
i'm using Java Enterprise System Messaging Server with "internal"
configuration. its similar to master.cf configuration in postfix.
maybe this can help:
[mercurio:/]# ps -ef | grep spam
mailsrv 2020 18464 1 15:39:43 ? 2:55 /opt/csw/bin/perl
-T /opt/csw/bin/spamd -d -s /var/log/spamd.log -u mailsrv
root 18464 1 0 13:31:39 ? 0:41 /opt/csw/bin/perl
-T /opt/csw/bin/spamd -d -s /var/log/spamd.log -u mailsrv
root 5887 5824 0 16:15:06 pts/2 0:00 grep spam
mailsrv 2019 18464 2 15:39:43 ? 7:19 /opt/csw/bin/perl
-T /opt/csw/bin/spamd -d -s /var/log/spamd.log -u mailsrv
now you confirm me that every message should have headers i must
identify why not all messages are filtered.
> That is possible, yes. It can also be that the messages are too big (over 250
> kB, usually). But again it depends on how SA is called.
>
ok, i think size is not the problem in this case.
--
àngel bosch
Departamento de Servicios y Proyectos
Brújula
T. +34 971 433 909 - F. +34 971 433 910
www.brujula.es
___________________________
En el corazón de su negocio
