>Can you attach strace (you just add strace to fetchmail's command line) >and report the last few lines around where things start looking like >fetchmail running into timeouts (SIGALRM is one such sign) or socket >trouble (read errors), and/or also the last few lines of a tcpdump >running in parallel and filtering on traffic to 79.98.45.16/110?
In principle, this is possible, as I have deleted the offending messages from the webmail interface, and the messages are in the trash and I could recover it. In practice this is very difficult: it would take a lot of time for me to try and do it. Especially because that would have to be done while my personal email keeps arriving at my mailbox. However, tomorrow I may try to do something. >Also, does it take a long time between starting to read the message 3 >(see below) and before fetchmail fails? Almost certainly less than one minute. >I need to understand, from strace (or ltrace) and tcpdump, what are the >last few log lines around the connection getting reset and what the >software is doing. Ok, I'll see if I can manage to find the time and at least do an strace. -- Francesco Potortì (ricercatore) ISTI - CNR, Pisa, Italy Web: http://fly.isti.cnr.it Skype: wnlabisti Mobile: +39.348.8283.107 also Telegram, and even Wa
