Re: [fetchmail-devel] broken behavior in Exchange Server 2003 IMAP4rev1

[Adam S. <sim...@ci...>]

On Fri, Nov 02, 2007 at 05:58:31PM +0100, Matthias Andree wrote:
> Am Donnerstag, den 01.11.2007, 18:06 -0700 schrieb Adam Simpkins:
> 
> > I tracked down the problem, and it occurs because the Exchange server
> > is rewriting the MIME boundary before sending it to the IMAP client.
> 
> So tell Exchange not to do that.
> Why would a client want to cater for servers who tamper with data? It's
> the MIME boundary today and the sender address tomorrow. And why would a
> client want to use such a server at all?

Yes, I agree Exchange is broken here.  Unfortunately, I don't have any
control over the mail server.  I have contacted my IT support contacts
about this problem with the server, but I haven't heard anything back
from them yet.  (And I don't have high hopes that they'll be willing
or able to fix this problem anyway.)


> [bug fixing for Lotus insanity transferred to MS Exchange?]
> > I don't suppose I can convince you to reconsider?  (I somehow doubt
> > I'll have much luck convincing Microsoft to fix exchange.)
> 
> Well, if I had time at my hands, I might offer to fix this for money.
> Given that 6.3.9 has been delayed for weeks already, I'd rather not make
> any offers in that direction.
> 
> I'm aware this isn't too helpful, but I don't see it as my foremost
> interest to work around server bugs - especially not if the changes to
> code would have to be rather intrusive.

Sure, I completely understand.  I've switched to POP3 for now, which
shouldn't have the problem.

If I have the time later, I might create a patch for this on my own.
Would you consider accepting the patch if I came up with one?  It
looks like I should probably just create a new method struct identical
to the current "imap" one, but with a single fetch method that gets
everthing, and fetch_body set to NULL.  Is that the preferred
approach, or did you have something else in mind?

-- 
Adam Simpkins
sim...@ci...