From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Cc: Jake Colman <colman@ppllc.com>, Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: error In imap-parse-body 2 (Exchange 2007)
Date: Fri, 25 Apr 2008 04:54:33 -0400 [thread overview]
Message-ID: <m3od7yjov3.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <764p9r9ucj.fsf@dev-d01.ppllc.com> (Jake Colman's message of "Thu, 24 Apr 2008 10:54:20 -0400")
I forwarded that message to myself, bypassing the procmail rule which
would otherwise have kept it out of the dbmail store.
The exact packet dbmail-imapd sent to imap.el looks like:
=============================================================================
* 1 FETCH (RFC822.SIZE 5872 UID 1 BODY (("text" "plain" NIL NIL NIL "7BIT" 13 3)("message" "rfc822" NIL NIL NIL "7BIT" 4551 ("Thu, 24 Apr 2008 10:54:20 -0400" "Re: error In imap-parse-body 2 (Exchange 2007)" (("Jake Colman" NIL "colman" "ppllc.com"))(("Jake Colman" NIL "colman" "ppllc.com"))(("Jake Colman" NIL "colman" "ppllc.com"))(("Ted Zlatanov" NIL "tzz" "lifelogs.com"))(("James Cloos" NIL "cloos" "jhcloos.com")(NIL NIL "ding" "gnus.org")) NIL {91}
<86ej95lfdp.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 16 Apr 2008 15:21:54 -0500") "<764p9r9ucj.fsf@dev-d01.ppllc.com>")("text" "plain" NIL NIL NIL "7BIT" 1339 41) 119) "mixed") BODY[HEADER.FIELDS (Subject From Date Message-Id References In-Reply-To Xref To Newsgroups)] {227}
to: cloos@freeshell.org
subject: [Jake Colman] Re: error In imap-parse-body 2 (Exchange 2007)
message-id: <m3mynjqcbn.fsf@lugabout.jhcloos.org>
from: James Cloos <cloos@jhcloos.com>
date: Thu, 24 Apr 2008 15:31:17 -0400
)
=============================================================================
(OK, I did replace the CRLF line endings with LF line endings.)
The first interesting thing I see is that the tab in the In-Reply-To
header's value (from a continuation line) is still there. Dbmail
dropped the CRLF but did not convert the tab to a space.
I'll have to try it again with the patch.
(At least since I upgraded pgsql from 8.2 to 8.3 -- which included a
full dump and restore of the db's data -- and switched from having
xinetd run dbmail-imapd -n to having emacs do so -- which eliminated
the 50% idle time during startup -- it now takes somewhere between
10 and 20 minutes to startup rather than 3 hours or so....)
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2008-04-25 8:54 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
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 [this message]
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=m3od7yjov3.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=colman@ppllc.com \
--cc=ding@gnus.org \
--cc=tzz@lifelogs.com \
/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).