On Thu, May 09, 2002 at 01:15:01PM +0000, Bill Michell wrote:
Mail Admin writes:
Hi,
I've been using maildrop for a long time in a system with huge mail traffic.
Everything was fine till we decided to filter out all porn and spam material.
We built a list of more than 600 address known to send spam material, and
about same number of groups know to distribute adult stuff. I tried to get
maildrop do the job using normal maildroprc filter, something like.
if ( /^From: .*spammer1.*/ || /^From: .*spammer2.*/ || ........... ||
/^(To|Cc): .*badgroup1.*/ || /^(To|Cc): .*badgroup2.*/ || ....... etc )
{
exit
}
This is working , but it makes the server's load avarage over 20 :)
You might get better performance if you changed the exact form of the
pattern matching. At the moment, you'll probably be scanning each message
entirely through once for each of the From: addresses, for example. Try
listing the string From: only once, with a choice of things to follow it. I
don't promise it will help, but it shouldn't hurt.
Better yet, what MTA are you using? Most have a facility for doing this
sort of thing. For instance: Sendmail's access_db or qmail's
badmailfrom.
4 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Re: Performance issue.
