POP server issues.

[#1]

Thought I'd start this before we get a flood of complaints. Since around 11.15 this morning, my 'Mailwasher' program has been complaining of intermittent POP server fails, and the last time I attempted to download my messages, Thunderbird also reported no connection to the server (but only on 2 of my 5 mailboxes, the other 3 were OK).

This is leading me to believe the whole mail network (for POP at least), is liable to crash again, as it did a couple of times last year.

Any of the PN help team want to have a look?

[#2]

Me too! One of my three PN mailboxes keeps failing with a "no response" error.

[#3]

Hi there, we're not actually aware of any issues on the mail platform but feel free to send me a PM with the maibox names in question so I can check a few things on our side. 

[#4]

Another sufferer here. Has been progressing through my all PN mailboxes since late morning. Don't understand how this does not get monitored and picked up 😞

Ray.

[#5]

@adamwalker the last two checks on all my accounts failed, the first with a generic  response which means MW doesn't quite know what is happening, the second with a slightly more definite 'the server timed out'.

[#6]

@adamwalker

The last time something like this happened it was down to the load balancing server in front of the mail platform. As far as I remember it has two IP addresses and one of them wasn't picking up properly. The way round it was to manually configure the working IP address. That was a trial and error job after advice from Bob Pullen. If it's still happening tomorrow I'll look for some notes I made at the time and post them. Not at home at the moment.

[#7]

I found some notes on my tablet. The two IP addresses involved are (or were!) 212.159.9.81 and 212.159.8.81. Toggling between the two located the bad one. Might be worth trying as a starter for 10. Replace mail.plus.net with each one in turn to see if it makes any difference, although you might catch the bad one behaving when you try it.

[#8]

Noticed issues also this evening.

Had forgotten about the IP workaround, 212.159.9.81 works like a charm, appreciate the reminder!

[#9]

@adamwalker

The problem is still there this morning using mail.plus.net, but I can confirm @rd1956 's post that 212.159.9.81 cures it completely. In fact the server access time is almost instant using that IP address.

Looks to me as though last year's problem has returned. It was intermittent at first, but became a real annoyance.

[#10]

@nozzer - You are undoubtedly correct, but I am not messing about with the server settings - PN need to resolve the problem.

[#11]

All we need is to get someone to respond to this! 

[#12]

Yep, cos it's still happening. 

[#13]

Hi @smallblueplanet, @jab1, @nozzer, @rd1956 and @BoneMan,

I've emailed our incident management team, who inform me that this issue should now be fully resolved.

Are you able to confirm this?

[#14]

Errrm it seems worse than before, it's now failing to connect with ALL of the Plusnet accounts not just (a random) one of them.

Unable to send or receive messages for the ... account. The email server returned an error.

Server Error: 0x800CCC90
Server Response: -ERR Cannot connect to POP server 1.1.1.1 (1.1.1.1:110), connect error 10060
Server: 'mail.plus.net'
Windows Live Mail Error ID: 0x800CCC90
Protocol: POP3
Port: 110
Secure(SSL): No

Any help @OskarPapa?

[#15]

@OskarPapa

It's no different from before. Sometimes ok, sometimes failing to connect. The IP address we tried earlier though is perfect! It's connecting through mail.plus.net that's a problem.

Edit: Having said that, it suddenly seems to have improved quite a bit. Seems to connect now every time.