you could do most of this today with plus addressing like
[email protected]
you can do all the normal filtering on the + part (on a per-user basis),
can be used to auto-sort your inbound mail into different folders and
leave unqualified stuff in your main folder
David Lang
On Fri, 23 Oct 2009, Edward Ned Harvey wrote:
Date: Fri, 23 Oct 2009 21:41:46 -0400
From: Edward Ned Harvey <[email protected]>
To: tech <[email protected]>
Subject: [lopsa-tech] Email naming convention
You know what I really wish existed?
[email protected]
[email protected]
[email protected]
and so on.
(No, this does not address the multiple-users-with-same-name problem.) This
is something completely separate.
I do magnificently well with [email protected] . I never give out the
same email address twice. (Note, [email protected], and
[email protected], etc) and when I start receiving spam on some
address . I know who let my address "leak" to spammers, and I simply throw
away that address (or filter it).
Yes, I recognize, if something like the above were popular, then spammers
would send mail to [email protected], but I think the next step
would be really obvious . Whenever I send mail to some email address, my
server autogenerates my From is [email protected], and my server
keeps track of "[email protected] corresponds with
[email protected]" and so on . if my server receives something
addressed to [email protected], or if my server receives
something addressed to [email protected] which didn't come from
[email protected] . the server can flag it or handle it in various
possible ways. Meh, I'm not describing it well, but I don't care. I just
want to blow steam for a minute or two here, on something that I think is a
good idea, which will never stand a chance of existing due to the fact that
there's no money in it, and nobody gives a crap about developing such
things. And then go get a beer. ;-)
Problem is, all the existing implementations of things like . Exchange,
Google Apps, collaboration email suite du jour . None of them understand how
to handle something like this. When I login as eharvey, I need my global
addressbook auto-populated with the list of other users in the organization.
But all the existing mail collaboration suites assume the domain name draws
the organization boundary.
_______________________________________________
Tech mailing list
[email protected]
http://lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
_______________________________________________
Tech mailing list
[email protected]
http://lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
