233206 - List of "Safe" filters for outgoing mail addresses

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Account Configuration, enhancement)

Description

[Alastair]

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

I have two mail accounts, one is based around my home ISP's mail server, the
other is at my office (and I access it over VPN).

My worry is that because I have a large address book, when I type e-mail
addresses in the "To:", "CC:" or "BCC:" fields using the auto-complete system
that one day I am eventually going to send company-confidential documents to an
external address accidentally.

Therefore, I think it would be a really useful feature if, associated with each
individual mail account, we could enter a set of filters that define a "safe
list" of addresses.

Example: If I worked for company ABC, with domains ABC.com and ABC.co.uk, and
that company had its own mail server, I might like to add the following filter
rules for the safe list of the account:

*@abc.com
*@abc.co.uk

If I then tried to send an e-mail to [e-mail] via this account, Mozilla
mail would pop up a confirmation box when I hit send informing me that one or
more of the e-mail addresses did not match the safe list for the account and do
I want to proceed.

By default, when no filter rules were in the safe list, Mozilla Mail would just
assume the filter to be "*".

Natural extensions to this:

* An "unsafe" filter, or perhaps defining a "How safe is this rule" value for
each individual filter entry, with varying degrees of feedback from Mozilla Mail
ranging from no warning to prohibiting the send.

* The ability to mark particular contacts with a similar "Safety ranking" for
any given account that would by default over-ride the filter list itself.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.