Hi Albrecht: On 05/12/2018 01:44:40 PM Sat, Albrecht Dreß wrote:
Hi all, sorry for the long delay – after a long time, I now have a /very/ preliminary patch for moving Balsa's IMAP support to GIO, via the libnetclient component. First, I tried to re-write larger parts of libbalsa/imap, and failed miserably, due to the complexity of the protocol and the implementation in Balsa.
☺
The approach I implemented is an extra layer on top of libnetclient, simulating the character-based approach of libbalsa/imap. There is room for improvement (e. g. as libnetclient *guarantees* lines are CRLF terminated, there is no need for extra checks in the IMAP layer). At least, the result is working for me. However, it is not yet finished (read: suitable for human consumption…), but I would highly appreciate if you could try the current status. As the patch is huge, please load it from <http://www.mynetcologne.de/~nc-dreszal/IMAP-Netclient.diff.bz2>. One not yet finished part (apart from thorough testing) is that the logic for configuring a IMAP account (in src/folder-conf.c) is not fully functional. Hovever, this module shares a lot of /almost/ duplicated code with src/mailbox-conf.c, which should be re-factored if possible. As always, any comment is really welcome! Cheers, Albrecht.
Thanks for the huge patch, and the huge effort that went into it! The patch applied cleanly, and Balsa built and is running. So far, no debug output when running with G_MESSAGES_DEBUG=imap; is that the correct G_LOG_DOMAIN? I can't tell whether Balsa is really talking to my IMAP server… Best, Peter
Attachment:
pgpodPQUDBRil.pgp
Description: PGP signature