<[email protected]> ha escrit:

> imap4d in GNU Mailutils 3.17 (Ubuntu package 1:3.17-1.1build3, not rebuilt)
> takes time that grows with the square of multipart nesting depth on
> FETCH

Yes, I know.  
 
> On imap4d --preauth, a legal 256 KiB message of 1007 nested multipart/mixed
> parts (a distinct boundary per level):

I don't think such messages happen often in practice, so the issue is
mostly of theorical nature.

> A nesting limit, or parsing each part once without rescanning the enclosing
> body, removes the quadratic cost.

Yes, of course. But setting the limit doesn't seem practical, whereas
caching the message structure would require introducing mailutils-specific
mailbox (or cache) format, both of which are hardly worth the effort, given
the above consideration.

Regards,
Sergey

Reply via email to