Thunderbird not recognizing password
I was having an issue sending email. I could receive OK. Troubleshooting was not going well so I deleted my account and tried simply setting it back up. When I set everything up it says incorrect user name or password. I have re-entered the username (email address) and password many times but it will not go through. If I enter the same user name and password in their web based (webmail) system it works fine. Since it works on the webmail server Bell is telling me it must be a Thunderbird error. Please help.
All Replies (9)
Did you sort it out?
What are your settings? According to Bell:
Incoming IMAP server: imap.bell.net on port 993, SSL/TLS, authentication = normal password, User name = email address.
Incoming POP server: pophm.sympatico.ca on port 995, SSL/TLS, authentication = normal password, User name = email address.
Outgoing SMTP server: smtphm.sympatico.ca on port 587, STARTTLS, authentication = normal password, User name = email address.
Disable email scanning by antivirus if it's turned on.
That worked but only half way. I was trying the IMAP settings and switched to POP. So now I can receive e-mails but still can't send. I will appreciate any tips but this particular email account is 98% incoming anyway. Any replies I will use my secondary account.
Bell instructions are a bit vague, and I don't think they support STARTTLS. Try this: in the smtp settings, change the security to SSL/TLS, which will autoswitch the port to 465, the usual port for SSL. Type in 587 for the port, so you have SSL/TLS on port 587. Does sending now work?
Well I think we are getting closer. It seems to connect to the server but it "times out". What is frustrating is that I am pretty sure no setting were changed that would explain why it stopped working in the first place.
Time-outs often result from antivirus scanning of outgoing mail. Did you disable that option? What is the AV program? Running in Windows safe mode is one way to test if AV is interfering.
A sudden change in performance could be caused by a mixup between a TB update and an AV update.
We are just Using the stock Windows Defender. I will try safe mode but that will have to wait until we close for the evening. Thanks for the help so far.
I haven't noticed that WD causes any problems with TB, but there could be another program interfering, e.g. a VPN if you have one.
The SUMO article for Bell suggests the same settings I first mentioned, i.e. smtphm.sympatico.ca on port 587, STARTTLS, but you can't be 100% confident the info provided by Bell is completely accurate. Bell support says they don't support TB, which translates to 'we don't really know how email works'.