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

[Sunil S. <sun...@ro...>]

Dear John Connett,




________________________________
 > From: John Connett <jr...@sk...>
> 
> I have recently been migrated to Demon's new service which appears to be based on Microsoft Exchange Server 2010.  The migration appeared to have been successful with messages being fetched.  Then fetching of messages ceased.  I added "-vvv" to /etc/init.d/fetchmail and restarted fetchmail.  Here are edited highlights from /var/log/fetchmail:
> 
> fetchmail: IMAP< A0004 NO AUTHENTICATE failed.
> fetchmail: IMAP> A0005 LOGIN "xx...@yy..." *
> fetchmail: IMAP< A0005 OK LOGIN completed.

Please include the signature line / output of CAPABILITY command of your imap server in your report. This is to show the imap version supported.

> fetchmail: IMAP> A0009 FETCH 1 RFC822.HEADER
> fetchmail: IMAP< A0009 OK FETCH completed.
> fetchmail: Incorrect FETCH response: OK FETCH COMPLETED..

...

> The problem seems to be the "A0009 OK FETCH completed." response to "A0009 FETCH 1 RFC822.HEADER".  There are no patches touching "imap.c" in the openSUSE source RPM and I have confirmed that it is identical to the 6.3.21 original.
> 
> The "Incorrect FETCH response: OK FETCH COMPLETED.." appears to be generated from within imap_fetch_headers() by "an unexpected tagged response".  Is this an exciting new innovation in Microsoft Exchange Server 2010?

As is documented in imap.c, fetchmail expects response in the following format:

IMAP> A0006 FETCH 1 RFC822.HEADER                                     
IMAP< * 1 FETCH (RFC822.HEADER {1360}                                 
.... mail headers here ...
IMAP< A0006 OK FETCH completed.
                                                         

In your case, the middle part of the response is missing. Can you check by using telnet to the server if there are any headers in the mail and response to the variouse commands listed below:

A0010 FETCH 1 RFC822.TEXT

A0011 FETCH 1 BODY[TEXT]

for the mail causing the problem? Or check the mail through some other client and see if it is visible properly.

-- 
Sunil Shetye.