Created attachment 1698 [details] claws network log of interrupted logins Configuration of POP3 and IMAP accounts. IMAP triggers a 'Keep Alive' NOOP command during POP3 login/negotiation' and the POP3 login 'times out' and fails. Log extracts attached. Other POP3 connections are successful and once connected are never interrupted no matter how long the duration of message download & deletion. The same POP accounts will connect normally at other times.
(In reply to comment #0) > Created attachment 1698 [details] > claws network log of interrupted logins > > Configuration of POP3 and IMAP accounts. > > IMAP triggers a 'Keep Alive' NOOP command during POP3 login/negotiation' and > the POP3 login 'times out' and fails. > > Log extracts attached. > > Other POP3 connections are successful and once connected are never > interrupted no matter how long the duration of message download & deletion. > > The same POP accounts will connect normally at other times. IMAP connections run in separate threads with different sockets, no way they can interrupt another open connection AFAIK. The network log is a shared resource and messages from different protocols or sessions may be mixed, but that doesn't mean connections to the servers are shared. In fact your log shows a clear example of a POP account which also timeouts without any other message in between: ,----- | * Account 'uk-drills-non-delivery': Connecting to POP3 server: 94.76.203.118:110... | ** Session timed out. You may be able to recover by increasing the timeout value in Preferences/Other/Miscellaneous. `----- So, I think that the POP server was simply having connectivity problems at wrong moment.