spf-discuss
[Top] [All Lists]

Re: No use of checking RFC2822 headers

2004-09-29 04:11:07
On 9/29/04 12:49 AM, "Michel Py" 
<michel(_at_)arneill-py(_dot_)sacramento(_dot_)ca(_dot_)us> wrote:

Carl Hutzler wrote:
The latter address is the email address which is
cdhutzler(_at_)aol(_dot_)com(_dot_) Carl Hutzler is the display name
or pretty name. We do not display the pretty name
in our AOL clients. Never have.

This is very good and we all thank you, but I'm afraid that the outlook
of the Outlook situation (pun intended) is bleak. The very reason
Outlook displays the pretty name is customer request, and delivering to
the customers what they want (no matter it's a good or bad idea) is what
made M$ successful.

I don't see a solution to it as of now, since millions would tell you
that it's a feature they want not a bug.


Agreed. But there are solutions to this. For example, you can have the
CLIENT software only display the display name if the receiving client has
the sender in their address book. This is the way some clients do it today
like in the IM world.

Not saying MSFT does not have to change the behavior...they do. And they
will have to do it for DomainKeys, CallerID and SenderID too! And they know
the issue well. I was just trying to ensure the whole community is aware so
when we talk to real people (your mom, dad, the Wall Street Journal, the
FTC...) we show them the limits of 822 checking and the caveats.

Otherwise some smart person in the audience at The FTCV's November
"showdown" will ask the question and we will all be caught flat footed. :-)

-Carl


-- 
Carl Hutzler
Director, AntiSpam Operations
America Online Mail Operations
cdhutzler(_at_)aol(_dot_)com
703.265.5521 work
703.915.6862 cell