104026 - [RFE] Select identity (From address) automatically based on folder or receipient

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Account Configuration, enhancement)

Description

[Joakim Recht]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5+) Gecko/20011009
BuildID:    2001100908

A nice feature would be if the From field could be set on a folder or/and
receipient basis, so that when you reply to a message in some folder, a specific
From address is chosen. Likewise, this match could be on the To or CC fields of
the message. This way you wouldn't have to set it manually, which is easy to
forget, and as some mailing lists only accept mails from a specific mail
address, this could help a lot.

One place this could be set is under the Properties for a folder.

Reproducible: Always
Steps to Reproduce:
1. Reply to mail
2. Select sender (From)


Actual Results:  From must be set manually

Expected Results:  From should be set automatically

Comment 1

[Ninoschka Baca]

Adding jglick to Cc: list because this is an interesting idea.

Comment 2

[Stephen Edmonds]

Either I am missing something or the current mozilla does not support multiple
identities per mail account.  I see this being essential to this feature (which
would be really good)

I found a page (can't recall where now) that talked about how multiple identies
per mail account could be stored in the config file.  Trying to do this manually
didn't work...

Comment 3

[Jo Hermans]

that's bug 44863 ...

Comment 4

[(not reading, please use [e-mail] instead)]

mass re-assign.

Comment 5

[Jungshik Shin]

To make it more generic, we may introduce what's called 'role' in Pine
(http://www.washington.edu). 'From:' address is set according to various
conditions including recipient and folder.

Comment 6

[Joel Thornton]

This is a great idea. The web-based email service http://www.fastmail.fm
has this feature as well (labeled "personalities"). You can set a specific
personality on a per-folder basis, and when you compose or reply from a
certain folder, it sets your from-address, save-to folder
and message signature corresponding to the assigned personality.

I would use this feature liberally, as I collect mail from my various inboxes
into a single IMAP store, and would like to use the proper From address
depending on which folder I'm reading/replying from.

As for from-address-per-recipient, I don't think this would be a 
straightforward implementation, since the folder-defined role and the per-from-
address role would conflict when different. Instead, I would suggest making 
roles per-folder only, and then setting the From: address of replies match the 
To: address in the replied-to message.


If it isn't already, should 'roles' get an enh bug on its own? This bug seems 
to address the per-folder/per-recipient aspect more than the 'roles' aspect 
specifically.

Also, it seems the "identities" (currently bound 1-to-1 with email accounts) 
should be abstracted from the email accounts themselves -- instead assigning a 
preferred identity on a per-email-account and a per-folder basis.

Comment 7

[Robert Kaiser]

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

Comment 8

[Robert Kaiser]

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