Sorry - we're unable to communicate with our sign-up server.
I'm attempting a new install of the latest version of Thunderbird on Windows 7 booted in safe mode with networking. All networking functions check out perfectly, however, when attempting to configure an email account Thunderbird errors out with "Sorry - we're unable to communicate with our sign-up server.". There is no virus protection running. What's the best troubleshooting next step?
Chosen solution
PROBLEM SOLVED
OK here's the final solution. It was an initial config error that caused follow-on problems. Here's the sequence.
1- A scratch install of Thunderbird left me with the wrong proxy settings ( "No proxy" was not set). This was the caused of the "unable to communicate with sign-in server" problem. **BUT** I did not identify that root cause at that time. You should understand that the sign-in server process does an automatic fetch and load of the correct cofig for the account you specify. This means that no auto-fetch was done.
2- Instead of the auto-fetch, I configured manually. I did know all the parameters since I was familiar with another Thunderbird install that was configured for IEEE mail service using IMAP. Once I laid in what I knew to be a correct config, I still had problems, so I went back to researching.
3- Upon researching and reading I went back to check proxy settings and found "No proxy" was NOT set. So I set it.
4- This showed some progress. Now I was able to establish credentials, and talk to the server, but for unknown reasons I was getting the "unknown command" messages and my inbox would not populate.
5 - Now, in desperation, and with "No proxy" properly set, I deleted the account and re-created it. This time I did not get the "unable to communicate with sign-in server" problem, so the auto-fetch and config **DID** occur.
This magically cured the "unknown command" issue which is still something of a mystery since the config appears to be identical, but hey .... it's working so I'm happy.
Read this answer in context 👍 0All Replies (14)
Yesterday or the day before there was someone on the forum with almost exactly the same issue. Their fix was to disable copmodo firewall as it was messing up.
There is no firewall or anti-virus software running, and I'm in safe mode with networking.
But thanks for the suggestion. Any other ideas?
Is there any error log I can inspect?
I have continued to work on this and while I did not find a fix, I did find a way around it. I manually configured the account with server names, port numbers, and both security and authentication protocols. I now seem to be able to get Thunderbird to talk to the server, and at first I thought I was home free, but now I am getting the obscure message:
The current operation on 'inbox' did not succeed. The mail server for account jmoses@ieee.org responded: Unknown command at [long string of mixed numbers and characters]
Any suggestion you might have as to what is going on would be *REALLY* appreciated.
Correction ... strike the word "at" . The actual message is:
The current operation on 'Inbox' did not succeed. The mail server for account jmoses@ieee.org responded: Unknown command rm8mb84709573oeb
As you use a Windows OS then the built in Windows Firewall should be working in Safe Mode with Networking.
Can you confirm that it is not running or access it and ensure Thunderbird is allowed?
Confirm you have accessed the webmail account using a browser and selected either POP or IMAP forwarding? Some servers have them auto enabled and others need you to select which option you wish to use. Which option did you select or confirm which option is auto selected?
When you click on get messages, what does it say in the bottom Status Bar...looking up, connecting, connected etc ? Does it ever get to the 'connected' ?
Please post this info: In thunderbird Help > Troubleshooting Information click on 'Copy text to clipboard' In this forum question, right click in a 'Post a Reply' text box and select: 'Paste' You can edit/remove all info on fonts and printers but nothing else.
The "unable to communicate with our set-up server" issue was resolved by adjustment of proxy settings. For some reason Thunderbird did not install with "no proxy" as the default. I set it to "no proxy" and the problem resolved.
I am still working on the problem that came next:
The current operation on 'Inbox' did not succeed. The mail server for account jmoses@ieee.org responded: Unknown command rm8mb84709573oeb
I am unfamiliar with the whole concept of a "sign in server" Have you ever seen such an error in Thunderbird @Toad?
You could log the connection, See https://wiki.mozilla.org/MailNews:Logging
Chosen Solution
PROBLEM SOLVED
OK here's the final solution. It was an initial config error that caused follow-on problems. Here's the sequence.
1- A scratch install of Thunderbird left me with the wrong proxy settings ( "No proxy" was not set). This was the caused of the "unable to communicate with sign-in server" problem. **BUT** I did not identify that root cause at that time. You should understand that the sign-in server process does an automatic fetch and load of the correct cofig for the account you specify. This means that no auto-fetch was done.
2- Instead of the auto-fetch, I configured manually. I did know all the parameters since I was familiar with another Thunderbird install that was configured for IEEE mail service using IMAP. Once I laid in what I knew to be a correct config, I still had problems, so I went back to researching.
3- Upon researching and reading I went back to check proxy settings and found "No proxy" was NOT set. So I set it.
4- This showed some progress. Now I was able to establish credentials, and talk to the server, but for unknown reasons I was getting the "unknown command" messages and my inbox would not populate.
5 - Now, in desperation, and with "No proxy" properly set, I deleted the account and re-created it. This time I did not get the "unable to communicate with sign-in server" problem, so the auto-fetch and config **DID** occur.
This magically cured the "unknown command" issue which is still something of a mystery since the config appears to be identical, but hey .... it's working so I'm happy.
Modified by carswellb58
Many thanks for posting a complete feedback on your fndings. This may assist others with similar situation. There is always something to learn and spreading the knowledge of such findings is extremely helpful. Could you mark your last comment as 'Chosen Solution'.
I inadvertently marked the wrong response as the "Chosen Solution" but I'm not seeing how to correct that. Am I missing something obvious?
carswellb58 said
I inadvertently marked the wrong response as the "Chosen Solution" but I'm not seeing how to correct that. Am I missing something obvious?
Nothing a moderator can not fix.