Yes, that is more or less the right thing. Instead of mail_partial_body(stream, msgno, 0, 0, 0, 0); it would be more clear if you did mail_partial_text(stream, msgno, 0, 0, 0, 0);
Ok, I can do that. If I were you, I would do a mail_fetch_fast() of the entire mailbox first,
and then pass the actual message sizes as the "last" argument rather than passing 0.
Will doing that force the library to only fetch the desired number of bytes rather than reading until the end of the IMAP reply? A problem I've seen is that MS Exchange is broken and gives "estimates" of email sizes rather than actually saying how many bytes are in the message; sometimes it reports too many bytes, sometimes too few. I'd really like to get everybody to just abandon the piece of crap, but I guess it's not happening any time soon. Also, I would use a larger transfer size than "a few KB". This isn't
1987; we do have a bit more memory on our machines today. The smaller your transfer size, the slower it will be.
Yeah, good point; I could probably up the limit to many MB without getting in anything's way.
_______________________________________________ Imap-uw mailing list [email protected] https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
