Bug 1131065

Summary:	Tumbleweed: please add checkbox to allow temporary suspension of Thunderbird email account
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Eric Benton <erbenton>
Component:	Firefox	Assignee:	Mozilla Bugs <mozilla-bugs>
Status:	RESOLVED UPSTREAM	QA Contact:	E-mail List <qa-bugs>
Severity:	Enhancement
Priority:	P5 - None	CC:	Andreas.Stieger, pujos.michael
Version:	Current
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Eric Benton 2019-03-30 13:47:56 UTC

Like most people i have a number of email accounts setup in Thunderbird. Whats really needed is a simple setting like a checkbox on the Account Settings page that would suspend completely all sending and receiving for the account without losing the password, emails or other important data.
this should prevent the account from doing any internet activity like contacting the server EVEN if the "Get all Messages" menu-button is used. In all cases it should just skip over that account if the checkbox is checked to disable it. Unchecking the box would resume normal behavior with no further input required of the user. e.g don't come back and ask  for the password again because like with a lot of people its long forgotten
I have a bit wordy because googling around there are all sorts of wacky suggestions like inserting a space in the user login name or deleting the password, none of which are acceptable, nor do they work properly.

Comment 1 Michael Pujos 2019-04-02 17:46:52 UTC

This is not an openSUSE issue but a Thunderbird issue and new feature.
I agree this is annoying and I think it has been asked on the Mozilla bugtracker for years to no avail.

Still the simple workaround to append .invalid to the "Server Name" of the account you want to disable works:

imap.blargh.com => imap.blargh.com.invalid

Comment 2 Eric Benton 2019-04-02 19:14:41 UTC

Thanks. I'll see about filing this with mozilla

Comment 3 Andreas Stieger 2021-04-25 08:47:01 UTC

resolving as this is an upstream feature request

Comment 4 Eric Benton 2021-04-25 09:52:32 UTC

# unset EDITOR
# crontab -e
/bin/sh: line 1: /usr/bin/vi: No such file or directory
crontab: "/usr/bin/vi" exited with status 127
#

Comment 5 Eric Benton 2021-04-25 09:54:01 UTC

Dang, i just commented on the wrong bug, i wish i could delete the comment but...