[Users] claws waits forever, freezes grafik on slower networks

[clawsmail at pasdzierny.de]

hi Paul;

thanks for spending the effort to reproduce, I guess the 'total network
interruption' case.

these questions I noted some days ago:

> ...
> you see from the log that the pop3 connection logs stops at a specific
> interaction. 
> - what are the exact parameters of the previous message sent ?
> - what exact status was it returned with ?
> - what is the next system call or network api call ?
> - and what status is it returned with ?
> - might there be a reason STERR is blocked (temporarily) so that the
>   real debug message is not seen ?
> - ... etc, you know the drill ;)
> 
> And why is the GUI system dependent on that at all ?
> ...


The main thing i wonder about is that eventually the GUI freezes,
sometimes seconds, sometimes 'forever'. 

GUI should not be related to *any* network io timeouts or other
concepts, should it ?

And yes, it probably does not make much sense to use longer timeouts
(as the log window explicitly suggests).
...rather than e.g. *retrying* the last failing action a couple of
times or even forever. 
... or sth completely different, dependent on what *exactly* goes wrong
always at the same step of the pop3 sequence, thats what the other
questions were about.

JM2C, Martin.

On Sat, 8 Feb 2025 10:37:59 -0000
Paul <paul at claws-mail.org> wrote:

> I can reproduce your problem, but only if I set the Network I/O
> timeout setting to a value that is longer than I am prepared to wait.
> 
> The Network I/O timeout setting was already mentioned in a response
> to you.
> 
> My suggestion to you is to set it to a value which matches your
> patience. For example, if you don't want to wait for more than 15
> seconds, set it to 15 seconds.
> 
> This, I believe, is the root of your problem, and it has nothing to
> do with your other guesses.
> 
> regards
> 
> Paul
> 
> 
> 
>