wasm-demo/demo/ermis-f/imap-protocol/cur/1600095186.22920.mbox:2,S

43 lines
1.7 KiB
Plaintext

MBOX-Line: From dave at cridland.net Tue Mar 20 09:41:18 2007
To: imap-protocol@u.washington.edu
From: Dave Cridland <dave@cridland.net>
Date: Fri Jun 8 12:34:38 2018
Subject: [Imap-protocol] literal usage
In-Reply-To: <71fe4e760703200717v201c983dq39791707ec286aa5@mail.gmail.com>
References: <71fe4e760703200717v201c983dq39791707ec286aa5@mail.gmail.com>
Message-ID: <1648.1174408878.724182@Nokia-N800-51>
> Hello
> I'm suffering using the little bogus python imaplib, that don't
> handle well
> literals.
> I would like to update the code, but need enlightened advices.
You could take a look at my Python library, at
http://trac.dave.cridland.net/
It might well save you a lot of work.
> In the following questions I'm not to much interested by AUTH,
> LOGIN, FETCH
> or APPEND but more about LIST, SEARCH, SETACL ...
> I would like to better understand the literal usage :
> When does a _server_ OR a _client_ use a literals ?
> When their is no other way (when does quoted string are not enough)
> ?
> What are the usual cases ? (I looked cyrus and found constraint
> about
> size>1024 or use of special char like "%" )
Either when they have to, or can. Quoted strings must be used in a
couple of places, such as Append commands for the date.
> What is the correct usage when mixing literal and string,
> does I need to insert a space between the end of a literal ?
There's usually a space, yes.
> For example for a setacl mailbox username lrswipcda, where I mix
> strings
> ands literals
> (Here .. means CRLF)
> C: 000001 SETACL "mailbox" {8}
> S: wait for server "continuation response"
> C: username..<DO I NEED TO INSERT A SPACE HERE>lrswipcda..
No cr lf should be there. Just a space.
Dave.