A friend of mine is having all kinds of issues with his POP3 email account. He consistently has issues with server timeouts, slow to login to receive emails, 30 sec - 1 min is normal. At times, he will randomly receive duplicate copies of the same email in his inbox, not be able to delete emails, or sent email receipts.
Are there known issues with POP3 accounts? Would switching to an IMAP account offer any benefit or resolve these issues? Are POP3 accounts still being supported?
I have another friend using the same software and OS (Windows Live Mail 2012 / Windows 10), using IMAP with no issues.
Thank you for posting email concerns on your friend's behalf.
Even though we still support POP3, we recommend using IMAP. If your friend access emails primarily on a single device then he can continue using POP3. You can define the frequency of checking for new messages in the mail client.
Community - anybody using POP3, please share your experience.
Thanks for the replies.
I will try another email client and see if that's the issue, if not I'll switch to IMAP and see. He only uses his computer for checking emails, so whichever works more reliably is fine. I was more worried POP3 being older, was not supported anymore, which could have been causing the issues.
I'm assuming that using Webmail works properly?
I also occasionally got duplicate e-mails a couple of years ago when there were problems with Rogers/Yahoo. I now avoid getting duplicates on Outlook by keeping my inbox in webmail clean, except for one e-mail to preclude the ads that pop up there if you don't have at least one e-mail. In Webmail I move all but one e-mail to various folders when in webmail. This also gives me a duplicate set of e-mails "in the cloud". The ones on Webmail and the ones on my Outlook client on my computer. This also allows me to work "offline" in Outlook. Of course there are advantages to IMAP like synching all your devices, however, if you only have one device, POP3 should work fine.
For the past 2 days, I have not been able to access my Rogers Mail via POP in my Outlook. it keeps prompting me for my password, which I know works since i am able to access my mail thru the browser.
Yes my settings are correct as I have been using POP for years. It's just the last couple of days that it is not working.
Is there a current issue with the service that I need to wait for it to work again?
If you have not updated to an app password, this has been rolled out during the past couple of years. Just because something has worked for many years doesn't mean that it's not affected by changes to the e-mail system:
Here's the FAQ on how to set things up, including the app password at the bottom of the link.
For over the past year, I have been having a problem retrieving my Rogers POP3 e-mails that I access through Windows Live Mail. After many contacts with Rogers, and several reviews of my set-up etc. with no resolution, I decided to troubleshoot the problem myself. I know that Windows Live Mail is no longer supported and that IMAP is recommended over POP3, but neither of those 'scapegoat' suggestions is the cause of this problem. This problem is intermittent and usually it's a matter of playing Russian roulette until I land on a 'good' server that will retrieve my e-mails.
The problem I am experiencing appears to be related to one 'dud' server in a pool of five units. Using the Ping and TraceRoute diagnostics of my Rogers modem, I determined that the domains; pop.broadcast.rogers.com, pop.nl.rogers.com, and pop.mail.yahoo.com, all use the same pool of POP3 e-mail servers. However, they don't appear to select them in the same access sequence. I have identified the five IP addresses as follows: 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, and 126.96.36.199. Using the website www.wormly.com access Tools/POP3/SSL for any of the domains mentioned, I determined that the server 188.8.131.52 is the unit that has an issue, since never passes the POP3 test. I get "ERROR: Couldn't connect to POP3 service. POP3 test failed". The other 4 units appear to work fine, as far as I can determine from this basic test.
This information was reported to Rogers last year, and I talked to several people, including supervisors, but no one seemed to know how to contact the server's owner (Yahoo or a third party provider??) to have this 'dud' unit fixed, or removed from service. So this problem still exists, and during busy periods, trying to quickly retrieve e-mails is totally frustrating.
Hopefully someone from Rogers (who has some familiarity with their mail-server network) will pick up on this problem and refer it to the appropriate people for investigation and repair. I appreciate the help of their Internet techs but this issue seems to be outside of the scope of their knowledge.
Does this issue sound familiar to anyone else using POP3?
I have the following comments:
1. I use POP and don't have any issues using Outlook as my client, so I don't believe it's strictly a server issue since lots of people still use POP and I haven't seen any reports like yours. Not sure why one server is worse than others.
2. Per the first link in post 7 of this thread, app passwords need to be updated.
3. Since you're using an unsupported client and since you're in the minority from what I can tell from posts here, you may not get much "action" by technical support on your issue.
4. You may wish to consider switching to a supported client.
Thanks for the prompt reply.
A couple of things I would like to comment on in regards to your answer.
1/ Depending on which domain name you use, this problem may manifest itself less frequently. I was instructed to set up on pop.nl.rogers.com. I don't know if you tried the test access at www.wormly.com, but if you do, you will see that the IP for the dud server I identified fails every test attempt. You didn't say what your domain was, so if it not one of the domains I mentioned, you may be accessing different servers, hence you wouldn't have the problem.
2/ I being through the set-up procedures several time with the Rogers people, changed apps. etc. and nothing clears the problem.
3/ I think I may be tainted by the "unsupported client" factor because many of the Rogers tech people tend to blame Windows Live Mail using POP3, and have tunnel vision when it comes to looking beyond that conclusion. If the trouble was there continuously, I would be more inclined to believe that possibility. But when it works fine most of the time, I am more inclined to believe that the dud server is the main issue, especially at times when the servers are really busy.
4/ Over the years I have switched e-mail clients a number of times, but on most of the platforms, there has always been other issues that come up . If Rogers were to fix/eliminate the dud server and the problem still persisted then I would seriously consider moving to a new platform. You just can't keep people switching around every time there is a problem that Rogers doesn't know how or are not willing to troubleshoot.
I will wait and see if anybody from Rogers picks up on this issue and has the wherewithal to pass it on the network people who look after their assigned servers.