Open Bug 563334 Opened 11 years ago Updated 4 months ago

Implement pref and UI to exclude account from "Get All New Messages" poll: Cannot disable checking of obsolete account

Categories

(Thunderbird :: Account Manager, defect)

defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: mikeudalluk, Unassigned)

References

(Depends on 1 open bug, )

Details

(Whiteboard: [workaround with Tb 3.1: server=0.0.0.0])

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2.4pre) Gecko/20100403 Ubuntu/9.10 (karmic) Namoroka/3.6.4pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.10pre) Gecko/20100403 Shredder/3.0.5pre

I have a couple of old accounts which contain messages that I want to keep for reference but can no longer be checked due to server restrictions.  I wish to disable new mail checking for these accounts and keep them solely as a store of messages for searching.  Every time I click "Get all new messages" I get several error pop-ups for these accounts.

Reproducible: Always

Steps to Reproduce:
1.  Create several accounts
2.  Disable every checking option in one of the account's settings
3.  Click "Get all new messages"
Actual Results:  
All accounts are checked including the old account and this generates pop-up errors.

Expected Results:  
Allow the absolute disabling of the checking of an account in the account's preferences.  Then never check that account when asked to check for all new mail.
Component: Account Manager → Preferences
QA Contact: account-manager → preferences
Mike,

Do you have an IMAP account or a POP 3 account?
I assume IMAP.

To check account type go to:
- Tools => Account Settings
- Choose "old account" kept for searching
- Server Settings
Look for Server Type

If you have a POP 3, message a downloaded to your computer.
I assume that even if you delete your account, mails are still on your local computer.
Becareful, I'm not 100% sure.
It needs to be confirmed by a more experienced developper.
Before doing any deletion back-up your profile:
http://support.mozillamessaging.com/fr/kb/Profiles#Backing_up_a_profile
or use http://mozbackup.jasnapaka.com/

If you have an IMAP account, it could be different.
I'm less familiar with IMAP account
Your mail could be deleted if you delete your account.
It depends on your setting in Tools => Account Settings => Synchronization & Storage.
The account in question is a POP 3 account but I did not intend to confine the bug to that.  Ideally, any account for which thunderbird has local storage should be able to be disabled and the messages kept.

If I delete the account, all of the folders will disappear and I lose the local storage (unless I move all of the messages into other folders).  I would like to avoid this in case I re-enable the account in the future.

Really I just need to disable checking for new mail for that account rather than delete the account.  Any further thoughts on how I could do this?
There is existing capability that You access from "Account Settings". From the accounts 'Server Settings' tab uncheck automatic server polling under 'Server Settings'. This deactivates get mail for that server with out effecting the local storage.

If the existing function is not what your asking for, please provide more information.  Otherwise I'm inclined to mark this as an invalid bug.
(In reply to comment #3)
> There is existing capability that You access from "Account Settings". From the
> accounts 'Server Settings' tab uncheck automatic server polling under 'Server
> Settings'.

This bug is about the manual clicking on the "Get All New Messages" item (in the drop-down menu of the "Get Mail" button).

"Get All New Messages" is not affected by the auto polling setting, nor arguably should it be.  There needs to be a separate option to include/exclude the account from the manual "Get All New Messages"
Workaroud-1.

As Tb's mail folder is set of <folder_name>, <folder_name>.msf, <folder_name>.sbd (directory to hold files/directory for subfolder), a POP3 account's mail directory(Server Settings, Local Directory:) can be changed to a folder of "Local Folders" account.
1. A POP3 account's Local Directory:   ...\Mail\abc.pqr.xyz
2. Move the directory to ...\Mail\Local Folders\abc.pqr.xyz
3. Change it to mail folder of Local Folders
   - Rename it to        ...\Mail\Local Folders\abc.pqr.xyz.sbd
   - Create null file of ...\Mail\Local Folders\abc.pqr.xyz
     (corresponding msf) ...\Mail\Local Folders\abc.pqr.xyz.msf)
4. Restart Tb.
   Folders of old POP3 account of hostname=abc.pqr.xyz are accessed
   as subfolders under folder named abc.pqr.xyz of "Local Folders".
   Local Folders
     abc.pqr.xyz
       Inbox
         sub1
           sub2
       Trash
       Sent
5. After that, the POP3 account can be deleted.
   As mail directory is not deleted by account deletion,
   manual deletion of ...\Mail\abc.pqr.xyz is required.
Note:
Above is applicable to old IMAP account too, if all mails is downloaded into offline-store(file of <folder_name>) before account is killed.

Workaround-2.

AFAIR, "Get All New Messages" doesn't try to connect to server which was not accessed yet after account creation. If it's right, "dummy POP3 account with Local Directory:old account's mail directory" can be a workaround of your problem.
However, "Work Offline" asks whether download or not even if dummy POP3 account, or tries to download for offline mode.
So, I recommend workaround-1 if your are familiar with directory/file manipulation, familiar with checking of settings using Config Editor, familiar with checking folder location via "Folder Properties".
If not, workaround-2 is better, because required operations are only (1) create dummy POP3 account, (2) Delete old account, (3) Change Local Directory: of the dummy account to directory used by old account, and (4) Restart Tb(mandatory).
A simpler workaround (for 3.1) is to set the server address to 0.0.0.0  This results in immediate (no packets) termination of the connection (0.0.0.0 is an invalid tcp destination address) when getting all, and 3.1 only shows a brief auto closing non modal alert (as opposed to a modal dialog requiring interaction in - Bug 123440)
Whiteboard: [workaround with Tb 3.1: server=.0.0.0]
Whiteboard: [workaround with Tb 3.1: server=.0.0.0] → [workaround with Tb 3.1: server=0.0.0.0]
Workaround-3.

1. Change server name to dummy server at Server Settings.
2. Sm 2 automatically removed entry from Password Manager.
   If Tb 2/3.0 doesn't remove it, remove manually.
Sm 2 reported no error by "Get All New Messages". After re-specifying of correct server name, Sm 2 asked password upon "Get New Messages" for the account.
Duplicate of this bug: 657281
Duplicate of this bug: 318310
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: x86 → All
Summary: Cannot disable checking of an obsolete account when "Get all new messages" is selected → Implement pref and UI to exclude account from "Get All New Messages" poll: Cannot disable checking of obsolete account
There is some progress on this in bug 281417.
Depends on: 281417
Version: unspecified → Trunk
Duplicate of this bug: 1118340
Duplicate of this bug: 1293488
Duplicate of this bug: 1293488
(In reply to al_9x from comment #6)
> A simpler workaround (for 3.1) is to set the server address to 0.0.0.0  This
> results in immediate (no packets) termination of the connection (0.0.0.0 is
> an invalid tcp destination address) when getting all, and 3.1 only shows a
> brief auto closing non modal alert (as opposed to a modal dialog requiring
> interaction in - Bug 123440)

This worked for me in Thunderbird 52.2.1.
After I set the server address to 0.0.0.0 , when I click on "Get messages for all accounts", I receive no pop-up error for this account. 
If I select this account in the account tree on the left, and then I click on "Get messages for the current account", only a little message in the lower bar is given (such as "connecting to 0.0.0.0), which is not very annoying...
Thanks.
See Also: → 464703
Component: Preferences → Account Manager
Duplicate of this bug: 604585
Duplicate of this bug: 636174
Duplicate of this bug: 1302095

https://mzl.la/2XGzu2X is a collection of issues

Some of the dupes to bug 689067 should perhaps be duped instead to this bug

You need to log in before you can comment on or make changes to this bug.