Re: Sync problem

[Gilles Roy <groy@xxxxxxx>]

On Thu, Mar 08, 2007 at 07:51:32AM -0600, John Goerzen wrote:
>On Thu, Mar 08, 2007 at 08:40:37AM -0500, Gilles Roy wrote:
>> Any advice here? Is is just the server that gets mixed up when the CR LF 
>> CR LF sequence is broken up into multiple messages? Is this even a valid 
>> message from offlineimap?
>
>Incidentally, you mentioned Exchange 5.5...  have you read the FAQ:
>
>http://software.complete.org/offlineimap/wiki/FrequentlyAskedQuestions#MicrosoftExchange

FYI,

I played with it some more, and the Exchange server seems to just get
hung up at random, it has nothing to do with the CR LF being broken 
up. I found a problem report against Exchange 5.5:

http://support.microsoft.com/kb/239082/EN-US/
"If the server obtains the end of the message and a carriage return/line 
feed (CR/LF) during a single read, the CR/LF may be ignored, and 
therefore it is not decrypted. This causes the client to stop 
responding."

When I read that statement, I get the impression the server ignores the 
final CR LF (sometimes). To try to make the server receives it in 
a separate read(), I put a sleep(0.1) in imaplib.py:

self.send(literal)
time.sleep(0.1);
self.send(CRLF)

Seemed to make things run much better for me. 

But then I noticed that some of the messages in my maildir were being 
corrupted. Mutt was saving them there OK, but I think that during the 
APPEND some of the lines were being shuffled (i.e. lines at beginning of 
message are switched with lines around 20-25 such that the proper 
headers are embedded in the message). Maybe a problem at the exchange 
end?

Then I guess offlineimap synced this corrupted message from the 
Exchange server  back to my maildir. Normally the messages that I moved 
around locally in my maildir using mutt don't have any offline imap 
headers, but all of the corrupted 
messages have something like:

X-OfflineIMAP-1717163787-52656d6f7465-6d756c74696d65646961:
1173905685-0675798118739-v4.0.16


This corruption was occurring even before I messed around with the 
sleep(). I think I'm ready to give up on syncing with Exchange 5.5. I 
just wanted to share this info with others. offlineimap/echange never had 
problems with fetching messages, it is mainly with APPEND.


Regards,
Gilles