Bug 312619 Comment 19 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(Hidden by Administrator)
This is definitely a problem (missing ability) with TB. I do not want to delete certain accounts in TB or attempt to connect to particular mailboxes for a few reasons that I have found:

1) During testing of website/email setups for clients
2) Site hosting transfer and my or my client's emails
3) While I try/test different configurations
4) Checking other people's emails on occasions (e.g. colleagues/groups/vacations)
5) Reducing cPanel process tasks for little needed accounts (IMAP connections don't stop on my shared server even without IDLE)

And all the reasons others have stated.

This IS the same as bug 689067.

There needs to be a specific IMAP option to deactivate on a per account basis. Simply going off-line for an account would not be something I'd trust probably due to the way I've seen TB go onff-line on it's own and the complications it would/might bring making accounts on-line again.   

Due to the lack of the ability to deactivate an account I have a couple of times managed to lock myself out of my entire hosting server (thanks to their keen and useful firewall!) due to one account repeatedly using the wrong credentials in just a short space of time. My IP was completely blocked from accessing any email accounts or websites.

It's so obvious that this is needed and yet it's been missing for years despite the definite need.

It's no good saying to just set it to never check, or not to click on it, particularly when in unified view it automatically tries to connect and even though as a workaround I have changed the mail server etc. to xxx.yyy.zzz to avoid the firewall lock outs, TB still throws up a "can't connect" error message whenever I click on Unified or the particular account in normal view when checking contents of any of its folders.

Long overdue, really annoying for several reasons, and I can't find a fix or workaround.

Back to Bug 312619 Comment 19