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

[Jake Colman <colman@ppllc.com>]

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

>>>>> "JC" == James Cloos <cloos@jhcloos.com> writes:
   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
   JC> with
   JC> them.

   JC> (I should note that message/rfc822 parts have a significantly
   JC> different
   JC> representation in an imap FETCH responce than any other mime type.
   JC> 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
   JC> 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
   JC> 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.

   Jake> James,

   Jake> Can you think of any way I can avoid the problem?  I don't (think I)
   Jake> have the option of using a procmailrc recipe since my email is delivered
   Jake> directly to the IMAP server and I use Gnus as an IMAP client.  Is there
   Jake> something I can do to tell Gnus to avoid the problematic email?

   Jake> ...Jake

James,

Actually, even more important in the short-term, is there a way to force
Gnus to keep going if it encounters this error?  If I try to enter a
group that has this one of these messages, it simply hangs.  Then when I
hit C-g, I see the warning.  The only way to continue is for me to use a
different IMAP client to kill the offending message.  Can you think of a
better way?

...Jake


-- 
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