Re: Problem with Spamassassin since upgrade (permissions)
On Wed, 28 May 2014, Bob Proulx wrote:
> Probably no one is running amavis-new plus spamassassin plus getting
> that message. I am not.
The recommended way to plug spamassassin into amavisd-new is to NOT use
spamd.
amavisd-new integrates a lot better over the perl module API to spamassassin
(it loads up spamassassin as if it were a library/module, inside the same
child process as the amavisd-new worker).
OTOH, the per-process memory penalty of amavisd-new can get quite high.
YMMV. I've never seen a high-volume/high-performance amavisd-new+SA install
that used spamd, though.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
Reply to: