<html>
<head>
<style type="text/css">
<!--
body { margin-bottom: 1px; margin-right: 4px; font-variant: normal; margin-left: 4px; margin-top: 4px; line-height: normal }
-->
</style>
</head>
<body style="margin-bottom: 1px; margin-right: 4px; margin-left: 4px; margin-top: 4px">
<DIV>
Has anyone used MailScanner?
</DIV>
<DIV>
www.mailscanner.info
</DIV>
<DIV> </DIV>
<DIV>
It is not a SMTP Proxy and it will use any AV software and will also check the RDBs. I have
</DIV>
<DIV>
SpamAssassin hooked into mine and it works a treat!!
</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> <br><br>Regards,<br>Andrew Barbara<br> <br>FocusNet I.T. Consulting<br>0433 124 852<br>andrew@focusnet.com.au<br><br><br>>>>bernie@innovative.iinet.net.au 10/14/04 12:20 am >>>
<DIV> </DIV>
<DIV> Craig Ringer <craig@postnewspapers.com.au> writes:
<DIV> </DIV>
<DIV> </DIV>
<DIV> >Bernd Felsche wrote:
<DIV> </DIV>
<DIV> </DIV>
<DIV> >>Amavis would be top of my charts. The commercial AntiVir version
<DIV> </DIV>
<DIV> >>works well as a content filter with postfix. I have it running
<DIV> </DIV>
<DIV> >>that way at one "site" (actually a number of servers throughout
<DIV> </DIV>
<DIV> >>Australia).
<DIV> </DIV>
<DIV> </DIV>
<DIV> >OK, I'll have to look into that. I see those two amavis variants
<DIV> </DIV>
<DIV> >coming up quite a bit, though I was unaware there was a commercial
<DIV> </DIV>
<DIV> >variant.
<DIV> </DIV>
<DIV> </DIV>
<DIV> Well; commercial "plugin" is probbaly closer to the mark.
<DIV> </DIV>
<DIV> </DIV>
<DIV> As I understand it, amavis can use a variety of content scanners.
<DIV> </DIV>
<DIV> </DIV>
<DIV> >>The anti-virus and anti-spam scanners all seem to require one
<DIV> </DIV>
<DIV> >>instance per message. That's the simple method of implementation and
<DIV> </DIV>
<DIV> >>intuitively; the most secure.
<DIV> </DIV>
<DIV> </DIV>
<DIV> >What about SpamAssassin's spamd, and clamav's clamd? My
<DIV> </DIV>
<DIV> >understanding is that both of those used the Apache 1.x daemon
<DIV> </DIV>
<DIV> >service model, rather than strict one-helper-per-job. I could have
<DIV> </DIV>
<DIV> >easily missed something though.
<DIV> </DIV>
<DIV> </DIV>
<DIV> So could I! :-)
<DIV> </DIV>
<DIV> </DIV>
<DIV> Frankly; I'd rather not have a daemon left in a state by a previous
<DIV> </DIV>
<DIV> message.
<DIV> </DIV>
<DIV> --
<DIV> </DIV>
<DIV> /"\ Bernd Felsche - Innovative Reckoning, Perth, Western Australia
<DIV> </DIV>
<DIV> \ / ASCII ribbon campaign | I'm a .signature virus!
<DIV> </DIV>
<DIV> X against HTML mail | Copy me into your ~/.signature
<DIV> </DIV>
<DIV> / \ and postings | to help me spread!
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> PLUG discussion list: plug@plug.linux.org.au
<DIV> </DIV>
<DIV> http://mail.plug.linux.org.au/cgi-bin/mailman/listinfo/plug
<DIV> </DIV>
<DIV> Committee e-mail: committee@plug.linux.org.au
</body>
</html>