From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] problems with rubymail on an initial sup-add/sync
Date: Wed, 19 Sep 2007 07:41:12 -0700 [thread overview]
Message-ID: <1190212675-sup-5699@south> (raw)
In-Reply-To: <20070919123616.GA24149@vual.tchpc.tcd.ie>
Excerpts from Jimmy Tang's message of Wed Sep 19 05:36:16 -0700 2007:
> [Wed Sep 19 13:32:59 +0100 2007] problem getting messages from mbox:///u1/trhpc/jtang/Mail/system.RequestTracker: For some bizarre reason, RubyMail was unable to parse this message.
Interesting. I've never seen that triggered, to date. Congratulations!
Basically this means I asked RubyMail to parse the message, and RubyMail
gave up.
> is there anyway of turning on more debugging to see whats causing the
> problem...?
Unfortunately no. The best I can offer is the following patch against
0.1, which will print out the message ids. You can then grep the mbox
for those and see if there's anything weird about the messages. I'm
guessing the MIME is screwed up in such a way that RubyMail chokes.
I'm interested in figuring out why this happens.
--- cut here ---
--- lib/sup/message.rb (revision 503)
+++ lib/sup/message.rb (working copy)
@@ -320,7 +320,7 @@
$1
end
- m.body && body = m.decode or raise MessageFormatError, "For some bizarre reason, RubyMail was unable to parse this message."
+ m.body && body = m.decode or raise MessageFormatError, "For some bizarre reason, RubyMail was unable to parse this message (#{m.header['message-id']})."
if charset
begin
--- cut here ---
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-09-19 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20070919-141338-+042.23-1@vual.tchpc.tcd.ie>
2007-09-19 12:36 ` Jimmy Tang
2007-09-19 14:41 ` William Morgan [this message]
2007-09-20 14:31 ` Jimmy Tang
2007-09-20 15:24 ` William Morgan
2007-09-19 22:44 ` Jimmy Tang
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=1190212675-sup-5699@south \
--to=wmorgan-sup@masanjin.net \
/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