From: James Cloos <cloos+math_uh-ding@jhcloos.com>
To: Simon Josefsson <simon@josefsson.org>
Cc: ding@gnus.org
Subject: Re: nnimap vs dbmail
Date: Thu, 24 May 2007 15:07:35 -0400 [thread overview]
Message-ID: <m3y7je59bl.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <87hcq34n98.fsf@mocca.josefsson.org> (Simon Josefsson's message of "Wed, 23 May 2007 16:40:03 +0200")
I have to take some time to write a full reply, but for now I'll just
note that all messages which have a message/rfc822 attachment trigger
the "In imap-parse-body 2" (assert) -- I have a corpus of examples if
anyone needs some -- and if I comment out the (asserts) some of those
emails will work in the *Article* buffer but w/ empty/default data in
the *Summary* buffer and some others do not show up at all. In every
case, though, mutt has no problems seeing, summarizing and displaying
all of the messages.
I'll followup again with a full replay as soon as I can write it.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2007-05-24 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 11:33 James Cloos
2007-05-23 14:40 ` Simon Josefsson
2007-05-24 19:07 ` James Cloos [this message]
2007-05-25 10:12 ` Simon Josefsson
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=m3y7je59bl.fsf@lugabout.jhcloos.org \
--to=cloos+math_uh-ding@jhcloos.com \
--cc=ding@gnus.org \
--cc=simon@josefsson.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).