Closed Bug 139483 Opened 23 years ago Closed 15 years ago

Option for disabling contact in list

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, enhancement)

x86
Windows 2000
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: jeremy.m, Unassigned)

Details

I have alot of mailing lists containing overlapping lists of contacts. It would be a godsend if I could temporarilly disable a contact for all mailing lists. e.g. Alice goes on holiday and I don't want to flood her mailbox with status reports for that period. So I just open her contact mark the "temporarilly disable" checkbox and when she gets back to the office I uncheck the box. In the meantime she won't recieve mail sent to any of the lists she belongs too. when she gets back from vacation, I just uncheck the box and shes back on all the lists. Displaying her contact information grayed out when shown as part of a list would also be nice
No dups -> New
Status: UNCONFIRMED → NEW
Ever confirmed: true
mass re-assign.
Assignee: racham → sspitzer
Summary: RFE: Disabling contact in List → Option for disabling contact in list
Product: Browser → Seamonkey
Assignee: sspitzer → mail
QA Contact: nbaca → addressbook
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.