Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Ding Mailing List <ding@gnus.org>
Subject: Re: IMAP retrieval errors
Date: Mon, 30 Jul 2007 11:44:17 -0400	[thread overview]
Message-ID: <m2lkcxoq0e.fsf@lifelogs.com> (raw)
In-Reply-To: <m2myxl5yel.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 24 Jul 2007 16:39:46 -0400")

On Tue, 24 Jul 2007 16:39:46 -0400 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> This is with an Exchange server over IMAP:
TZ> UID FETCH 252,583,1120,1144,1147,1186,1208,1225,1525,1549,1573,1577,1594,1619,1627,1635:1636,1667:1668,1684,1723,1733,1736,1740:1751 (UID RFC822.SIZE BODY BODY.PEEK[HEADER.FIELDS (Subject From Date Message-Id References In-Reply-To Xref X-Face Keywords Gcc Cc X-Spam-Status X-Bogosity X-CRM114-Status To Newsgroups)])
TZ> 3294 BAD Protocol Error: \"One of the supplied fetch items is invalid\".

TZ> Has anyone seen the problem before?  Is it something about the format of
TZ> the FETCH command that Exchange doesn't like?

Further information:

CVS Gnus

The Exchange server occasionally will throw this errors for a group.  I
lose all marks for the group (which is very annoying).  If I re-enter
the group, everything is marked as 'read'.  If I mark things again and
exit, the Exchange server will give me this error again and I lose the
marks again.  The only way to fix has been to move all articles to a
temporary group and back.

If no one has seen this before, I'll debug deeper next time it happens,
but at least I'd like a way to get my marks back!  Losing all the marks
is very counter-productive for me.

Thanks
Ted



  reply	other threads:[~2007-07-30 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 20:39 Ted Zlatanov
2007-07-30 15:44 ` Ted Zlatanov [this message]
2007-07-30 16:33   ` Leo
2007-07-30 17:16     ` Ted Zlatanov
2007-07-30 18:05       ` Leo

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=m2lkcxoq0e.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).