Re: [Imap-protocol] If Crispin were creating IMAP today how would it be different?

It's off topic here.
The mailing list is about IMAP.
It's not about SMTP.


-- 
Hoa V. Dinh


On Tuesday, March 10, 2015 at 4:14 AM, Imants Cekusins wrote:

> Ok it appears I am not the only one considering current protocol slow.
> I read this a while ago so I do not claim to be a discoverer of this
> solution.
> 
> This is what D. J. Bernstein apparently wrote:
> 
> 
> > The bottleneck in mailing list delivery today is SMTP latency. It typically takes more than ten seconds to transfer a message to another Internet host through SMTP. My mail transfer protocol, QMTP, is much faster, but how can qmail tell whether a remote host supports it? Answer: encode the information into the remote host's MX record. A future version of qmail-remote will support this. My target is 100 million remote deliveries per day on a 16MB machine.
> 
> http://cr.yp.to/qmail/future.html
> 
> 
> > The Quick Mail Transfer Protocol (QMTP) is a replacement for the
> Simple Mail Transfer Protocol (SMTP). QMTP eliminates any need for
> end-of-line scanning between hosts with the same end-of-line
> convention. It features automatic pipelining and chunking, 8-bit
> transmission, prior declaration of the message size, and efficient
> batching. It is designed to be very easy to implement.
> 
> 
> http://cr.yp.to/proto/qmtp.txt
> _______________________________________________
> Imap-protocol mailing list
> [email protected]
> http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol
> 
>

_______________________________________________
Imap-protocol mailing list
[email protected]
http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol