Sorry for the previous top-post. New info below.
Thanks Albrecht, but that produces no output. Including mbox-mbox in the debug list does provide appropriate output, so I at least know G_MESSAGES_DEBUG is working. It also does show appropriate output when I send a message. What would cause balsa to not even try to do a pop3 fetch? I've confirmed that my configured POP3 servers are set to check for mail on startup.Running with "G_MESSAGES_DEBUG-all" I see in the output
Jack
On 6/2/22 11:00, Albrecht Dreß via balsa-list wrote:
Hi Jack:
Am 01.06.22 00:24 schrieb(en) Jack via balsa-list:
A new problem just cropped up for me this morning. It used to be when I "Get new mail" I'd get a popup showing each of the servers from which I POP3 fetch mail, showing the status and progrss of each. Now, I just get a popup "Checking mail" but it doesn't show any of the servers, and only stays up for less than a second. I can use my IMAP connection to see that I do have new mail. Using $G_MESSAGES_DEBUG="mbox-pop3" produces no output. It seems like it's just silently failing to even try to do a pop3 fetch.
You might try with “G_MESSAGES_DEBUG=libnetclient” which dumps all low-level network traffic and see if the remote POP3 server reports any new messages for you: after logging in successfully, Balsa should send a line reading (time stamp etc. omitted)
DEBUG[libnetclient]: W 'LIST'
and the remote server should send a list of new messages (one line for each message), terminated by a line only containing a single dot:
DEBUG[libnetclient]: R '+OK scan listing follows'
[the list of new message uid's, may be completely empty]
DEBUG[libnetclient]: R '.'
Please DO NOT post the contents of the debug dump to the list, as is contains your password!
Hope this helps,
Albrecht.
**
(balsa:8879): DEBUG: 17:43:34.702: Network is
unavailable (Sun 05 Jun 2022 05:43:34 PM EDT)