Last Comment Bug 151789 - Filter based on addresses of a nickname in addressbook
: Filter based on addresses of a nickname in addressbook
Status: NEW
:
Product: MailNews Core
Classification: Components
Component: Filters (show other bugs)
: Trunk
: All All
: -- enhancement (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2002-06-14 05:22 PDT by Johan Sundström
Modified: 2008-07-31 04:30 PDT (History)
0 users
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---


Attachments

Description Johan Sundström 2002-06-14 05:22:12 PDT
It would be nice if filters could identify senders by their nick in the
address book. I'd like to be able to construct a filter which refers to
all mail addresses listed in an address book entry, but by listing just
a unique key for the entry instead of copying those addresses by hand.
A hypothetical example of how such a filter could look in the UI:

For incoming messages that:
                            (*) Match any of the following:
(Sender) (is address book nick)   [traal                  ]
(Sender) (is address book person) [Jenny Dalenius         ]
Perform this action:
(Move to folder) (Friends on Lysator)

This example would match any incoming mail whose sender is any of the
mail addresses listed in my personal address book for the entries whose
Nick field is "traal", or whose Display name is "Jenny Dalenius".

This suggestion could be considered related to the bugs 65135, 34340,
34342 and 62687.
Comment 1 (not reading, please use seth@sspitzer.org instead) 2003-05-08 11:00:55 PDT
mass re-assign.
Comment 2 (not reading, please use seth@sspitzer.org instead) 2007-06-21 14:58:13 PDT
sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.
Comment 3 Serge Gautherie (:sgautherie) 2008-06-20 10:43:10 PDT
Filter on "Nobody_NScomTLD_20080620"

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