Thunderbird reporting "Login to server mail.force9.net with username ####### failed."

[#1]

which now looks to be at Greenby, no longer at Plusnet

Your email is still at Plusnet. What has moved is the proxy server. This has been changed to allow access to mail accounts both before and after migration , whenever it happens.

[#2]

---

@MisterW wrote:

which now looks to be at Greenby, no longer at Plusnet

Your email is still at Plusnet. What has moved is the proxy server. This has been changed to allow access to mail accounts both before and after migration , whenever it happens.

---

Thanks, it's good to have some facts!

[#3]

...but it's still not working 100% though...

[#4]

What is “it” and what is the failure “experienced”?

What was being attempted and the errors encountered help inform the investigations.

[#5]

---

@Townman wrote:

What is “it” and what is the failure “experienced”?

What was being attempted and the errors encountered help inform the investigations.

---

As in the thread title and the opening message - when Thunderbird is polling pop3 for new mail, it reports "Login to server mail.force9.net with username ####### failed.". Polling other servers, including mail.plus.net, are working as normal.

It's just force9 that's flaky. Looks as though it last worked at 17:44, it's been mostly failing all afternoon, although has occasionally worked for a brief periods. Not working now.

[#6]

Can you please try the email server diagnostic - link below.

[#7]

---

@Townman wrote:

Can you please try the email server diagnostic - link below.

---

Typical... it's working again now... Thunderbird is happy and all three curl commands are successful too.

If it stops working again, i'll repeat the curl commands and send further info.

[#8]

Oh no it's not...........

[#9]

Yes, not working for me either again this morning.

@Townman here's some diag info, see attached file for full output

imap and pop3 look to be timing on authentication? (bas64(?) password(?) obscured...) ...

....

> A002 AUTHENTICATE PLAIN
< +
> xxxxxxxxxxxxxxxxxxxxxxxx=
* response reading failed
* Closing connection 0
* TLSv1.2 (OUT), TLS alert, close notify (256):
curl: (56) response reading failed
exit code:1

smtp looks to work fine.

[#10]

Not working for me on Force9 either. Webmail login also fails.

curl.exe -v pop3s://mail.force9.net -u xxxx@xxxx.f9.co.uk

Enter host password for user 'xxxx@xxxx.f9.co.uk':
* Host mail.force9.net:995 was resolved.
* IPv6: (none)
* IPv4: 91.204.208.196
* Trying 91.204.208.196:995...
* schannel: disabled automatic use of client certificate
* schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - The revocation function was unable to check revocation for the certificate.
* closing connection #0
curl: (35) schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - The revocation function was unable to check revocation for the certificate.

[#11]

I will check with a test account and flag up to the business.

[#12]

---

@Townman wrote:

I will check with a test account and flag up to the business.

---

Out of curiosity, is there any follow up to this? I was out most of the morning, but by the time I got back, it was working normally again and seems to have been ok since then. Did PN know/find something was wrong? Did they fix something?

[#13]

I do not know.  I raised the observation but have received no update.