On Fri, 28 Jan 2005, Alan Knowles wrote: >This is the working connection on uw-imap, not the +\n is not broken >inside the "quot+\nprintable", but rather between the text. >http://docs.akbkhome.com/uw-imap.log.txt >(note this is a cut/paste from the terminal rather than cat'ing the log >so the ^M's blank out the first character of the lines. (process id I >presume)
Hi, Alan. Thanks for the reports! The protocol dumps clearly show that the two servers have different responses to this message. But I can't spot any protocol error. What I do see is that Binc IMAP writes extension sets in its BODYSTRUCTURE responses, and uw-imap doesn't. But the client is meant to ignore these if it doesn't understand them. I'd like to see if you can reproduce the error with any other IMAP clients, with the same message. I have a suspicion that it may be a client error, but I'd also like to see if others on this list can spot any protocol errors in the Binc IMAP dump. Andy :-) -- Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg Author of Binc IMAP | "It is better not to do something http://www.bincimap.org/ | than to do it poorly."
