From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: error Gcc'ing to imap folder
Date: Sat, 22 Jan 2011 20:55:52 +0100 [thread overview]
Message-ID: <87pqropvav.fsf@gnus.org> (raw)
In-Reply-To: <87tyh0g1m6.fsf@pinto.chemeng.ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Unfortunately. If there's any specific debugging you would like me to
> try, just let me know.
I guess the IMAP servers just don't return the article numbers in a
reliable way when searching by Message-ID. There's not much to do about
that, though. It's not a major issue for Gnus, but it means that some
features don't work totally as they should. But they're not very
central features.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-01-22 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 19:30 Eric S Fraga
2011-01-07 22:59 ` Dave Goldberg
2011-01-08 20:49 ` Eric S Fraga
2011-01-09 15:03 ` Dave Goldberg
2011-01-10 18:31 ` Eric S Fraga
2011-01-11 19:05 ` Lars Magne Ingebrigtsen
2011-01-13 20:33 ` Eric S Fraga
2011-01-22 3:42 ` Lars Ingebrigtsen
2011-01-22 19:49 ` Eric S Fraga
2011-01-22 19:55 ` Lars Ingebrigtsen [this message]
2011-01-22 20:35 ` Eric S Fraga
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=87pqropvav.fsf@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).