but
INTERNALDATE "28-Jan-2005 12:15:41 +0000" RFC822.SIZE 47335 BODY (("text" "plain" ("charset" "iso-8859-1") NIL NIL +
"quoted-printable" 1170 30)("text" "html" ("charset" "iso-8859-1") NIL NIL "quoted-printable" 443 0 997) "alternative" ))
0008 OK FETCH completed
rather than this is causing the problems
INTERNALDATE "28-Jan-2005 12:15:41 GMT" RFC822.SIZE 47335 BODY (("text" "plain" ("charset" "iso-8859-1") NIL NIL "quoted-printable"
1170 31 NIL NIL NIL NIL)("text" "html" ("charset" "iso-8859-1") NIL NIL "quoted-printable" 44350 998 NIL NIL NIL NIL) "alternative" ("boundary" "_=_54f0228d8fbd5e9eaf952a8a0a3bb771") NIL NIL))
I've commented out large chunks of maildirmessage.cc bodyStructure() (basically most of the code after (line ~146 ) io << toImapString(message->getSubType());
.. this gets rid of the last NIL/NILL... boundary stuff.
and the whole if (extended) { } section .. (which gets rid of the extra
NIL/NIL/NIL etc.It appears both changes are needed to make this work.
PS. Any ideas on the outlook issue? - the only one I could see quickly was the comments about qmail and the 1 second rule on scanning /new/ - but I dont think this would really be causing it..
Regards Alan
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)
Regards Alan
Alan Knowles wrote:
Another log from my wifes palm phone
Snappermail reports "Protocol error reading from server"
The log is here: http://docs.akbkhome.com/bincimap.log.txt
I suspect this is the continuation lines +\n are confusing the client.
Regards Alan
