Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Caută ajutor

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.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Unable to move a message to "Sent"

  • 1 răspuns
  • 1 are această problemă
  • 2 vizualizări
  • Ultimul răspuns de 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

Soluție aleasă

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

Citește acest răspuns în context 👍 0

Toate răspunsurile (1)

more options

Soluție aleasă

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