Using v4.80

I haven't changed anything and I can still access my email using a browser, but for the last 2 days I can't download any of the new emails. I've closed and reopened Pegasus and rebooted my computer without luck.

Is there one corrupted email that is causing this?

Thanks

I get this login script:

14:51:46.925: --- 24 Apr 2023, 14:51:46.925 ---
14:51:46.927: Connect to 'mail.shirshalombuffalo.org', timeout 5 seconds.
14:51:47.952: >> +OK Dovecot ready.
14:51:47.952: << USER philip.herzbrun@shirshalombuffalo.org
14:51:48.021: >> +OK
<< 0017 PASS XXXXXXXXXX
14:51:48.138: >> +OK Logged in.
14:51:48.141: << STAT
14:51:48.210: >> +OK 12 40841479
14:51:48.210: << LIST
14:51:48.279: >> +OK 12 messages:
14:51:48.289: << RETR 1
14:51:48.359: >> +OK 22602618 octets

I don't have a definitive answer but I would see if I can identify those 12 messages via the web interface of the host, and delete or move all that not important in the hopes that one of them is causing the problem.

Also, the log shows that you have a timeout of 5 seconds. This seems awfully short to me. Is there a reason for it being set to 5? Default is 30. I set mine at 120 once a long time ago when troubleshooting and left it there ever since with no ill effects. I like to think it minimizes the chance of a timeout resulting from a transient interruption during a connection.

I discovered the evil email and forwarded it to a different account and then deleted it by using the browser....All the rest downloaded like normal.

That evil one is quite large....I wonder if that has anything to do with the problem?

THANKS!!!

I don't know. Perhaps the download of the message took longer than 5 seconds allow the timeout to trigger although a timeout should have been identifiable in the log. During my internet research I found one post about a similar occurrence where some sort of malware protection in a router was blocking a message thus stopping the download process. That was in the UK with a brand of router that I had never heard of so that situation is unlikely but demonstrates how difficult a failure like yours might be to track down.

I think this is going to be one of those mysteries that I'm never going to solve. (And don't really care about.)

Thanks for your help!!!