much better

[#1]

After my previous thread "not the best start" I have to say I had fingers crossed re: the actual switch over to plusnet. But, credit where credit's due. My broadband switched over without a hitch on wednesday and so far (touch wood) everything is very good. Speed is currently 4 x that of my previous ISP. Just one small niggle if anyone can help. When I access my email sometimes all goes fine but sometimes it seems to time out (for mail.plus.net only - not my other domain addresses) and I get the (outlook) credentials box asking to confirm password etc. why is this?
Thanks

[#2]

Hi whistler,
Not sure what could cause this, are you getting any error messages from outlook at all (other than the username/password related one I mean)? Also do you ever have the same problem logging into the webmail server (http://webmail.plus.net - with the same username and password you use in outlook)?

[#3]

Quote from: Matt

are you getting any error messages from outlook at all (other than the username/password related one I mean)?

No - I don't get any error messages. Like I say - it doesn't allways happen but more often than not.

Quote from: Matt

Also do you ever have the same problem logging into the webmail server (http://webmail.plus.net - with the same username and password you use in outlook)?

No - no problem at all.
It seems to me that when attempting to connect to your pop3 server, it times out a couple of times - things usually work on the 3rd or 4th attempt. This doesn't happen though on your smtp server - that works first time, every time.

[#4]

I too have had a similar experience for the last six or so weeks, using Outlook Express. Whilst it doesn't actually time out, after clicking Send/Recv it seems to hang for several seconds as though there was a large file coming when it is actually a small simple email with no attachments. I have assumed it was Norton Internet Security 2010 doing its thing for viruses and spam, but then I have used Norton products for many years without this happening before. No big deal, but an annoying little niggle.

[#5]

Quote from: Matt

Not sure what could cause this

So...... is that it? has it gone into the too difficult bucket?

[#6]

Nope
Next time it times out, can you try the steps below:
Start > Run > type in 'cmd'
Type the following:
telnet mail.plus.net 110
then press return.
You should get a response along the lines of

Quote

+OK Hello there.

Type in:
user username  press enter
pass password  press enter
Obviously replacing the italicised words with your details.
Make sure you type carefully as if you hit any incorrect key you have to start over.
You should then have something like this:

Quote

+OK Hello there. user myusername +OK Password required. pass ******** +OK logged in.

Let us know how you get on with that.

[#7]

If you're using Vista/Windows 7, Telnet isn't installed by default though.
You can use Putty or in Control Panel > Programs and Features > Turn On/Off Windows features > Telnet client

[#8]

Quote from: birdman

I too have had a similar experience for the last six or so weeks, using Outlook Express. Whilst it doesn't actually time out, after clicking Send/Recv it seems to hang for several seconds as though there was a large file coming when it is actually a small simple email with no attachments.

Are you set to 'leave messages on the server'?. As the number of messages on the server builds up, it takes longer to sift through & find the new ones.

[#9]

Quote from: Chris

Let us know how you get on with that.

Hi Chris
OK - first things first. Since you last posted I've synched my email maybe 30 times and it's worked first time every time - no problem. So much so I thought you guys had found and fixed something. Then at around 20:55 tonight it failed again so I did your telnet login and it worked fine. Tried email again and it failed, tried telnet - it worked - tried email and that finally worked 3rd time lucky.
At this point I'm thinking it may look to you like it's an email client thing. BUT I have several other email accounts on my web host service and at the moment also my old email (pop3 only) on my old ISP - and they all work absolutely fine. The only one out of my six pop3 accounts that does this is your mail.plus.net server.

[#10]

Would you mind deleting and then recreating the mail account just to make sure there's no corruption there that could be causing the issue? It might also be worth trying to access the account via IMAP to see if that makes any difference.

[#11]

Quote from: Matt

Would you mind deleting and then recreating the mail account just to make sure there's no corruption there that could be causing the issue?

At the moment its working fine and has been all morning - next time it fails I'll do this.

Quote from: Matt

It might also be worth trying to access the account via IMAP to see if that makes any difference.

How do I do this?

[#12]

Quote from: whistler

How do I do this?

You can either do it by accessing your mail via webmail or by setting up the account in your e-mail client as an IMAP account (in OE for example select IMAP instead of POP3) and then use imap.plus.net as the incoming server instead of mail.plus.net. (Don't just edit the server on the account in OE or Windows Mail - you'll need to add a new account.)

[#13]

ok - thought I'd see how things behaved over a few days. Still the same. I'd say on average probably 50% of attempts succeed/fail.
Telenet allways works.
Re-created pop3 account: no difference.
IMAP works no problem - though I only tried it for a few hours.
Done a bit of research. Could it be that your pop3 server max concurrent users setting is too low OR your pop3 server isn't man enough for the number of concurrent logins you generally get?
It's not a killer - just a bit of a PITA. Ironically it was about the one thing my previous ISP got right - c'est la vie.

[#14]

@Simon M

Quote

Are you set to 'leave messages on the server'?. As the number of messages on the server builds up, it takes longer to sift through & find the new ones.

Many thanks for your response and apologies for delay in replying. Yes, it is set to leave messages on server, but for only 2 days so not a huge amount of emails would build up. I have now set it up not to leave messages to see whether it makes much difference. It is a handy feature and I can always change back again.

[#15]

Quote from: whistler

Done a bit of research. Could it be that your pop3 server max concurrent users setting is too low OR your pop3 server isn't man enough for the number of concurrent logins you generally get?

Nope, I doubt that's a factor for a number of reasons. Firstly, there would be widespread reports of problems if this was the case. Secondly, your telnet tests would fail. Thirdly, our graphing/monitoring shows no suggestion of problems (the load balancer sessions paint a similar picture).

This does seem like a local problem TBH from the evidence you've provided. I'd go with removing *all* Plusnet mail accounts from your email application and settign up the ones you need again. That reminds me, do you have just the one Plusnet account set up or are there more?
My next piece of advice would be to temporarily disable any antivirus/security software to see if the problem still occurs (I'd only do this is you're behind a router, don't try it if you use a standalone USB modem).