* This is the modus mailing list *

Hi Ken,

I'll give you my results of running M3 also.

As Ronnie mentioned, we have not added a new sieve filter since we began
the beta.  In fact, we have actually disabled some of the scripts we
used before the beta.

THE SCA ROCKS!!  

While we have tested White and Black list functions, we have not
released these to the masses yet.  I did not want to do this in the
event there was any "modification" in the functionality or user
interface (which there was) in the release version.  They work well per
user.  We did not implement nor test either list "server wide".

Someone asked earlier about additional processing power requirements.
To my knowledge, each of the beta companies ran the beta on hardware on
the same, equal or in some cases even less powerful servers than we ran
M2 on.

Brace yourselves Vircom users - "something wonderful is about to
happen", it has for us already!  <grin>

Bill




-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Ken Grimes
Sent: Saturday, November 01, 2003 10:17 PM
To: [EMAIL PROTECTED]
Subject: [Modus] When is 3.0 due out?

* This is the modus mailing list *

While holding my breath for the November 3rd release, we have a few
questions for the beta testers if it doesn't violate their NDA's.
First, I
read from the list that the companies that are currently running the M3
setup have all experienced great results with filtering the spammers
known
techniques but are these due to the next generation Sieve filters or are
these the result of "server wide" whitelisting/blacklisting or
challenge/response?  If you answer to the first question is "yes", have
you
contacted all your customers to make them aware of the new
challenge/response system just to pre-warn them of the possible delays
in
message receipt?  Second question, of the companies and domains using
the
challenge response is there anyone whom has put together a list of
important
newsgroups that we could implement prior to customer complaints about
their
Yahoo Groups now not being received because of their non-response
capacity?
Thirdly, has anyone had experience with third party mail relaying with
regards to what additional functionality can you filter for these
servers?
In other words, in Modus 2.x we can select filtering of SPAM, VIRUS, or
ATTACHMENTS independently, will version M3 allow the additional the new
white/black or challenge/response options for relays?  Fourth, if you
have
implemented the challenge/response how does M3 perform with massive spam
attacks from the same IP if using different forged return addresses?  In
other words, if 20,000 messages come from 80.123.123.123 all with
different
forged return addresses will it perform challenges for each message or
will
it cache it's results and prevent wasted bandwidth by auto "identifying"
a
new spammers IP that may not be blocked by the RBL's yet.

Just curious about these in advance,
Ken Grimes




----- Original Message ----- 
From: "Mike Herrera" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, November 01, 2003 4:53 PM
Subject: [Modus] When is 3.0 due out?


> * This is the modus mailing list *
>
> We see fewer false positives now than when we were using Modus 2 along
> with spamassassin!  The nice thing is that users will be able to go
into
> their quarantines and check for them and can add them themselves to
> their whitelist.
>
> MikeH
>
>
> ---- 
>
> I'm not a complete idiot, some parts are missing!
>
> Mike Herrera
> Access One Online Services
> http://www.access-one.com
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Robert Sinclair
> Sent: Saturday, November 01, 2003 4:40 PM
> To: [EMAIL PROTECTED]
> Subject: [Modus] When is 3.0 due out?
>
>
> * This is the modus mailing list *
>
> What about false positives? How well is it handling those?
>
> ----- Original Message ----- 
> From: "Mike Herrera" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, November 01, 2003 12:58 PM
> Subject: [Modus] When is 3.0 due out?
>
>
>
> **
> To unsubscribe, send an Email to: [EMAIL PROTECTED]
> with the word "UNSUBSCRIBE" in the body or subject line.


**
To unsubscribe, send an Email to: [EMAIL PROTECTED]
with the word "UNSUBSCRIBE" in the body or subject line.


**
To unsubscribe, send an Email to: [EMAIL PROTECTED]
with the word "UNSUBSCRIBE" in the body or subject line.

Reply via email to