Re: error In imap-parse-body 2 (Exchange 2007)

[Jake Colman <colman@ppllc.com>]

>>>>> "JC" == James Cloos <cloos@jhcloos.com> writes:

>>>>> "Jake" == Jake Colman <colman@ppllc.com> writes:

   Jake> (error/warning) Error in process filter: (error In imap-parse-body 2)

   Jake> In my imap-log, I see the following:

   Jake> "iso-8859-1") NIL NIL "quoted-printable" 47 7)("message" "rfc822" NIL
   Jake> NIL
   JC>                                                         ^^^^^^^   ^^^^^^

   JC> I posted a bug report about message/rfc822 parts a while back.
   JC> Including a debug trace.

   JC> I wasn't able to debug why it happens, but nnimap is unable to deal with
   JC> them.

   JC> (I should note that message/rfc822 parts have a significantly different
   JC> representation in an imap FETCH responce than any other mime type.  And
   JC> that code in imap.el/nnimap.el *looks* OK; it seems to have the right
   JC> logic.  And the abf in the comments matches what my imapd sends.
   JC> But something is nonetheless wrong.)

   JC> I was forced to route all of my incoming mail which has a message/rfc822
   JC> part to a non-imap folder using this procmail recipe:

   JC> ,----[ excerpt from ~/.procmailrc ]
   JC> | # push message/rfc822 mail to a nnmh folder since nnimap.el eats them.
   JC> | :0HBw
   JC> | * ^Content-Type: message/rfc822
   JC> |   RFC822/.
   JC> `----

   JC> I had confirmed that other imap clients like mutt and seamonkey had no
   JC> problem with such messages on my imapd, but didn't have any other imap
   JC> server to test against.  That you see it as well proves that it is not
   JC> specific to dbmail-imapd.

   JC> I wouldn't ming seeing this one squashed.

Interesting.  I assumed that this is part and parcel of my my company's
"upgrade" from Exchange 5.5 to Exchange 2007.  But I guess other servers
are broken too.

-- 
Jake Colman
Director of Software Development
Principia Partners LLC
101 West Elm Street
Suite 620
Conshohocken, PA  19428
+1 (610) 755-9786
www.principiapartners.com