Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

V60.3.0 cannot delete emails or empty trash. Trash and trash.msf have been deleted.

  • 2 ответа
  • 1 имеет эту проблему
  • 17 просмотров
  • Последний ответ от w4wyi

more options

11/8/18 had a forced update of Thunderbird to v60.3.0 (32 bit, Win10). Now I cannot delete any email messages or empty the trash folder. I have deleted trash and trash.msf files but still have the problem. Error message is "The current operation on 'Inbox' (or 'Trash') did not succeed. The email seriver for account ... responded: [SERVERBUG] Internal error occured. How do I fix this? How can I go back to the previous version that worked correctly?

11/8/18 had a forced update of Thunderbird to v60.3.0 (32 bit, Win10). Now I cannot delete any email messages or empty the trash folder. I have deleted trash and trash.msf files but still have the problem. Error message is "The current operation on 'Inbox' (or 'Trash') did not succeed. The email seriver for account ... responded: [SERVERBUG] Internal error occured. How do I fix this? How can I go back to the previous version that worked correctly?

Выбранное решение

Subscribe to see the server Trash folder. Right click on imap mail account and select 'Subscribe' Click on 'Refresh' button select/highlight trash and click on 'Subscribe' click on 'OK'

Прочитайте этот ответ в контексте 👍 0

Все ответы (2)

more options

Выбранное решение

Subscribe to see the server Trash folder. Right click on imap mail account and select 'Subscribe' Click on 'Refresh' button select/highlight trash and click on 'Subscribe' click on 'OK'

more options

Thank you very much. The problem was a coincidence to the 60.3.0 upgrade. The REAL problem that happened at the same time was with Comcast/Xfinity email servers. I was actually able to get a Comcast agent that was familiar with the problem. It took a few hours but the server problem was resolved.

I appreciate your help.