From: Rupert Swarbrick <rswarbrick@gmail.com>
To: ding@gnus.org
Subject: Re: QRESYNC syntax
Date: Sun, 28 Nov 2010 11:12:48 +0000 [thread overview]
Message-ID: <ictdfk$k3f$1@dough.gmane.org> (raw)
In-Reply-To: <m3d3ppn3e6.fsf@quimbies.gnus.org>
[-- 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 --]
prev parent reply other threads:[~2010-11-28 11:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 1:25 Lars Magne Ingebrigtsen
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 [this message]
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='ictdfk$k3f$1@dough.gmane.org' \
--to=rswarbrick@gmail.com \
--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).