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.
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.
It could just be a dodgy Outlook profile, which when deleted and setup again works fine. Wouldn't be the first time we've heard of that!
I can ping mail.freeola.net but can't telnet to port 110.
I set up a new profile last night but got the same result.
I've [temporrarily] switched all firewalls but that's had no effect either..... most odd.
I'll keep trying but any further suggestions are always welcome.
LGF
C:>ping mail.freeola.net
Pinging mail.freeola.net [81.31.99.8] with 32 bytes of data:
Reply from 81.31.99.8: bytes=32 time=39ms TTL=53
Reply from 81.31.99.8: bytes=32 time=39ms TTL=53
Reply from 81.31.99.8: bytes=32 time=38ms TTL=53
Reply from 81.31.99.8: bytes=32 time=39ms TTL=53
Ping statistics for 81.31.99.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 39ms, Average = 38ms
C:>
C:>telnet 81.31.99.8 110
Connecting To 81.31.99.8...Could not open connection to the host, on port 110: C
onnect failed
C:>telnet 81.31.99.8 110
Connecting To 81.31.99.8...Could not open connection to the host, on port 110: C
onnect failed
C:>tracert mail.freeola.net
Tracing route to mail.freeola.net [81.31.99.8]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.1
2 36 ms 35 ms 35 ms lns20.inx.dsl.enta.net [188.39.1.38]
3 35 ms 37 ms 35 ms gi1-10.inx.dist.dsl.enta.net [188.39.1.37]
4 35 ms 36 ms 35 ms te2-2.interxion.dsl.enta.net [78.33.141.89]
5 38 ms 35 ms 35 ms te2-3.interxion.core.enta.net [87.127.236.209]
6 39 ms 38 ms 39 ms te3-3.bir.core.enta.net [78.33.141.29]
7 39 ms 39 ms 39 ms te4-1.birmingham-te.core.enta.net [87.127.236.11
4]
8 39 ms 39 ms 39 ms te4-1.wolv-te.core.enta.net [87.127.236.150]
9 39 ms 39 ms 39 ms te1-1.telford-dc1.core.enta.net [87.127.236.17]
10 40 ms 39 ms 40 ms pop.freeola.net [81.31.99.8]
Trace complete.
...IMAP mail is fine and I've checked and rechecked all account settings.
Hi JTD,
I might have misread something here, but if you are using IMAP then doesn't that mean you should be using freeolamail.net - i.e. emailpro?
Eccles asked you to tracert mail.freeola.net which is standard non-IMAP email?
Is there some confusion with standard(free) email and emailpro settings? - Or as I mentioned it could just be me losing the plot! :¬P
[s]Hmmm...[/s]
EDIT:
For me both standard and emailpro accounts are working fine this morning.
Hi All,
Anyone having problems with POP3/SMTP email (non-VIP)?
Might be me getting confused the Hmmm. We don't have a 'VIP' mail package as such, this would be EmailPro. So as you said 'Non-VIP' I assumed you meant our normal email service than only provides POP3 and SMTP and uses mail.freeola.net. Which mail service is it you're trying to use?
Looks like I haven't explained myself as clearly as I thought I had.
It is nonVIP email-freedom POP.
I only mentioned IMAP working fine as I also have other profiles using email-pro which eliminated any network issues that might have been causing the problem.
The error messages just say I can't connect to the pop server. It doesn't indicate wheteher that is a newtork connection problem or an authentication issue.
It's interesting that I can ping mail.freeola.net but not telnet to port 110 - regardless of which type of mail I have.
Hope that's a bit clearer.
JTD
Yep, IMAP did confuse things for me :¬)
So it's standard Freeola email with 'freedom' enabled.
Perhaps there's an issue with your 'freedom' account - BUT that should only present itself if you are having issues 'sending' not 'receiving'.
To try to get some more meaningful message from Outlook you might like to try the 'Test Account Settings' option and see what that says?
You might be better waiting for Eccles/Freeola Support to investigate in case I just confuse things though.
[s]Hmmm...[/s]
Sorry for throwing in the IMAP red herring :o)
It was the 'test account' report which came back with the unhelpful messages.
Things are a bit clearer in the meantime. I have fred up an old(ish) pc I had in my garage and I can telnet to port 110 on the mail server.... so it's looking like something wrong with my laptop/outlook setup.
Thanks for your help but I reckon this one is down to me to fathom out what's going on.
bl**dy Microsoft. sigh.
JTD
OMG.... out of absolutley nowhere it started to work again.
I've spent two days trying to work out what's going on and after another (of many) reboots Outlook suddenly pops up and asks for my password.
I check telenet and that's OK too.
The only thing I did before this reboot was switch automatic updates back on (really clutching at straws as to what I'd done before the problems started) - XP installed one update and shut down.
When it came back up all was well.
If that hadn't worked I was on the verge of a system restore. So I'm pleased it's working again but very puzzeld as to why it stopped in the first place.
Many thanks for all suggestions and system checks.
JTD