[Imap-protocol] QRESYNC and new arrivals which get deleted
immediately through VANISHED
jkt at flaska.net
Fri Jul 13 11:23:16 PDT 2012
On 06/12/12 19:35, Alexey Melnikov wrote:
>> Would a proposal for adding "* ARRIVED 64,65,66" to replace EXISTS have
>> any real-world chance of getting accepted?
> Even if it would be, we can't just add "ARRIVED" to QRESYNC, because it
> is an RFC and I believer there are multiple server implementations
> already. We can reopen the document and define a new IMAP capability,
> but in short to medium term your code would have to handle the current
> situation anyway...
I've tried to define an extension adding the ARRIVED response to
QRESYNC. The full text in HTML format is available at , source in
rfc2xml format at .
I'm not familiar with the IETF process and such, and I'll also
appreciate some feedback before I submit it further -- so I'm open to
suggestions about what to do here. If you (anyone on the list) feel like
this is a waste of time, a great idea or anything in between, please let
I've also taken the liberty of not requiring an explicit ENABLE
QRESYNC-ARRIVED; it seems to me that the mere act of SELECT ...
QRESYNC-ARRIVED is explicit enough and the extra ENABLE is in fact not
I'll add code supporting this extension to my client shortly (probably
as "X-DRAFT-I00-QRESYNC-ARRIVED", that's the correct format, right?); if
any server vendors feel like implementing it as well for
interoperability testing, I'll offer a beer to the first such person I
meet in real life again :).
With kind regards
Trojita, a fast e-mail client -- http://trojita.flaska.net/
More information about the Imap-protocol