[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Slowing down smtpserver (was: Re: A potential way to cut down on spam.)
- To: unlisted-recipients:; (no To-header on input)
- Subject: Slowing down smtpserver (was: Re: A potential way to cut down on spam.)
- From: acli@ada.dhs.org
- Date: Thu, 5 Feb 2004 03:50:33 GMT
- Distribution: local
- Newsgroups: local.mailgate.zmailer
- Organization: somewhere in Scarborough, Canada running C News CR.G and some assorted hacks for NNTP (including a hacked nntpxmit derived from NNTP 1.5.12)
- Original-Recipient: rfc822;zmailer-log@nic.funet.fi
- References: <S339884AbUBDSMc/20040204181232Z+798@SMTP.Morgan-Systems.com> <S339884AbUBDSMc/20040204181232Z+798@SMTP.Morgan-Systems.com> <1075920710.31943.55.camel@ariel.sovam.com>
- Sender: zmailer-owner@nic.funet.fi
In article <1075920710.31943.55.camel@ariel.sovam.com>,
Eugene Crosser <crosser@rol.ru> wrote:
>We use different scoring model, and different way of throttling
>(make smtp server appear very slow rather than reject message),
>but otherwize, I too think that "dynamic reactive" approach is
>the most useful one.
Before I switched to Eugene's zmscanner, my content filter
would often spend too much time analysing messages (not because
it's being thorough, rather the opposite: because my code is
poorly written and Perl is too slow for that box). I felt that
making the smtp server appear very slow *might* actually cause a
problem.
Some servers seem to have a very low tolerance of how "slow"
they can handle; any slower than that and they would assume your
server is down and they abort and retry later.
Does anyone have similar experiences? What would be a good
absolutely-maximum delay (e.g., for "tarpit")?
--
Ambrose LI Cheuk-Wing <a.c.li@ieee.org>
http://ada.dhs.org/~acli/
-
To unsubscribe from this list: send the line "unsubscribe zmailer" in
the body of a message to majordomo@nic.funet.fi