QRESYNC syntax

QRESYNC syntax

[Lars Magne Ingebrigtsen]

One of the servers, a Zimbra server, says that it accepts QRESYNC, and
it answers OK on "ENABLE QRESYNC", but it gives the following response
to this command:

435 EXAMINE "Drafts" (QRESYNC (1 1))

435 BAD parse error: wrong character; expected ' ' but got '('

Isn't that the right QRESYNC syntax?  This used to work...  I think...

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: QRESYNC syntax

[Lars Magne Ingebrigtsen]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> 435 EXAMINE "Drafts" (QRESYNC (1 1))
>
> 435 BAD parse error: wrong character; expected ' ' but got '('
>
> Isn't that the right QRESYNC syntax?  This used to work...  I think...

After experimenting a bit, I find that it accepts the following syntax:

435 EXAMINE "Drafts" (QRESYNC  (1 1))

Note the extra space before (1 1).

I think that Zimbra installation is just broken.  

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: QRESYNC syntax

[Daniel Pittman]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> 435 EXAMINE "Drafts" (QRESYNC (1 1))
>> 435 BAD parse error: wrong character; expected ' ' but got '('
>> Isn't that the right QRESYNC syntax?  This used to work...  I think...
>
> After experimenting a bit, I find that it accepts the following syntax:
>
> 435 EXAMINE "Drafts" (QRESYNC  (1 1))
> Note the extra space before (1 1).
> I think that Zimbra installation is just broken.

As far as I know the only common client that uses QRESYNC is the Zimbra
Destkop implementation, and some of the mobile phone hosted MUAs that need an
awful lot of work-arounds themselves.

So, it could be that it seldom gets used and that quirk has never been seen
before.
        Daniel
-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

Re: QRESYNC syntax

[Lars Magne Ingebrigtsen]

Daniel Pittman <daniel@rimspace.net> writes:

> As far as I know the only common client that uses QRESYNC is the
> Zimbra Destkop implementation, and some of the mobile phone hosted
> MUAs that need an awful lot of work-arounds themselves.

Hm.  But I think that it used to work...  Was the Zimbra server on
Rimspace upgraded recently?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: QRESYNC syntax

[Daniel Pittman]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Daniel Pittman <daniel@rimspace.net> writes:
>
>> As far as I know the only common client that uses QRESYNC is the
>> Zimbra Destkop implementation, and some of the mobile phone hosted
>> MUAs that need an awful lot of work-arounds themselves.
>
> Hm.  But I think that it used to work...  Was the Zimbra server on
> Rimspace upgraded recently?

There was an upgrade on 2010-11-17 at ~ 11:24, but nothing outside that.
      Daniel
-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

Re: QRESYNC syntax

[Lars Magne Ingebrigtsen]

Daniel Pittman <daniel@rimspace.net> writes:

>> Hm.  But I think that it used to work...  Was the Zimbra server on
>> Rimspace upgraded recently?
>
> There was an upgrade on 2010-11-17 at ~ 11:24, but nothing outside that.

I only noticed it not working a few days ago, and I hadn't looked at
that server for a while, so that does sound like the upgrade broke
QRESYNC.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: QRESYNC syntax

[Daniel Pittman]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Daniel Pittman <daniel@rimspace.net> writes:
>
>>> Hm.  But I think that it used to work...  Was the Zimbra server on
>>> Rimspace upgraded recently?
>>
>> There was an upgrade on 2010-11-17 at ~ 11:24, but nothing outside that.
>
> I only noticed it not working a few days ago, and I hadn't looked at
> that server for a while, so that does sound like the upgrade broke
> QRESYNC.

It could be.  The upgrade was, IIRC, 6.06 to 6.09, which fixed a whole bunch
of other stuff along the way.
        Daniel
-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

Re: QRESYNC syntax

[Steinar Bang]

>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:

> After experimenting a bit, I find that it accepts the following syntax:

> 435 EXAMINE "Drafts" (QRESYNC  (1 1))

> Note the extra space before (1 1).

> I think that Zimbra installation is just broken.  

Wasn't there some other IMAP server (cyrus? courier?) that needed to
have extra spaces removed on some commands?

Re: QRESYNC syntax

[Michael Welsh Duggan]

Steinar Bang <sb@dod.no> writes:

>>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:
>
>> After experimenting a bit, I find that it accepts the following syntax:
>
>> 435 EXAMINE "Drafts" (QRESYNC  (1 1))
>
>> Note the extra space before (1 1).
>
>> I think that Zimbra installation is just broken.  
>
> Wasn't there some other IMAP server (cyrus? courier?) that needed to
> have extra spaces removed on some commands?

Yes.  http://article.gmane.org/gmane.emacs.gnus.general/72495

-- 
Michael Welsh Duggan
(md5i@md5i.com)

Re: QRESYNC syntax

[Lars Magne Ingebrigtsen]

Michael Welsh Duggan <md5i@md5i.com> writes:

>> Wasn't there some other IMAP server (cyrus? courier?) that needed to
>> have extra spaces removed on some commands?
>
> Yes.  http://article.gmane.org/gmane.emacs.gnus.general/72495

Yeah, but choking on extra spaces, while sloppy, is easier to deal with
than inserting extra spaces here and there.  :-)

The only server I have access to that uses QRESYNC is the Zimbra
server.  Could people who have other servers that have QRESYNC eval
the following while in the "*nnimap ...*" buffer?

(nnimap-command "EXAMINE INBOX (QRESYNC  (1 1))")

Substitute a different mailbox name if you don't have INBOX.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: QRESYNC syntax

[Rupert Swarbrick]

[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Michael Welsh Duggan <md5i@md5i.com> writes:
>
>>> Wasn't there some other IMAP server (cyrus? courier?) that needed to
>>> have extra spaces removed on some commands?
>>
>> Yes.  http://article.gmane.org/gmane.emacs.gnus.general/72495
>
> Yeah, but choking on extra spaces, while sloppy, is easier to deal with
> than inserting extra spaces here and there.  :-)
>
> The only server I have access to that uses QRESYNC is the Zimbra
> server.  Could people who have other servers that have QRESYNC eval
> the following while in the "*nnimap ...*" buffer?
>
> (nnimap-command "EXAMINE INBOX (QRESYNC  (1 1))")
>
> Substitute a different mailbox name if you don't have INBOX.

Looks fine with dovecot (I did it once with and once without the extra
space):

rupert@hake:~ /usr/lib/dovecot/imap
* PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS] Logged in as rupert
1 enable qresync
* ENABLED QRESYNC
1 OK Enabled.
2 examine inbox (qresync (1 1))
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS ()] Read-only mailbox.
* 0 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1290942640] UIDs valid
* OK [UIDNEXT 1] Predicted next UID
* OK [HIGHESTMODSEQ 1] Highest
2 OK [READ-ONLY] Select completed.
3 examine inbox (qresync  (1 1))
* OK [CLOSED] Previous mailbox closed.
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS ()] Read-only mailbox.
* 0 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1290942640] UIDs valid
* OK [UIDNEXT 1] Predicted next UID
* OK [HIGHESTMODSEQ 1] Highest
3 OK [READ-ONLY] Select completed.
imap(rupert): Info: Connection closed bytes=82/910

[-- Attachment #2: Type: application/pgp-signature, Size: 315 bytes --]