The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
Hi All,
Anyone having problems with POP3/SMTP email (non-VIP)?
I upgraded from Outlook 2003 to Outlook 2010 yesterday and haven't received any POP3 emails since 09:51 - but this may just be a coincidence.
I can see in my webmail view that there are mails waiting to be picked up.
IMAP mail is fine and I've checked and rechecked all account settings.
Error message from outlook is a particularly unhelpful 'unable to connect to pop3/smtp server'.
So, before I start to uninstall/reinstall accounts can I rule out a server problem?
thanks
JTD
Edit: changing smtp auth to ssl port 465 seems to have got that going but still no pop3.
Anyone having problems with POP3/SMTP email (non-VIP)?
I upgraded from Outlook 2003 to Outlook 2010 yesterday and haven't received any POP3 emails since 09:51 - but this may just be a coincidence.
I can see in my webmail view that there are mails waiting to be picked up.
IMAP mail is fine and I've checked and rechecked all account settings.
Error message from outlook is a particularly unhelpful 'unable to connect to pop3/smtp server'.
So, before I start to uninstall/reinstall accounts can I rule out a server problem?
thanks
JTD
Edit: changing smtp auth to ssl port 465 seems to have got that going but still no pop3.
Page:
Outlook works in mysterious ways! Glad you got it working again though. I use Mozilla Thunderbird personally and the most recent version is pretty good. Sadly they are ceasing development to concentrate on browser stuff.
Glad to hear you are all sorted JTD.
As telnet also started working for you this doesn't sounds as it was an Outlook issue.
I'm an Outlook fan - I use it to run my life. The calendar functions are great :¬)
As telnet also started working for you this doesn't sounds as it was an Outlook issue.
I'm an Outlook fan - I use it to run my life. The calendar functions are great :¬)
[s]Hmmm...[/s] 
It sounds to me like a routing / firewall issue. If it happens again, I'd suggest restarting your router to clear any cached data. If that doesn't help, it's likely to be a firewall blocking the connection to mail.freeola.net:110.
Hi dean,
That's what I thought too and it's why I dug an old PC out to fire up. When that could telnet OK it couldn't have been a ISDN frouter/firewall issue and must have been a local laptop issue.
Hmmm... yeah, I'd come to the conclusion it wasn't an outlook issue too and started to check blocked sites/port issues...still found nowt.
I wish I had a clear answer as to what had happened but I haven't. I'll not lose too much sleep over it though.
Case closed. Nothing more to see here.
JTD
That's what I thought too and it's why I dug an old PC out to fire up. When that could telnet OK it couldn't have been a ISDN frouter/firewall issue and must have been a local laptop issue.
Hmmm... yeah, I'd come to the conclusion it wasn't an outlook issue too and started to check blocked sites/port issues...still found nowt.
I wish I had a clear answer as to what had happened but I haven't. I'll not lose too much sleep over it though.
Case closed. Nothing more to see here.
JTD
If you were able to connect from another computer, that rules out the router, however it could have still been a firewall on the original PC. As Hmmm... said, if it was Outlook, you would have been able to telnet.
The most likely thing I would expect this to have been is a firewall issue on the local computer. Hopefully it wont happen again, but if it does, I'd advise starting by ensuring that Outlook is on the exceptions list on your firewall software.
The most likely thing I would expect this to have been is a firewall issue on the local computer. Hopefully it wont happen again, but if it does, I'd advise starting by ensuring that Outlook is on the exceptions list on your firewall software.
dean5 wrote:
If you were able to connect from another computer, that rules out the router, however it could have still been a firewall on the original PC. As Hmmm... said, if it was Outlook, you would have been able to telnet.
The most likely thing I would expect this to have been is a firewall issue on the local computer. Hopefully it wont happen again, but if it does, I'd advise starting by ensuring that Outlook is on the exceptions list on your firewall software.
-------------------------------- --------------------------------
@dean5
JTD has closed this, but... :¬)
Just trying to work through the logic of your last post.
If the problem returns, surely the first thing to try is telnet as that's not application dependant?
If you were able to connect from another computer, that rules out the router, however it could have still been a firewall on the original PC. As Hmmm... said, if it was Outlook, you would have been able to telnet.
The most likely thing I would expect this to have been is a firewall issue on the local computer. Hopefully it wont happen again, but if it does, I'd advise starting by ensuring that Outlook is on the exceptions list on your firewall software.
-------------------------------- --------------------------------
@dean5
JTD has closed this, but... :¬)
Just trying to work through the logic of your last post.
If the problem returns, surely the first thing to try is telnet as that's not application dependant?
[s]Hmmm...[/s] Page: