Gnus development mailing list
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: Jake Colman <colman@ppllc.com>
Cc: ding@gnus.org
Subject: Re: error In imap-parse-body 2 (Exchange 2007)
Date: Thu, 03 Apr 2008 14:31:20 -0400	[thread overview]
Message-ID: <m3k5jessc0.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <76hceikhjy.fsf@dev-d01.ppllc.com> (Jake Colman's message of "Thu, 03 Apr 2008 12:51:45 -0400")

>>>>> "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 NIL
                                                        ^^^^^^^   ^^^^^^

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

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

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

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

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

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

I wouldn't ming seeing this one squashed.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6



  reply	other threads:[~2008-04-03 18:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 16:51 Jake Colman
2008-04-03 18:31 ` James Cloos [this message]
2008-04-03 20:51   ` Jake Colman
2008-04-10 13:46   ` Jake Colman
2008-04-10 13:58     ` Jake Colman
2008-04-10 14:46       ` James Cloos
2008-04-10 18:15         ` Jake Colman
2008-04-10 19:09         ` Ted Zlatanov
2008-04-16 20:21           ` Ted Zlatanov
2008-04-24 14:54             ` Jake Colman
2008-04-25  8:54               ` James Cloos
2008-04-25 16:23               ` Ted Zlatanov
2008-04-10 14:39     ` James Cloos
2008-04-10 18:17       ` Jake Colman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3k5jessc0.fsf@lugabout.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=colman@ppllc.com \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).