Hi Simon,
Couple guidelines: fast disk I/O more important than CPU for courier
itself.
despite whatever a workstation benchmarks might show about SATA disks,
even 8 year old scsi controllers and disks still just plain rock when it
comes to lots of I/O duties.
On single system (pair) handling couple hundred users or so, you really
want strength in the disk subsystem, and it helps to have more than one
proc (allows for multiple threads to run). I'm handling 200 users, 10k
messages per day on a pair of old dual PIII 1Ghz machines with u320 10k
rpm hard drives (software raid mirrors) and 2Gbytes ram, including all
the functions you mention. No loading issues or delays in email, and all
my users are IMAP over TLS and use message submission protocol on
sending side.
Current total message store size: 110Gbytes +/-, plenty of maildirs with
100k emails in them (my own account). I run xfs as a filesystem on
linux. Personal pref entirely (since reiserfs has been chroot'ed to
jail), but I've avoided the ext3/ext4 journal/lock/fopen/order
discussion entirely. (xfs has mature repair/optimization tools/options
as well).
by far, spamassassin, clamav and so on will chew up CPU time 2-5x
compared to any courier-mta related processes. spamassassin chews up
memory compared to the MTA;-)
here's how I inlined both clamav and spamassassin into courier, via
/etc/courier/maildroprc (note: if you use procmail or other final
delivery agent, you'll need something similar for that process)
Note: I don't claim any credit for the script. it works nicely, no
problems. My active users get maybe one to five spams per week each and
no true false positives to mention. I've had the same email address for
a dozen years and am plastered in numerous domain registrar databases. I
get one or two unlabeled spams per week....seriously.
(I do use the RBL features too and hold SMTP connections open for 30
seconds before answering helo. together, those dump 90% of the trash out
there)
regards,
andy
more /etc/courier/maildroprc
# Only scan mails smaller than VSCANSIZE for a virus
VSCANSIZE="2000000"
# Only scan mails smaller than SCANSPAMSIZE for spam
SCANSPAMSIZE="200000"
###############################################################################
#
# Use ClamAV to scan for viruses.
#
###############################################################################
if( $SIZE < $VSCANSIZE )
{
exception {
xfilter "/usr/bin/clamscan.sh"
}
}
if(/^X-Virus-Status:.*INFECTED/)
{
`test -d $DEFAULT/.Quarantine`
if ( $RETURNCODE == 1 )
{
`/usr/bin/maildirmake -f Quarantine $DEFAULT`
`echo INBOX.Quarantine >> $DEFAULT/courierimapsubscribed`
}
exception {
to "$DEFAULT/.Quarantine/"
}
}
###############################################################################
#
# Use SpamAssassin to filter SPAM
#
###############################################################################
if( $SIZE < $SCANSPAMSIZE )
{
xfilter "/usr/bin/spamc"
}
if (/^X-Spam-Flag: *Yes/:h)
{
#Create SPAM IMAP folder if they don't have one
`test -d $DEFAULT/.Spam`
if( $RETURNCODE == 1 )
{
`/usr/bin/maildirmake -f Spam $DEFAULT`
`echo INBOX.Spam >> $DEFAULT/courierimapsubscribed`
}
exception {
to "$DEFAULT/.Spam/"
}
}
Simon Loewen wrote:
>
> A few final questions for this evening :)
>
> 1) I am looking for some performance information of courier in
> particular the MTA so that I can spec some hardware. I have trawled
> their website for a while and have not managed to locate anything, nor
> on Google.
>
> 2) Can Spamassasin Bitdefender and clamv be hooked into Courier-mta?
>
> Night night, S.
>
------------------------------------------------------------------------------
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
------------------------------------------------------------------------------
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
