Reformatted excerpts from Carl Worth's message of 2009-09-17: > The code was previously broken in calling EnclosedMessage.new with > only 2 instead of 5 arguments.
Thanks, this has been applied. > So I'm not 100% sure that this patch is correct, but it does allow > sup-sync to proceed and the message appears in sup as well as could be > expected, (the "extra" headers from the corrupted mime part appear in > the body as one might expect here). Yeah, I think that's the best we can hope for here. -- William <wmorgan-...@masanjin.net> _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
