From: "Steven E. Harris" <seh@panix.com>
To: ding@gnus.org
Subject: Re: Courier-IMAP and UIDPLUS problem
Date: Wed, 29 Aug 2007 17:56:49 -0700 [thread overview]
Message-ID: <7ywsvdzvid.fsf@fillmore.spawar.navy.mil> (raw)
In-Reply-To: <7yr6lm18by.fsf@fillmore.spawar.navy.mil> (Steven E. Harris's message of "Wed, 29 Aug 2007 11:49:12 -0700")
"Steven E. Harris" <seh@panix.com> writes:
> I just sent this message to my ISP regarding their mail servers:
My ISP corrected the capability string on their IMAP server (which was
apparently a proxy server's misrepresentation of the real IMAP server's
capabilities), and the aforementioned problems with Gcc, copying, and
moving messages went away.
This one falls under "be conservative in what you send, liberal in what
you accept"; nnimap does not fail gracefully when the advertised UIDPLUS
data turns out to be missing from the server responses.
--
Steven E. Harris
prev parent reply other threads:[~2007-08-30 0:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 17:35 New nnimap error with Gcc Steven E. Harris
2007-07-02 14:08 ` Simon Josefsson
2007-07-03 3:22 ` Steven E. Harris
[not found] ` <7ybqcr79q8.fsf@fillmore.spawar.navy.mil>
2007-08-29 18:49 ` Courier-IMAP and UIDPLUS problem (was: New nnimap error with Gcc) Steven E. Harris
2007-08-30 0:56 ` Steven E. Harris [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=7ywsvdzvid.fsf@fillmore.spawar.navy.mil \
--to=seh@panix.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).