From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] opposite of bloom filter
Date: Sun, 14 Nov 2010 13:56:28 +1100 [thread overview]
Message-ID: <AANLkTi=O+3S-s6pV0iV+1J9VHC0oaNQmkZqfVmBe2v8i@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=u5uJaCgq-v1KhTaNzTXgY3UJT_DkY4iQ4+Xza@mail.gmail.com>
crap i was right the first time. suffixes from .com to .crazy-tool.com
On Sun, Nov 14, 2010 at 1:54 PM, Bruce Ellis <bruce.ellis@gmail.com> wrote:
> oops "prefixes are common". it's hot and i'm still wingless.
>
> brucee
>
> On Sun, Nov 14, 2010 at 1:52 PM, Bruce Ellis <bruce.ellis@gmail.com> wrote:
>> grep -f is very efficient. you can extract it to a lib if you like.
>> please think about this and peek at the code before replying. i
>> understand the code because i was lucky enough to be in the room when
>> it was written.
>>
>> a negatie bloom sounds good but your positives will (potentially) collide.
>>
>> so the data structures i would recommend are a suffix tree
>> [McCreight], but reversed as the suffixes are common, or if you are
>> thinking of hashing go for a scapegoat tree.
>>
>> brucee
>>
>> On Sun, Nov 14, 2010 at 9:26 AM, Lyndon Nerenberg (VE6BBM/VE7TFX)
>> <lyndon@orthanc.ca> wrote:
>>>> The purpose is allowing an spooling (store+forward) mail relay
>>>> to learn which addresses are not accepted by the actual maildrop
>>>> (which is connected by an uucp-link, so no direct smtp chat),
>>>> to get rid of the thousands silly error bounces from brute force
>>>> attacks on email addresses.
>>>
>>> Very(!) interesting approach to this. I still transfer large chunks
>>> of my mail over UUCP, so this is a problem I face daily. I'd appreciate
>>> being kept in the loop for anything you find out. (And collaborating on
>>> a solution.)
>>>
>>> --lyndon
>>>
>>>
>>>
>>
>
next prev parent reply other threads:[~2010-11-14 2:56 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 [this message]
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
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='AANLkTi=O+3S-s6pV0iV+1J9VHC0oaNQmkZqfVmBe2v8i@mail.gmail.com' \
--to=bruce.ellis@gmail.com \
--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).