Could have been some third-party SMTP server in front of Exchange that re-aliased the
address into an acceptable one.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 3:42 PM
To: Exchange Discussions
Subject: Re: Question regarding ñ
Just to clarify RFC821 versus RFC822
It is true that RFC821 DOES NOT allow this character in the destination headers.
However, RFC822 DOES allow this character. In fact there are follow-on RFCs that
describe Quoted-Printable for the 822 headers. So, you should be able to have the
descriptive
Discussions
Subject: RE: Question regarding ñ and other characters
Just to clarify RFC821 versus RFC822
It is true that RFC821 DOES NOT allow this character in the
destination headers. However, RFC822 DOES allow this
character. In fact there are follow-on RFCs that describe
Quoted
I'm not sure what ASCII character that translates to, I assume it isn't
0=128? If not, it's not a valid ASCII character for an SMTP address.
-Original Message-
From: David S. Michel [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 12:05 PM
To: Exchange Discussions
Subject:
Charmap says it's 241.
-Original Message-
From: Chris Scharff [mailto:[EMAIL PROTECTED]]
Posted At: Thursday, July 25, 2002 01:21 PM
Posted To: MSExchange Mailing List
Conversation: Question regarding ñ and other characters
Subject: RE: Question regarding ñ and other characters
On Thu, 25 Jul 2002, at 1:31pm, Tom Meunier wrote:
Charmap says it's 241.
Too bad ASCII only defines a 7-bit (0-127) character set. :-)
--
Ben Scott [EMAIL PROTECTED]
| The opinions expressed in this message are those of the author and do not |
| necessarily represent the views or policy
On Thu, 25 Jul 2002, at 12:04pm, David S. Michel wrote:
We have a user who wants the ñ in his name to also be in his email
address instead of a plain old n.
We have a user who wants to win the lottery. :-)
However, this user insists that at his last firm his actual email address
was
7 matches
Mail list logo
