Anton Yuzhaninov
2008-May-18 22:48 UTC
[Dovecot] RFC 3516 - IMAP4 Binary Content Extension
Is Binary Content Extension (rfc3516) support planned? -- WBR, Anton Yuzhaninov
On Mon, 2008-05-19 at 02:48 +0400, Anton Yuzhaninov wrote:> Is Binary Content Extension (rfc3516) support planned?It's not in my near-term plans. Where are you planning on using it? Are there some clients that support it? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20080519/7ab96ab1/attachment-0002.bin>
Anton Yuzhaninov
2008-May-19 06:59 UTC
[Dovecot] RFC 3516 - IMAP4 Binary Content Extension
Timo Sirainen ?????:> On Mon, 2008-05-19 at 02:48 +0400, Anton Yuzhaninov wrote: >> Is Binary Content Extension (rfc3516) support planned? > > It's not in my near-term plans. Where are you planning on using it? Are > there some clients that support it? >It may be useful in loaded web-mail applications (base64 decoding implemented in C is more cpu/memory efficient than in perl or other web scripting language). And may be we will use this extension in the webmail for our free-mail service (http://mail.rambler.ru) Popular desktop clients AFAIK don't support rfc3516. Is it possible to write plugin for support this extension? -- WBR, Anton Yuzhaninov
Maybe Matching Threads
- 1.0.10 - Cached message offset lost
- converting maildir to mailbox
- gzip compressed mbox: Panic: file istream-zlib.c: line 421 (i_stream_zlib_seek): assertion failed: (ret == -1)
- fts squat and dovecot-shared
- dovecot 1.1.5 mbox bug (From_-line separator related)