The perl filter you used for *BSD probably used the serial version of SpamAssassin. SpamC is a "drop-in" replacement for the SpamAssassin calls. SpamD *is* SpamAssassin but running all the time. The slowness you experienced was because SpamAssassin takes a while to load up before running. SpamD is always running, so you avoid the start-up time.
SpamAssassin has no SMTP connection. It is still run by passing a file to it (spamc < msg.txt). I prefer not to use a relaying spam checker because it can't verify the end user in some configurations (such as the mail server running on a different machine). I'd be happy to help anyone get SpamAssassin up and running so they can compare it to ASSP. I'm most comfortable with setting up SpamAssassin in CygWin for Windows, SuSE Linux 9, and Fedora Core 4, but I think I can help with other configurations. I can help with plugging it into Exchange Server and XMail as native filters, or by using eWall (in line transparent proxy) to allow it to work with mail servers that don't support plug in filters. ------------------------------------------------------------ Jason J Ellingson -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Buehler Sent: Thursday, September 08, 2005 8:12 PM To: xmail@xmailserver.org Subject: [xmail] Re: stopping spam Ah - I was only referring to a Spam Assassin filter I sued with XMail, and in my case as of about a year ago (the last time I set it up and used it). Glad that it has all of those features now - it didn't that I was aware of then. No danger of flame at all - I like dialog about this stuff - it helps me clarify my own direction and make changes if better options are out there. However, with respect to efficiency, you mention that to use Spam Assassin in these ways requires a significant investment not only time to install, but also in hardware. This is largely what I was referring to when I mentioned ASSP - it is robust, easy to install, extremely powerful and configurable AND there is no reason to run it on separate platform because it isn't a memory or a CPU hog, and it is fast. I have yet to try ALL of the Spam Assassin apps you comment on (SpamC, SPamD, etc.) - when I ran it under FreeBSD it was simply a perl filter in XMail and SpamD running (I vaguely recall RBL through Razor or some name like that). At the time, it was really slow, but there was no SMTP session handling, so I'm glad that has been introduced. In my case, I run ASSP -> ClamSMTPD (effective and thorough antivirus) -> XMail (and for some clients -> Exchange). This has proven to be simple, robust and effective, and I know the Windows implementation is straightforward from the mail list (even though I don't use Windows internally). It sounds like Spam Assassin is a pain under Windows (I find Cygwin to be a bit of a pain myself and try to avoid it - why use it at all for a operate platform - just run Linux or *BSD). So my recommendation still remains ASSP - Digerati has used it, it is easy and works well, so all that is required is finding out why it was failing on his system, which the ASSP mail list would help with quickly. Jeff - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
