31 lines
1.3 KiB
Plaintext
31 lines
1.3 KiB
Plaintext
MBOX-Line: From tss at iki.fi Wed Aug 8 13:01:12 2007
|
|
To: imap-protocol@u.washington.edu
|
|
From: Timo Sirainen <tss@iki.fi>
|
|
Date: Fri Jun 8 12:34:40 2018
|
|
Subject: [Imap-protocol] Best Practices for Implementing an IMAP Client
|
|
Message-ID: <1186603272.29782.355.camel@hurina>
|
|
|
|
http://www.imapwiki.org/ClientImplementation
|
|
|
|
Feel free to update. I was hoping that it would eventually include
|
|
pretty much all the information needed by a new IMAP client developer,
|
|
including possible server bugs and their workarounds. So if a client
|
|
does something badly, you could just point the developers to a page
|
|
which says how it should have been done instead.
|
|
|
|
If you disagree with how something should be done, either let me know or
|
|
modify the Wiki directly. I've subscribed to .* pages so I get an email
|
|
if anything gets changed (you can do it too). Also see
|
|
http://www.imapwiki.org/About
|
|
|
|
(The domain was just registered, if it doesn't work or shows a Gandi
|
|
page, you can use http://imap.dovecot.org/ also for now)
|
|
|
|
-------------- next part --------------
|
|
A non-text attachment was scrubbed...
|
|
Name: signature.asc
|
|
Type: application/pgp-signature
|
|
Size: 196 bytes
|
|
Desc: This is a digitally signed message part
|
|
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20070808/1e01b901/attachment.sig>
|