From: Thomas Davis <tdavis@nersc.gov>
To: Dumitru Ciobarcianu <Dumitru.Ciobarcianu@ines.ro>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>, linux-kernel@vger.kernel.org
Subject: Re: Postgrey experiment at VGER
Date: Wed, 13 Dec 2006 17:25:59 -0800 [thread overview]
Message-ID: <4580A827.7080200@nersc.gov> (raw)
In-Reply-To: <1166001902.15211.4.camel@DustPuppy.LNX.RO>
Dumitru Ciobarcianu wrote:
> On Wed, 2006-12-13 at 01:50 +0200, Matti Aarnio wrote:
>> I do already see spammers smart enough to retry addresses from
>> the zombie machine, but that share is now below 10% of all emails.
>> My prediction for next 200 days is that most spammers get the clue,
>> but it gives us perhaps 3 months of less leaked junk.
>
> IMHO this is only an step in an "arms race".
> What you will do in three months, remove this check because it will
> prove useless since the spammers will also retry ? If yes, why install
> it in the first place ?
>
>
spammers are already re-trying; but they give up after 10 minutes.
As the delay time increases, the chances of getting on a blacklist
increase, which makes it easier to identify a machine as a spamming bot.
I normally let my greyfilters run at 30 minutes deny, and 72hrs of
lease time on a IP/To/From tuplet. This setting seams to be pretty
effective in dropping spam; at one point, upto 10k spam vs. a couple
hundred ham messages.
thomsa
next prev parent reply other threads:[~2006-12-14 2:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 23:50 Matti Aarnio
2006-12-13 9:25 ` Dumitru Ciobarcianu
2006-12-13 12:52 ` Trond Myklebust
2006-12-14 1:25 ` Thomas Davis [this message]
2006-12-14 5:21 ` Rick
2006-12-13 14:11 Al Boldi
2006-12-13 15:37 ` Gene Heskett
2006-12-13 16:09 ` Giacomo A. Catenazzi
2006-12-13 17:16 ` Horst H. von Brand
2006-12-14 4:41 ` David Rees
2006-12-15 10:56 ` Folkert van Heusden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4580A827.7080200@nersc.gov \
--to=tdavis@nersc.gov \
--cc=Dumitru.Ciobarcianu@ines.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome