[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Content filtering



El 9 May 2003 a las 14:43, Eino Tuominen escribió:

> Matti Aarnio wrote:
>  >
> > See the list archive:
> > 	http://www.zmailer.org/mhalist/2003/threads.html
> > Subjects:
> > 	How I did integrate Virus Scanner to ZMailer
> > 	MailScanner
> > 	New fields in control files?
> 
> Ok, thanks! Somehow I have managed to miss those, yet I'm a list member.
> I must have a memory management bug of some sort...
I just run my first speed test of ZMailer+MailScanner+SpamAssassin+McAfee... 
it's neither comprehensive nor representative, but it allows me to see the 
order of magnitude of overhead.

I used 3 machines with zmailer (they're some nice IBM computers with 512Mb 
RAM and a scsi disk)... I don't remember the details but /proc/cpuinfo says:
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 11
model name      : Intel(R) Pentium(R) III CPU family      1266MHz
stepping        : 1
cpu MHz         : 1266.736
cache size      : 32 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 mmx fxsr sse
bogomips        : 2509.56

I'm using redhat 7.3 with some rpm's from redhat 8.0 (notably, perl 5.8.0).

I'm using zm1 as a "feeder", zm2 as the test machine and zm3 as a sink.

All is done with static routes.

The "feeder" machine has a bunch of mails already in the scheduler queue 
routed to zm2.

The scheduler in zm1 has this setting:
smtptest/*
        expiry=5d
        maxchannel=199
        maxring=50
        maxthr=200
        overfeed=10
        command="smtp -8 -c smtptest -s -l ${LOGDIR}/smtptest"

Actually, it only kept about 30 concurrent connections to zm2.

zm2 is the test machine, it is configured to route all incoming mail to zm3 
(which would be the internal message store).

The smtpserver uses an alternative $POSTOFFICE ($POSTOFFICEIN)

MailScanner picks messages from $POSTOFFICEIN/router, processes them and 
leaves them in $POSTOFFICE/router for the router to pick them.

MailScanner invokes SpamAssassin internally (as a perl library) and _always_ 
rewrite the headers.

finally, zm2's scheduler has this configuration:
smtpint/*
        expiry=5d
        maxchannel=199
        maxring=50
        maxthr=4
        overfeed=10
        command="smtp -8 -c smtpint -s -l ${LOGDIR}/smtpint"
which keeps 4 parallel connections to zm3.

zm3 has a fqdnaliases entry that sends:
@example.com: /dev/null

I fed about 3500 spam messages with a few (about 10) containing viruses (no 
ham).

I measured differences in zm2's output queue using local "mailq -sQ"

On the bottom line, plain zmailer (that is, without MailScanner, smtpserver 
writing to the standard $POSTOFFICE/router) delivers about 140 msgs/min, 
whereas, with MailScanner+SpamAssassin+McAfee in between, it delivers about 
65 msgs/min.

Obviously, your mileage may vary... especially if you add lots of attachments 
that must be virus checked...

I used:
ZMailer 2.99.56-pre4 tarball
MailScanner 4.20-3
SpamAssassin 2.53
McAfee uvscan 4.24.0



--
Mariano Absatz
El Baby
----------------------------------------------------------
Too much of a good thing can be wonderful.
      -- Mae West


-
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi