Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

My "When I delete a message" folder setting breaks each time I update TB

  • 1 resposta
  • 1 tem este problema
  • 2 visualizações
  • Última resposta por topshot

more options

Because I want to keep some "trash" around longer to get around Gmail's 30-day limit, I created a folder under my account and changed the "When I delete a message" setting to move it to that folder. Seems simple enough and it works exactly like I want.

However, BOTH times TB has updated since I made this change in Aug, it breaks this setting so that those messages I wished moved to that folder are apparently permanently deleted instead as I cannot locate them in any mailbox or on web-based Gmail.

To fix it, I have to select one of the other options and then re-select the move option. I'm not certain if I did it the first time, but this time I closed TB after selecting the other option and then re-selected move after starting TB again.

As a software developer, I consider this a bug rather than a "feature". It clearly should not be doing this.

Because I want to keep some "trash" around longer to get around Gmail's 30-day limit, I created a folder under my account and changed the "When I delete a message" setting to move it to that folder. Seems simple enough and it works exactly like I want. However, BOTH times TB has updated since I made this change in Aug, it breaks this setting so that those messages I wished moved to that folder are apparently permanently deleted instead as I cannot locate them in any mailbox or on web-based Gmail. To fix it, I have to select one of the other options and then re-select the move option. I'm not certain if I did it the first time, but this time I closed TB after selecting the other option and then re-selected move after starting TB again. As a software developer, I consider this a bug rather than a "feature". It clearly should not be doing this.

Todas as respostas (1)

more options

Apparently this has been a known bug for EIGHT YEARS! https://bugzilla.mozilla.org/show_bug.cgi?id=533140

Apparently just restarting the program will cause it to happen as well so it wasn't related to the update itself, just the restart of TB.

scud42's message of 2017-06-12 seems the simplest workaround since I always use either Delete or Shift-Delete to decide which type of delete action I want.