[sup-talk] problems with rubymail on an initial sup-add/sync

[William Morgan]

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>