Re: [Jmap] Submission is not hard

["Adrien de Croy" <[e-mail]>]

------ Original Message ------
From: "John Levine" <[e-mail]>
To: "[e-mail]" <[e-mail]>
Cc: "[e-mail]" <[e-mail]>
Sent: 22/04/2017 3:16:36 AM
Subject: Re: [Jmap] Submission is not hard
>
>Finally, if people want to try whizbang ways to show animations of
>mail zipping through the aether, that sounds like a swell optional
>add-on to try and implement and test and perhaps bring back later as
>an extension, but it'd be nuts to try to invent it now.
>

IME, if we don't design it now, it will never happen.  Surely it's 
important enough to do the work up front?

ll I'm suggesting here is that in the new MUA to JMAP protocol, we allow 
for notifications about delivery, and not use the MDNs for this (between 
client and JMAP server).

When a JMAP server needs to forward a message via SMTP, then it can use 
existing SMTP extensions for this if supported, or tell the client that 
it won't be getting any more delivery status updates for that message.

For internal mail that doesn't go anywhere near SMTP, it could be a very 
rich experience.

Eventually when organisations using this build enough web of trust to 
use it for inter-organizational messaging, the rich experience will come 
for free.  This is one way to provide a compelling reason to make a 
change.

Because sorry, but bounce messages are out of the dark ages.  We need an 
attitude change here, we're competing against systems that aren't bound 
by the need for consensus, and are just able to provide service and 
function which is enticing users away from our systems.  This is making 
existing systems weaker and gradually obsolete.

Cheers

Adrien



>
>R's,
>John
>
>_______________________________________________
>Jmap mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/jmap