unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Josefsson <simon@josefsson.org>
To: Jake Colman <colman@ppllc.com>
Cc: Ted Zlatanov <tzz@lifelogs.com>, "ding@gnus.org" <ding@gnus.org>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: Exchange 2007 Issues When Copying Between Folders
Date: Tue, 01 Apr 2008 16:49:04 +0200	[thread overview]
Message-ID: <87myodiqan.fsf@mocca.josefsson.org> (raw)
In-Reply-To: <76zlsdiqyb.fsf@dev-d01.ppllc.com> (Jake Colman's message of "Tue, 01 Apr 2008 10:34:52 -0400")

Jake Colman <colman@ppllc.com> writes:

>>>>>> "SJ" == Simon Josefsson <simon@josefsson.org> writes:
>
>    SJ> Simon Josefsson <simon@josefsson.org> writes:
>    >> Jake Colman <colman@ppllc.com> writes:
>    >> 
>    >>> Simon,
>    >>> 
>    >>> Can you suggest something better to fix this problem?  I'm sure that I'm
>    >>> not the only user who will want to use Gnus with Exchange 2007.  This
>    >>> fix, incorrect though it may be, does work.  Is there something other
>    >>> IMAP command that will get data in the way Gnus needs to see it?
>    >> 
>    >> Does the fix work?  In another post you said it didn't help.
>    >> 
>    >> We can introduce a variable nnimap-enable-exchange-bug-workaround that
>    >> toggles the way the code works.  You can set that variable, if it indeed
>    >> solves your problem, and others can leave it at its disabled default
>    >> value.
>
>    SJ> Here is what I propose, if 1:* really solves the problem.  Please test
>    SJ> it, apply the patch and customize nnimap-enable-minmax-bug-workaround to
>    SJ> a non-nil value.
>
> Simon,
>
> I probably thought it wasn't working because of the performance issue
> sue to the amount of data being transferred.  Yes, the bug fix _does_
> work and I _am_ able get data from my Exchange server.  Unfortunately,
> it is quite slow and, has some other bugs with moving  email betweeen
> folders.

Ok, I have installed my proposed patch in gnus cvs.

You need to customize and enable nnimap-enable-minmax-bug-workaround to
use the slow behavior.

/Simon




  reply	other threads:[~2008-04-01 14:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <767ifjymej.fsf@dev-d01.ppllc.com>
2008-03-31 18:50 ` Exchange 2007 Issues When Copying Between Folders Ted Zlatanov
2008-04-01 14:06   ` Simon Josefsson
2008-04-01 14:13     ` Jake Colman
2008-04-01 14:14     ` Jake Colman
2008-04-01 14:21       ` Simon Josefsson
2008-04-01 14:29         ` Simon Josefsson
2008-04-01 14:34           ` Jake Colman
2008-04-01 14:49             ` Simon Josefsson [this message]
2008-04-01 22:00     ` Gaute Strokkenes
2008-04-01 22:08       ` Simon Josefsson
2008-04-02 14:19     ` Ted Zlatanov
2008-04-02 14:33       ` Simon Josefsson
2008-04-03 13:09         ` Ted Zlatanov

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87myodiqan.fsf@mocca.josefsson.org \
    --to=simon@josefsson.org \
    --cc=colman@ppllc.com \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=tzz@lifelogs.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).