On Saturday, June 30, 2012 at 11:00:54 UTC, mar...@gregorie.org confabulated:
> On Fri, 2012-06-29 at 22:48 -0700, Jayanta Ghosh wrote:
>> Dear List,
>>
>> We are trying to configure Spamassassin (Version 3.3.1-2) with postfix
>> (Version 2.6.6-2.1) on RHEL 6.1 (64 bit). In order to integrate postfix with
>> Spamassassin We did the following changes in the master.cf file :-
>>
>> We added "-o content_filter=spamassassin" to the following line
>> smtp inet n - n - - smtpd -o
>> content_filter=spamassassin
>>
>> We also added the following lines at the end of master.cf
>> spamassassin
>> unix - n n - - pipe
>> flags=R
>> user=spamuser
>> argv=/usr/bin/spamc
>> -e /usr/sbin/sendmail
>> -oi -f ${sender} ${recipient}
>>
> Don't use both spamassassin and spamc:
> - running 'spamassassin' causes it to load, initialise, scan the
> message, and quit. This is done each time a message is received by
> Postfix and so is relatively slow because spamassasin is written in
> Perl and is quite big.
> - calling spamc, a lightweight C program makes it pass the message to
> spamd, a server, for scanning. spamd is a copy of spamassassin that is
> loaded at boot time, so has much less overhead than loading and
> running it against each message.
> Make up your mind which you're going to use, fix that configuration and
> remove the one you don't use.
> - Are you sure your spamassassin configuration is OK?
> - What does 'spamassassin --lint' tell you?
> - If you run known spam through 'spamc <spam.mbox' or
> 'spamassassin <spam.mbox' is it getting marked as spam?
> What about known ham?
> You should be able to do this as any user.
The OP is just using spamc. If memory serves, the tests the OP was
performing were from the server spamassassin was installed on.
Therefore, the spam score will be on the negative side instead of a
positive number.
--
If at first you don't succeed...
...so much for skydiving.
