At 0:30 +0000 3/7/03, Matt Sergeant wrote:
On Thu, 6 Mar 2003, Jim Youll wrote:
At 18:33 +0000 3/6/03, Matt Sergeant wrote:
>Tagged addresses, temporary addresses, etc. All work well for a bit.
>Until your real email address gets out there.
>
>And then you're history.
>
>Look at it this way - you give your mum your real email address,
>because you know she's not a spammer. She forwards you a joke, and
>CC's a whole bunch of co-workers. One of those co-workers forwards
>that email to somewhere that gets archived on the web. And her MUA
>includes all those people's email addresses. BAM.
But if you had a proper client that hid all the work, you could
"give" a different e-mail address to every correspondent, and if it
leaked out, you need only cancel that one and give that particular
correspondent a freshly-generated address, no?
I just don't see how that can work in the business world where you have
corporate directories. Is the directory also supposed to dish out fresh
addresses each time? Your proposal then requires changes to all MUAs, some
MTAs, and now all LDAP and directory services and address book software.
Major headache.
I see this as one of many techniques that can be used separately to help with
the problem. If I were to switch to this technique only for addresses that
are deliberately shown to the public (web pages, chats,
fundamentally), I believe
the bulk of my spam problems could be kept under control.
Of course this does not work for every situation! For my grandmother and niece
and nephew, it would work quite well in many circumstances,
especially if the details were taken
care of behind the scenes.
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg