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

Jason J. Ellingson wrote:

>ASSP is great and I applaud anyone using it...
>
>ASSP is easier to set up and use than SpamAssassin.  I won't argue that.
>
>However, SpamAssassin offers everything ASSP does and more.
>
>In your post:
>
>  
>
>>>It (ASSP) is far more efficient since it handles the SPAM check in the
>>>      
>>>
>SMTP session then closes it after a specified number of bytes
>
><< SpamAssassin does the same.  You insert your SpamC filter into Post-SMTP
>and it will only check messages smaller than a specified size you can set.
>You can also avoid running the filter for authenticated users (!aex).  The
>filter as well as SpamD has timeouts and triggers to return spam-identified
>messages instantly when it scores high enough to be spam.
>
>  
>
>>>It (ASSP) has far more options (RBL, filters, domain blocking,
>>>      
>>>
>whitelisting, etc.)
>
><< So does SpamAssassin.  You can use all the RBLs you like, enable disable
>filters to your heart's content, add domains, email addresses, IPs, etc to
>blacklists, and whitelists.
>
>Please, I don't mean to start a flame war.  Please read the following which
>I think is fair:
>
>ASSP is great!  Simple to install and use - Great for novices and experts
>alike!
>
>SpamAssassin is great! Slightly more powerful, but a lot more work to
>install and use - Not for novices!
>------------------------------------------------------------
>Jason J Ellingson
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
>Behalf Of Jeff Buehler
>Sent: Thursday, September 08, 2005 7:12 PM
>To: [email protected]
>Subject: [xmail] Re: stopping spam
>
>
>I would look more closely at what is causing the problem with ASSP and 
>continue to use that.  I like it much better than Spam Assassin myself, 
>at least for use with XMail.  It is far more efficient since it handles 
>the SPAM check in the SMTP session then closes it after a specified 
>number of bytes, and it has far more options (RBL, filters, domain 
>blocking, whitelisting, etc.).
>
>Jeff
>
>Eric Garnice wrote:
>
>  
>
>>On 9/8/2005 5:16 PM Jason J. Ellingson wrote:
>> 
>>
>>    
>>
>>>I have run SpamAssasin on Windows servers (both with ActivePerl and
>>>      
>>>
>CygWin)
>  
>
>>>and Linux servers.  Running SpamAssassin on Linux (or other unix) runs
>>>      
>>>
>much
>  
>
>>>faster and more reliably than on Windows.
>>>
>>>I run XMail on a Windows server and SpamAssassin on a Fedora Core 4
>>>      
>>>
>server.
>  
>
>>>Works like a charm.  I wrote a SpamC filter for Windows XMail Post-Data
>>>filter to use.
>>>
>>>If you are really limited to just one box, then you should try to run
>>>SpamAssassin using CygWin so you can make full use of DCC, Pyzor, Razor
>>>      
>>>
>and
>  
>
>>>such.  I still have an out-dated (but useful) page hidden on my server
>>>      
>>>
>that
>  
>
>>>might help you...
>>>
>>>http://www.yourtech.net/documents/cw-sa/
>>>
>>>I will (someday) write step by step instructions for install XMail for
>>>Windows, XMail-WAI (webmail and admin) for Windows, and SpamAssassin for
>>>Fedora Core 4.
>>>
>>>If you do decide to try Fedora Core 4, use YUM to install SpamAssassin.
>>>It'll give you a startup script for SpamAssassin and install it as a
>>>service.  Also note that SpamAssassin doesn't run under root account...
>>>you'll need to create an account for it to run under... I named mine
>>>      
>>>
>"spamd"
>  
>
>>>------------------------------------------------------------
>>>Jason J Ellingson
>>>   
>>>
>>>      
>>>
>>To my knowledge (and I have done some searching in the past), no one has 
>>developed a decent XMail filter for SpamAssassin in serial mode on Windows.
>>
>>At work I'm forced to run my XMail relay directly on the Exchange server 
>>and use Dario's XSpamC to call SpamAssassin on Fedora PPC on a Mac G4. 
>>It's been flawless for over a year now.
>>
>>I don't think Digerati is going to find exactly what he's looking for.
>>
>>- Eric
>>
>>-
>>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]
>>
>>
>> 
>>
>>    
>>
>
>-
>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]
>
>
>
>-
>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]
>
>
>  
>

-
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]

Reply via email to