> I think I have identified the remaining problems. Two of them. > > 1. Gmail sends data in a permuted order. When we ask for (BODY > [HEADER] > > BODY[TEXT]), Gmail sends (BODY[TEXT] BODY[HEADER]) which is formally > > correct. In practice, balsa's ideas about message was incorrect > (balsa > > looked for the headers and found none). The fix here is > straightforward, we just need to look closer at the sent data. > > 2. Gmail does not follow the RFC3501 when generating BODYSTRUCTURE > response. This response has "number-of-lines" field that is supposed > to > be present only for messages and text parts. Gmail sends it also for > > other parts, for example for application/pgp-signature. This > obviously > > confuses the parser... I have implemented a workaround for this but > the > right solution is to fix Gmail IMAP server. > > Anyway, attached patch fixes both of the problems for me. If I get > reports that it works as expected, I will commit it and release > 2.3.25. > Anyway, somebody should contact Gmail regarding point 2... > > Pawel
I've tested the patch and, so far, it's working with a default account configuration. It can be a tiny bit slow accessing the Inbox, but with the number of emails I have, I think it's normal. Thank you for the patch :) _______________________________________________ balsa-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/balsa-list
