Re: [imap5] Feature set? - was Re: Designing a new replacement protocol for IMAP

[Dave Cridland <[e-mail]>]

On Mon Feb 20 12:43:25 2012, Filip Navara wrote:
> JYFI, we (eM Client, www.emclient.com) do use BURL in some cases.
> 
> 
As does the Qt Messaging Framework.

(And Polymer, and Isode's M-Switch/M-Box, and ... )

That all said, I'm swinging around to the notion of sending mail  
through the message store access protocol:

If we have a command which sends a particular mail *with an  
envelope*, then I think we can map all ESMTP stuff to it - but rather  
more interestingly, we can keep the envelope around as metadata  
within the store.

This allows things which you simply cannot do with BURL, for instance:

1) We could track bounces using VERP, and annotate the message when a  
DSN is received, so you could see which sent messages have failed.

2) We could track MDNs in a similar way.

You'd want multiple envelopes on a message, to handle resends and  
redirects, and it seems sensible to capture the S/LMTP envelope on  
delivery, too, such that a client would have sufficient information  
to cause a (delayed) bounce.

I appreciate this appears to be a U-turn on my behalf - that's  
because it is. I don't see multiple protocols as being a  
show-stopper, but the comments about DSN/MDN processing sparked this  
chain of thought for me.

Dave.
-- 
Dave Cridland - mailto:[e-mail] - xmpp:[e-mail]
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade