William, I was able to isolate my problem: For me, heliotrope-add hangs
for messages with more than 32768 content lines.
I have attached two mbox files, each containing a single message.
The message in good.mbox has 32768 content lines (excluding header) and
has no problem in heliotrope-add. The message in bad.mbox has 32769
content lines, and heliotrope-add hangs when trying to add this message.
I haven't yet tried to locate the locate the problem in the source.
Regards,
Gregor
* William Morgan <wmorgan-sup@masanjin.net> [Mi Mär 02 19:51:58 +0100 2011]
> Reformatted excerpts from Gregor Hoffleit's message of 2011-03-02:
> > I can't give away the mbox file. Any hints how I could debug the
> > heliotrope-server script?
>
> Can you isolate the message? It might be that it has a huge attachment
> that RMail is taking forever to parse, and that results in a client
> timeout.
>
> I need to move the message processing out of the request loop,
> obviously.
>
> As a workaround (which also is much faster), kill the server, wipe
> everything, and use `heliotrope-add -d <dir>` to import an mbox or
> maildir without having to go through HTTP.
>
> > Nice work otherwise! The web client is a nice demonstration of what
> > might come out of this project ;-)
>
> Thanks! I'm currently working on stripping everything out of Sup that
> will be handled by the server. The good news is that this is a LOT, and
> that Sup will be much leaner and meaner than before.
Attachment:
mbox-32768lines.tar.gz
Description: GNU Zip compressed data
_______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel