This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Unable to move a message to "Sent"

  • 1 reply
  • 1 has this problem
  • 1 view
  • Last reply by marmistrz

marmistrz
marmistrz
more options

After launching Thunderbird (and fetching the latest messages) I replied to an e-mail. The e-mail was successfully sent, even the Gmail web interface has it in its "Sent" folder. Nevertheless, Thunderbird has a blinking progress bar and is still trying to move the message to the "Sent" folder. I set maximum server connection to cache to 1, but to no avail.

My sent messages folder is in fact "Wysłane", not "Sent", I used the English counterpart for the sake of simplicity.

I'm using Linux Mint 17.1, Thunderbird 1:31.6.0+build1-0ubuntu0.14.04.1, architecture amd64

After launching Thunderbird (and fetching the latest messages) I replied to an e-mail. The e-mail was successfully sent, even the Gmail web interface has it in its "Sent" folder. Nevertheless, Thunderbird has a blinking progress bar and is still trying to move the message to the "Sent" folder. I set maximum server connection to cache to 1, but to no avail. My sent messages folder is in fact "Wysłane", not "Sent", I used the English counterpart for the sake of simplicity. I'm using Linux Mint 17.1, Thunderbird 1:31.6.0+build1-0ubuntu0.14.04.1, architecture amd64

Chosen solution

Changing the server from `*.googlemail.com` to `*.gmail.com` solved the issue

Read this answer in context 👍 0

All Replies (1)

marmistrz
marmistrz Question owner
more options

Chosen Solution

Changing the server from `*.googlemail.com` to `*.gmail.com` solved the issue