Re: can't fetch mail
Jack Ostroff via balsa-list <[email protected]> Tue, 7 Jun 2022 14:06:22 -0400
| Newsgroups | gmane.comp.gnome.apps.balsa |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============4328198967412752330== Content-Type: multipart/alternative; boundary="------------u94wq2ub9lNmbpuL5aPCQ0tW" Content-Language: en-US This is a multi-part message in MIME format. --------------u94wq2ub9lNmbpuL5aPCQ0tW Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Good timing - I'm finally digging into this right now. My smtp test send was through gmail, so not local. I'm now compiling gtk with debug symbols to see if I can find why it might think the network is missing, or at least trace into those g_network calls. The "route" command DOES show a "default" route to my router, to which I have a wired connection. I also do NOT see any network-changed messages. "grep -i network" on the output gives me: (process:8898): GLib-GIO-DEBUG: 17:43:34.475: Failed to initialize portal (GNetworkMonitorPortal) for gio-network-monitor: Not using portals (process:8898): GLib-GIO-DEBUG: 17:43:34.478: _g_io_module_get_default: Found default implementation networkmanager (GNetworkMonitorNM) for ?gio-network-monitor? (balsa:8879): GLib-GIO-DEBUG: 17:43:34.700: Failed to initialize portal (GNetworkMonitorPortal) for gio-network-monitor: Not using portals (balsa:8879): GLib-GIO-DEBUG: 17:43:34.702: _g_io_module_get_default: Found default implementation networkmanager (GNetworkMonitorNM) for ‘gio-network-monitor’ ** (balsa:8879): DEBUG: 17:43:34.702: Networkis unavailable (Sun 05 Jun 2022 05:43:34 PM EDT) Of course I do not have an example from when it used to work just fine. All I can assume now is that something else I upgraded early last week is causing a problem, but I won't be surprised if I'm surprised at how stupid the problem is, once I find it. Update later today. Jack On 6/7/22 13:54, Albrecht Dreß via balsa-list wrote: > Hi Jack! > > Am 05.06.22 23:54 schrieb(en) Jack Ostroff via balsa-list: >> ** (balsa:8879): DEBUG: 17:43:34.702: Networkis unavailable (Sun 05 >> Jun 2022 05:43:34 PM EDT) > > That message is printed by function print_network_status() in > src/main-window.c. Balsa uses a GNetworkMonitor (returned by calling > g_network_monitor_get_default()) to check if the network is available > or not. If you see this message only /once/, it is most like being > emitted from balsa_window_init() (in the same source file) using the > return value of calling g_network_monitor_get_network_available(). > The docs say > > <quote> > Checks if the network is available. "Available" here means that the > system has a default route available for at least one of IPv4 or IPv6. > It does not necessarily imply that the public Internet is reachable. > </quote> > > We connect to the “network-changed” of the monitor, which should print > a similar message whenever the network state changes. > >> 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. > > In libbalsa/server.c (libbalsa_server_test_can_reach*) we have > additional functions for checking if a remote server is reachable, > which internally call g_network_monitor_can_reach_async() and > g_network_monitor_can_reach_finish(). I can only guess that there > /might/ be an issue with your network or the gio configuration. SMTP > may work if you use a local MTA (localhost or 127.0.0.1) as that > address should always be reachable. > > Best, Albrecht. > > _______________________________________________ > balsa-list mailing list > [email protected] > https://mail.gnome.org/mailman/listinfo/balsa-list --------------u94wq2ub9lNmbpuL5aPCQ0tW 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>Good timing - I'm finally digging into this right now. My smtp test send was through gmail, so not local. I'm now compiling gtk with debug symbols to see if I can find why it might think the network is missing, or at least trace into those g_network calls. The "route" command DOES show a "default" route to my router, to which I have a wired connection. I also do NOT see any network-changed messages. "grep -i network" on the output gives me:<br> </p> <p><span style="font-family:monospace"><span style="color:#000000;background-color:#ffffff;">(process:8898): GLib-GIO-DEBUG: 17:43:34.475: Failed to initialize portal (G</span><span style="font-weight:bold;color:#ff5454;background-color:#ffffff;">Network</span><span style="color:#000000;background-color:#ffffff;">MonitorPortal) for gio-</span><span style="font-weight:bold;color:#ff5454;background-color:#ffffff;">network</span><span style="color:#000000;background-color:#ffffff;">-monitor: Not using portals </span><br> (process:8898): GLib-GIO-DEBUG: 17:43:34.478: _g_io_module_get_default: Found default implementation <span style="font-weight:bold;color:#ff5454;background-color:#ffffff;">network</span><span style="color:#000000;background-color:#ffffff;">manager (G</span><span style="font-weight:bold;color:#ff5454;background-color:#ffffff;">Network</span><span style="color:#000000;background-color:#ffffff;">MonitorNM) for ?gio-</span><span style="font-weight:bold;color:#ff5454;background-color:#ffffff;">network</span><span style="color:#000000;background-color:#ffffff;">-monitor? </span><br> (balsa:8879): GLib-GIO-DEBUG: 17:43:34.700: Failed to initialize portal (G<span style="font-weight:bold;color:#ff5454;background-color:#ffffff;">Network</span><span style="color:#000000;background-color:#ffffff;">MonitorPortal) for gio-</span><span style="font-weight:bold;color:#ff5454;background-color:#ffffff;">network</span><span style="color:#000000;background-color:#ffffff;">-monitor: Not using portals </span><br> (balsa:8879): GLib-GIO-DEBUG: 17:43:34.702: _g_io_module_get_default: Found default implementation <span style="font-weight:bold;color:#ff5454;background-color:#ffffff;">network</span><span style="color:#000000;background-color:#ffffff;">manager (G</span><span style="font-weight:bold;color:#ff5454;background-color:#ffffff;">Network</span><span style="color:#000000;background-color:#ffffff;">MonitorNM) for ‘gio-</span><span style="font-weight:bold;color:#ff5454;background-color:#ffffff;">network</span><span style="color:#000000;background-color:#ffffff;">-monitor’ </span><br> ** (balsa:8879): DEBUG: 17:43:34.702: <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> <br> </span>Of course I do not have an example from when it used to work just fine. All I can assume now is that something else I upgraded early last week is causing a problem, but I won't be surprised if I'm surprised at how stupid the problem is, once I find it.</p> <p>Update later today.</p> <p>Jack<span style="font-family:monospace"><br> </span></p> <div class="moz-cite-prefix">On 6/7/22 13:54, Albrecht Dreß via balsa-list wrote:<br> </div> <blockquote type="cite" cite="mid:[email protected]">Hi Jack! <br> <br> Am 05.06.22 23:54 schrieb(en) Jack Ostroff via balsa-list: <br> <blockquote type="cite">** (balsa:8879): DEBUG: 17:43:34.702: Networkis unavailable (Sun 05 Jun 2022 05:43:34 PM EDT) <br> </blockquote> <br> That message is printed by function print_network_status() in src/main-window.c. Balsa uses a GNetworkMonitor (returned by calling g_network_monitor_get_default()) to check if the network is available or not. If you see this message only /once/, it is most like being emitted from balsa_window_init() (in the same source file) using the return value of calling g_network_monitor_get_network_available(). The docs say <br> <br> <quote> <br> Checks if the network is available. "Available" here means that the system has a default route available for at least one of IPv4 or IPv6. It does not necessarily imply that the public Internet is reachable. <br> </quote> <br> <br> We connect to the “network-changed” of the monitor, which should print a similar message whenever the network state changes. <br> <br> <blockquote type="cite">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> </blockquote> <br> In libbalsa/server.c (libbalsa_server_test_can_reach*) we have additional functions for checking if a remote server is reachable, which internally call g_network_monitor_can_reach_async() and g_network_monitor_can_reach_finish(). I can only guess that there /might/ be an issue with your network or the gio configuration. SMTP may work if you use a local MTA (localhost or 127.0.0.1) as that address should always be reachable. <br> <br> Best, Albrecht.<br> <br> <fieldset class="moz-mime-attachment-header"></fieldset> <pre class="moz-quote-pre" wrap="">_______________________________________________ balsa-list mailing list <a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:[email protected]">[email protected]</a> <a class="moz-txt-link-freetext" href="https://mail.gnome.org/mailman/listinfo/balsa-list">https://mail.gnome.org/mailman/listinfo/balsa-list</a> </pre> </blockquote> </body> </html> --------------u94wq2ub9lNmbpuL5aPCQ0tW-- --===============4328198967412752330== 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 --===============4328198967412752330==--