Re: [fetchmail-users] [PATCH] Re: Problem with Demon's new Microsoft Exchange Server 2010 service

[John C. <jr...@sk...>]

On Thu, 10 May 2012 16:35:13 +0100, Matthias Andree  
<mat...@gm...> wrote:
> John,
>
> can you try Sunil's patch, i. e. unpack the fetchmail sources, apply the
> patch, ./configure --with-ssl --with-gssapi and install, then move the
> offending message back in your inbox, send yourself another test
> message, and see if the patched fetchmail version skips over the
> offending message and retrieves the test message?

Sorry I haven't had chance to try the patch yet.  However, on Friday I had  
another meeting reminder and a correction from the same source.  Both of  
them stopped the unmodified fetchmail from fetching any further messages  
as before.

I did find the following articles about Exchange 2010 Calendar Repair  
Assistant:

http://www.msexchange.org/articles_tutorials/exchange-server-2010/management-administration/exchange-2010-calendar-repair-part1.html
http://www.msexchange.org/articles_tutorials/exchange-server-2010/management-administration/exchange-2010-calendar-repair-part2.html

which might be a hint at the source of the problem.  Maybe it is  
appropriate for Exchange 2010 to provide special calendar handling if it  
is the central IMAP server for a single organization.  However, for an ISP  
using it as a Mail Transfer Agent I would expect Exchange 2010 to pass on  
all (non-spam) e-mail messages without inspecting, modifying or making  
unavailable the body of those messages!  At the very least it indicates a  
possible misconfiguration at Demon and probably a bug in the IMAP part of  
Exchange 2010.

No response from Demon yet.  I will forward a copy of this message to them  
tagged with their Case reference.

Thanks again
--
John Connett