From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Re: IMAP: 28 BAD Invalid QRESYNC parameter list in Examine
Date: Wed, 15 Dec 2010 22:59:18 +0100 [thread overview]
Message-ID: <874oae1yvd.fsf@member.fsf.org> (raw)
In-Reply-To: <m34oaek9ax.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 15 Dec 2010 22:36:38 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Tassilo Horn <tassilo@member.fsf.org> writes:
>
>> 22:30:45 97 EXAMINE "INBOX" (QRESYNC (1103381936 3974)).
>
> Right. I added that extra space because other servers choked when it
> wasn't present. But I've now removed it again.
Yes, that does the trick for me.
> Perhaps nnimap will have to add code to work around server quirks in
> this area. Too bad.
Indeed. How picky can a server be?!?
Bye,
Tassilo
next prev parent reply other threads:[~2010-12-15 21:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 8:15 Tassilo Horn
2010-12-15 19:59 ` Lars Magne Ingebrigtsen
2010-12-15 21:31 ` Tassilo Horn
2010-12-15 21:36 ` Lars Magne Ingebrigtsen
2010-12-15 21:59 ` Tassilo Horn [this message]
2010-12-16 13:32 ` Ludovic Courtès
2010-12-16 15:42 ` Lars Magne Ingebrigtsen
2010-12-17 16:18 ` Ludovic Courtès
2010-12-17 16:31 ` Lars Magne Ingebrigtsen
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=874oae1yvd.fsf@member.fsf.org \
--to=tassilo@member.fsf.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).