Gnus development mailing list
 help / color / mirror / Atom feed
From: Jake Colman <colman@ppllc.com>
To: ding@gnus.org
Subject: Re: the Exchange 2007 fix
Date: Thu, 03 Apr 2008 16:50:13 -0400	[thread overview]
Message-ID: <76iqyyhddm.fsf@dev-d01.ppllc.com> (raw)
In-Reply-To: <v9abkaafx8.fsf@marauder.physik.uni-ulm.de>

>>>>> "RS" == Reiner Steib <reinersteib+gmane@imap.cc> writes:

   RS> On Thu, Apr 03 2008, Ted Zlatanov wrote:
   >>>> FWIW, Exchange announces itself:
   >>>> 
   >>>> * OK The Microsoft Exchange IMAP4 service is ready."
   >>>> 
   >>>> so we could have specific fixes for it predicated on that,
   >>>> rather than user-controlled variables (and the user could
   >>>> override the auto-detection, naturally).  I don't relish the
   >>>> idea, but it's certainly better than leaving a large percentage
   >>>> of Gnus users out in the cold.
   >> 
   SJ> Maybe you could implement some logic that would set the newly
   SJ> introduced imap-enable-exchange-bug-workaround based on the
   SJ> server greeting?
   >> 
   >> I am not sure if Exchange-specific handling should be on or off by
   >> default.  The user will be able to override it the other way, but
   >> the base default is a bit of a philosophical question and
   >> therefore must take up more discussion time than a technical issue
   >> :)

   RS> The subject say that the problem is only with Exchange 2007.  If
   RS> older versions don't require it, we should probably not enable it
   RS> just because of the Exchange server greeting (which doesn't tell
   RS> the version).

I can vouch for the fact that Exchange 5.5 worked like a charm.  It's
amazing how badly MickySoft broke things when it released Exchange 2007.

I can also vouch for the fact that the patches contained in the latest
release of imap.el and nnimap.el go a very long way towards addressing
the issues.  We're not quite there but we're edging ever close.

-- 
Jake Colman
Director of Software Development
Principia Partners LLC
101 West Elm Street
Suite 620
Conshohocken, PA  19428
+1 (610) 755-9786
www.principiapartners.com




  reply	other threads:[~2008-04-03 20:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 19:31 Michael Harnois
2008-03-28 14:40 ` Ted Zlatanov
2008-04-01 22:30   ` Nathan J. Williams
2008-04-01 22:41     ` Simon Josefsson
2008-04-02  2:58       ` Jake Colman
2008-04-02 14:29         ` Simon Josefsson
2008-04-02 14:11       ` Ted Zlatanov
2008-04-02 14:50         ` Simon Josefsson
2008-04-03 13:11           ` Ted Zlatanov
2008-04-03 19:37             ` Reiner Steib
2008-04-03 20:50               ` Jake Colman [this message]
2008-04-08 21:14               ` Ted Zlatanov
2008-04-01 23:03     ` Michael D. Harnois
2008-04-02  2:59       ` Jake Colman
2008-04-02 14:31         ` Simon Josefsson
2008-04-02 14:48           ` Simon Josefsson
2008-04-02 22:13             ` Jake Colman
2008-04-03 13:07               ` Ted Zlatanov
2008-04-03 15:22             ` Jake Colman
2008-04-03 15:28               ` Simon Josefsson
2008-04-22 11:37             ` Steinar Bang

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=76iqyyhddm.fsf@dev-d01.ppllc.com \
    --to=colman@ppllc.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).