We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Can not send emails from Thunderbird 38.6, but can in 38.2.

  • 12 replies
  • 2 have this problem
  • 1 view
  • Last reply by christ1

more options

I used to be able to send email from Thunderbird 38.2, but not in 38.6. My ISP tested the two versions and found that your new 38.6 release doesn't use my complete username to access my ISP account (ex. [email protected] vs. username). Was there a change in this field after 38.2? Is this a known issue with a known fix?

I used to be able to send email from Thunderbird 38.2, but not in 38.6. My ISP tested the two versions and found that your new 38.6 release doesn't use my complete username to access my ISP account (ex. [email protected] vs. username). Was there a change in this field after 38.2? Is this a known issue with a known fix?

Chosen solution

I'd really be curious how your ISP concluded the problem is caused by the wrong user ID format. In any case, when your problem is fixed, can you mark the thread as 'Solved' please? Thank you.

Read this answer in context 👍 0

All Replies (12)

more options

How did they determine that? Did they try with the same profile?

more options

Correct - they used my same profile against each version.

more options

Then I don't see how two versions could behave differently wrt the user ID. What exactly is the problem with 38.6.0? Do you get any error message? Is a personal firewall or security software blocking Thunderbird (e.g. like Norton)?

more options

Assuming there were not changes on the Thunderbird side, I agree. All previous upgrades were seamless.

I receive the following error message:

Sending of the message failed. The message could not be sent because the connection to Outgoing server (SMTP) smtp.onebox.com timed out. Try again.

Are there any configurations I should be concerned about?

more options

Is your complete username in the field for your SMTP settings?

more options
more options

Q: Is your complete username in the field for your SMTP settings? A: I don't see a place to enter a username for the "Outgoing Server (SMTP)" window, I only see that in the "Server Settings" window. If you meant the "Server Settings" window, I have the User Name field filled with the username I use when I directly log into my Onebox.com account (ex. [email protected]).

Q: Is a personal firewall or security software blocking Thunderbird (e.g. like Norton)? A: I changed from McAfee to Bitdefender about one year ago and was able to send emails afterwards. If there is a setting within Bitdefender I should be checking to confirm if it is blocking me from sending email, pleeease let me know (I haven't changed any settings since the initial install that wasn't posing any problems sending emails through Thunderbird).

more options

Right click the account on the left side in the Folder Pane. Select Settings Go to the bottom of that list to Outgoing Server (SMTP) That is where you edit smot server settings.

more options

My "Outgoing Server (SMTP)" has a single identity, with the following settings:

Server Name: smtp.onebox.com Port: 587 User Name: [email protected] Authentication method: No authentication Connection Security: None

more options

Port 587 usually uses connection security of STARTTLS and requires a password.

You might double check the SMTP settings that your provider uses.

more options

Airmail -

After thinking about your comment regarding the Port #, I recalled that at one point I was using Microsoft Outlook. I checked the configs there and determined that my port was incorrect! I changed the port and I'm up and operating again! Thanks sooo much! I'm not sure why Onebox so poorly misdirected me.

Thanks again!

more options

Chosen Solution

I'd really be curious how your ISP concluded the problem is caused by the wrong user ID format. In any case, when your problem is fixed, can you mark the thread as 'Solved' please? Thank you.