@wignomore wrote:Telnet yes, and I've just googled raw pop3 🙂
I just logged into mail.btinternet.com via telnet, and although stat shows there are 3 messages, list only shows the two visible ones:
+OK Maildrop ready, (JPOP server ready).
stat
+OK 3 59298
list
+OK 3 message(s) (59298 octets).
1 8419
2 7124
.
Any advice on specific commands to try would be gratefully received - thanks!
After you've saved those two emails, or the ones you can get at - try telnet again and if the list command still shows 1 with no emails listed, try the dele command like dele 1 which should fail.
You could try telnet to IMAP port 143 I believe, you can then do a list command to show all folder emails
list "" "*"
and see what happens.
Anyway, the mail team should be able to reset the mailbox.
Many thanks all. I followed the "contact the mods" link as suggested.
Much appreciated!
With thanks again to those here, and to Dan who texted me, the issue is now resolved. Much appreciated!
I spotted that email was coming through before Dan got back to me (which to be fair, he said he would do sometime today!). I’ll post later once I hear from him.
thanks!
@wignomore wrote:I spotted that email was coming through before Dan got back to me (which to be fair, he said he would do sometime today!). I’ll post later once I hear from him.
thanks!
Is the message count now back to normal?
Hi Andy,
Yes, it’s now showing the correct number of unread emails in the summary pane (as well as being able to download emails to my devices).
thanks.
Hi @wignomore,
I raised this directly with Yahoo. They in turn sent it to the engineering teams who were able to fix the problem. It wasn't something that we could fix here as it was a fault at Yahoo's end.
Would you like me to look into anything else for you @wignomore or are you happy that I've resolved everything?
Thanks
DanielS
That's perfect @wignomore.
To be perfectly honest, I pushed for an explanation but haven't been given an in depth answer. Basically, I've reported it to them and they've left it with the engineering team who were able to work out the problem. Unless it has affected a multitude of users the information I get back is limited.
Thanks
DanielS