Re: can't fetch mail
Jack Ostroff via balsa-list <[email protected]> Sun, 5 Jun 2022 17:54:10 -0400
| Newsgroups | gmane.comp.gnome.apps.balsa |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============7019139230138236834==
Content-Type: multipart/alternative;
boundary="------------D0wiFzYPlcMXiC5ECyCJBiBv"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------D0wiFzYPlcMXiC5ECyCJBiBv
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Sorry for the previous top-post. New info below.
On 6/2/22 11:19, Jack via balsa-list wrote:
> 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.
>
> 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.
Running with "G_MESSAGES_DEBUG-all" I see in the output
** (balsa:8879): DEBUG: 17:43:34.702: Networkis unavailable (Sun 05 Jun
2022 05:43:34 PM EDT)
but I have no idea if this really indicates some network problem or is
just a red herring (false lead) as balsa is able to send messages by
smtp. Next step will be to debug and look for a backtrace from the
place that message is printed.
--------------D0wiFzYPlcMXiC5ECyCJBiBv
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Sorry for the previous top-post. New info below.<br>
</p>
On 6/2/22 11:19, Jack via balsa-list wrote:<br>
<blockquote type="cite"
cite="mid:[email protected]">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.
<br>
<br>
Jack
<br>
<br>
On 6/2/22 11:00, Albrecht Dreß via balsa-list wrote:
<br>
<br>
<blockquote type="cite">Hi Jack:
<br>
<br>
Am 01.06.22 00:24 schrieb(en) Jack via balsa-list:
<br>
<blockquote type="cite">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.
<br>
</blockquote>
<br>
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)
<br>
<br>
DEBUG[libnetclient]: W 'LIST'
<br>
<br>
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:
<br>
<br>
DEBUG[libnetclient]: R '+OK scan listing follows'
<br>
[the list of new message uid's, may be completely empty]
<br>
DEBUG[libnetclient]: R '.'
<br>
<br>
Please DO NOT post the contents of the debug dump to the list,
as is contains your password!
<br>
<br>
Hope this helps,
<br>
Albrecht.
<br>
</blockquote>
</blockquote>
Running with "G_MESSAGES_DEBUG-all" I see in the output<br>
<p><span style="font-family:monospace"><span
style="color:#000000;background-color:#ffffff;">**
(balsa:8879): DEBUG: 17:43:34.702: </span><span
style="font-weight:bold;color:#ff5454;background-color:#ffffff;">Network</span><span
style="color:#000000;background-color:#ffffff;"> is
unavailable (Sun 05 Jun 2022 05:43:34 PM EDT)</span><br>
</span></p>
<div class="moz-cite-prefix">but I have no idea if this really
indicates some network problem or is just a red herring (false
lead) as balsa is able to send messages by smtp. Next step will
be to debug and look for a backtrace from the place that message
is printed.<br>
</div>
<br>
</body>
</html>
--------------D0wiFzYPlcMXiC5ECyCJBiBv--
--===============7019139230138236834==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
balsa-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/balsa-list
--===============7019139230138236834==--