Hi Jack: Am 13.07.18 22:04 schrieb(en) Jack via balsa-list:
I was first using "all" and switched to only "imap" when there was too much overhead from my untroubled pop3 access. Is the list of possibilities for G_MESSAGES_DEBUG documented anywhere?
If you use the latest git, just say “cat README”… ;-)
I'll play more with both imap and libnetclient turned on, but I still wonder if there could/should be more specific imap debug output.
This is somewhat difficult, as the low-level libnetclient stuff is shared between SMTP and POP3 and IMAP, of which each may have several threads running in parallel. OTOH, it will dump all the raw transactions between Balsa and the server, which will probably give the most details insights. In January, I submitted a patch [1] which would override the standard log function, printing the ID of the thread triggering the log message. This would enable you to filter (via grep) the messages from the relevant connection/thread only. However, that part of the patch never made it into the git repo. It should be possible to extract the part for src/main.c from it, though; I /think/ it will still work. Best Albrecht. [1] <https://mail.gnome.org/archives/balsa-list/2018-January/msg00016.html>
pgpyvPkRChnRv.pgp
Description: PGP signature
_______________________________________________ balsa-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/balsa-list
