Re: [EAI] Fw: I-D Action: draft-yao-eai-dns-00.txt

["Jiankang YAO" <[e-mail]>]

----- Original Message ----- 
From: "Ned Freed" <[e-mail]>
To: "Jiankang YAO" <[e-mail]>
Cc: "Ned Freed" <[e-mail]>; <[e-mail]>
Sent: Tuesday, March 06, 2012 11:08 PM
Subject: Re: [EAI] Fw: I-D Action: draft-yao-eai-dns-00.txt


> 
>> ----- Original Message -----
>> From: "Ned Freed" <[e-mail]>
>> To: "Jiankang YAO" <[e-mail]>
>> Cc: <[e-mail]>
>> Sent: Tuesday, March 06, 2012 3:18 PM
>> Subject: Re: [EAI] Fw: I-D Action: draft-yao-eai-dns-00.txt
> 
> 
>> >> Thanks a lot for  all comments from the wg members.
>> >> Here are some clarifications:
>> >
>> >> 1) my intention is to help the deployment of eai protocols.
>> >> 2) In Feb. 2012, I talked with many email software and service providers in China.  some software providers in China have promised to implement and deploy rfc6531 and rfc6532.
>> >> 3) the idea in the draft was discussed during Feb. 2012 when I takled with them. They thought that some mechanisms with an early indicator of whether the destination server support SMTPUTF8 would help the deployment of RFC6531 and RFC652 during the early deployment of EAI.
>> >> 4) this draft is mainly for discussion about how we can help the deployment of EAI. If the WG thinks that it is not good idea, we can just discard it.
>> >> 5) the scenario which the email software or service providers would like to address is that eai users send the eai message to many users including eai user and ascii user.
>> >
>> >>  For example, if an internationalized message is sent to 10 users one of which is an ASCII user, the MSA may have
>> >>    to say EHLO 10 times before deciding to reject the message.
>> >
>> > Say what? I would expect in this case for the message to be delivered to the
>> > first 9 recipients and for the 10th to generate a DSN. That's the only sensible
>> > outcome
>> >
> 
>> there is a problem here.
> 
> I'm sorry, but there really isn't - at least there's no new problem that users
> don't already face all on a regular basis.
> 
>> When you send a message to 10 users, 9 users(A B C D E F G H I) recieve the
>> message. 1 user (K) can not receive it.
> 
>> question 1 ) what is your next step to deal with the user who can not receive
>> it?
> 
> The same as whatever you do when one of the users you sent to can't receive
> your mail now: Redo your message, so it's acceptable, call them on the phone,
> IM them, ignore the problem, whatever. This happens *all* *the* *time*, and
> when, say, your message is larger than the limit that site accepts, the
> condition may be every bit as permanent as if you tried to send them an EAI
> mail and they don't support that.
> 
> This is has always been how email has worked. Users have been coping with it
> for decades. They don't seem to have a problem doing so.
> 

I think that there has a little difference here.

In the pure ASCII email world, some users in the recipients list may lost the mail due to one or another reason. but after adjusting something,
they have a big chance to receive the message. So in the most cases, the message losing is temporary.

when EAI email word interacts with the ASCII email world, some users in the recipients list may never receive the mail sent to them.

I think that most users can bear the temporary failure of message delivery, but is unlikely to bear the permanent failure of message delivery.


Jiankang Yao