YES, YES ... YEEESSS! Comcast/Xfinity has blown up my POP3 connectivity every six months or so over the course of many years. Calls to tech support are hopeless. Always the same line about assuring port numbers & etc are correct, but no real help. It's always something that changes on their end. Usually, the problem 'heals' itself Most often, the problem shows up as some sort of SSL/TLS error, often with error code 0x800CCC1A (encryption type issue), killing both send and receive. This started for me sometime on 25 January 21. More recently, they managed to get the outbound (SMTP) fixed, but it was coming up with 0x8004210A (timed out waiting for POP3 server) where the receive was now an issue, and would just time out. What is bizarre is that the credential and SSL/TLS process is supposed to be identical for send/receive connections. I'm hoping by posting both of those error codes above that searches for soluitions related to them point to your answer, as it resolved problems for both of those codes. With their POP3 service failing (do NOT mention the acronym IMAP, please!), I was forced to their WebMail, which in turn, ALSO began to fail after a couple of days with timeouts at the same time as the send side of my POP3 started working again. Even their own mail web page (the page where the user views and sends mail) acknowledged the problem, popping up a "Server unreachable" message in a little box at the bottom of the WebMail interface. My MTU was set to something on the order of 4700. I backed it down to the 'standard' 1500 that you used to resolve your problem, and amazingly enough, both WebMail and my POP3 Outlook mail are working again (not timing out). Anyway, thanks VERY much for the work required to set us straight. What tipped you to idea of making the minor change in the max packet size? Yes, the Wireshark log would be fascinating to review if it doesn't disclose too much.
... View more