From: nathanw@MIT.EDU (Nathan J. Williams)
To: ding@gnus.org
Subject: Re: problem in connecting to Exchange 2007 - possible solution?
Date: Mon, 03 Dec 2007 13:14:57 -0500 [thread overview]
Message-ID: <mtuwsrv3ase.fsf@contents-vnder-pressvre.mit.edu> (raw)
In-Reply-To: <87bq97psi4.fsf@mocca.josefsson.org> (Simon Josefsson's message of "Mon\, 03 Dec 2007 19\:01\:23 +0100")
Simon Josefsson <simon@josefsson.org> writes:
> We shouldn't apply this so it is enabled by everyone, because it wastes
> bandwidth (sometimes by a large factor, bandwidth goes from O(1) to O(n)
> where n is the size of the mailbox...). Maybe you could rewrite this so
> that it is only used if some variable is enabled?
Does it? "FETCH *:*" seems to only return one message, the last one,
which makes sense to me - it's the range of messages from last to
last. It's not a synonym for "1:*".
- Nathan
next prev parent reply other threads:[~2007-12-03 18:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 23:58 Nathan J. Williams
2007-12-03 17:04 ` Nathan J. Williams
2007-12-03 18:01 ` Simon Josefsson
2007-12-03 18:14 ` Nathan J. Williams [this message]
2007-12-04 13:46 ` Simon Josefsson
2007-12-04 15:20 ` Nathan J. Williams
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=mtuwsrv3ase.fsf@contents-vnder-pressvre.mit.edu \
--to=nathanw@mit.edu \
--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).