From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: QRESYNC syntax
Date: Fri, 26 Nov 2010 02:25:05 +0100 [thread overview]
Message-ID: <m3aakwswpa.fsf@quimbies.gnus.org> (raw)
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
next reply other threads:[~2010-11-26 1:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 1:25 Lars Magne Ingebrigtsen [this message]
2010-11-26 1:31 ` Lars Magne Ingebrigtsen
2010-11-26 9:41 ` Daniel Pittman
2010-11-28 10:30 ` Lars Magne Ingebrigtsen
2010-11-28 11:30 ` Daniel Pittman
2010-11-28 12:03 ` Lars Magne Ingebrigtsen
2010-11-28 12:52 ` Daniel Pittman
2010-11-26 10:03 ` Steinar Bang
2010-11-26 18:48 ` Michael Welsh Duggan
2010-11-28 10:33 ` Lars Magne Ingebrigtsen
2010-11-28 11:12 ` Rupert Swarbrick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3aakwswpa.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).