If the TCP idle timeout kicks in, or we time out trying to connect,
and the user isn't manually doing something sieve related (no job),
this isn't worth bothering the user about.
This typically happens some time after starting kmail, for the initial
The 2019 Akademy university network was the ideal testcase for this
(due to blocked ports) but I also regularly get this elsewhere.