From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] opposite of bloom filter
Date: Sat, 13 Nov 2010 18:20:56 -0500 [thread overview]
Message-ID: <74cc3473129cfdc4f37c2f0fc3df9772@plug.quanstro.net> (raw)
In-Reply-To: <AANLkTi=TENXNS86geesTcdsG2g7w7gE-XeVa+SVbqB-H@mail.gmail.com>
> > ladd Nov 13 04:08:12 Disallowed gossinternational.com!ruiohfsd (gossinternational.com/124.172.212.142) to blocked name quanstro.net!b94cd358e11d3ffb43628c10bc786087
> >
> > i think the idea of spooling email is largely discredited.
> > it opens up the possiblity for backscatter spam, or the lack of
> > delivery rejection notification. either one is not good. i think the
> > acepting smtp server has to be in a position to make a definitive
> > decision on disposition. (sorry.)
>
> The solution I described (a Bloom filter of all the valid addresses)
> would work fine for this. An optimally sized Bloom filter requires
> about 4.8 bits per power of ten per address. If you want a 1 in 1000
> chance of a spammy address getting through and have n valid addresses,
> you need to a Bloom filter of size 3 * 4.8 * n = 14.4n bits.
i don't doubt the efficiency of bloom filters, but since
these addresses are never repeated, i don't see how it
would help. (i've gotten 1000s of these/day.)
- erik
next prev parent reply other threads:[~2010-11-13 23:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-13 18:43 Enrico Weigelt
2010-11-13 22:26 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-11-13 22:48 ` erik quanstrom
2010-11-13 23:10 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-11-14 2:52 ` Bruce Ellis
2010-11-14 2:54 ` Bruce Ellis
2010-11-14 2:56 ` Bruce Ellis
2010-11-13 22:31 ` Russ Cox
2010-11-13 22:38 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-11-13 23:15 ` Russ Cox
2010-11-13 23:20 ` erik quanstrom [this message]
2010-11-13 23:28 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-11-13 23:46 ` erik quanstrom
2010-11-13 23:51 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
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=74cc3473129cfdc4f37c2f0fc3df9772@plug.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).