v4.85.1.0 Beta for Linux RPM Available

Peter Bonivart bonivart at opencsw.org
Wed Feb 18 18:46:12 GMT 2015

On Wed, Feb 18, 2015 at 5:18 PM, Rick Cooper <rcooper at dwford.com> wrote:
> This applies to SpamAssassin as well. I sent Jules code to move MailScanner
> to use the Spamd process years ago. Now the clamav module had a lot of
> issues because when internal defs within the clam code changed the module
> would puke until someone patched the module but it makes no sense to me why
> anything MailScanner shares should be based on a perl module if there is a
> daemon available to communicate with. Spamd protocol is pretty simple and
> fairly easy to integrate within MailScanner. The difference in speed is
> pretty much nil but the difference in MailScanner memory usage per child is
> significant. When I originally worked with JF to integrate the clamd code
> his biggest hesitation was he wasn't comfortable with network code... I
> would bet that was the biggest reason for handling postfix the way it's
> handled as well. Whoever is currently developing MS should really look at
> moving toward spamd support in place of the perl module

That's still a great idea, I remember it from back in the day.
However, I think it's high time to close the wish list for this long
awaited release and start filling it for the next one or we may have
to wait a few more years. :)


More information about the MailScanner mailing list