Closed
Bug 317167
Opened 20 years ago
Closed 20 years ago
Reply and Reply-all on messages sent "From: myself" should consider all account identities when setting To field
Categories
(MailNews Core :: Composition, enhancement)
MailNews Core
Composition
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mkmelin, Assigned: mkmelin)
References
Details
(Keywords: fixed1.8.1)
Attachments
(2 files, 1 obsolete file)
|
4.31 KB,
patch
|
Bienvenu
:
review+
|
Details | Diff | Splinter Review |
|
5.54 KB,
patch
|
mscott
:
approval-branch-1.8.1+
|
Details | Diff | Splinter Review |
See bug 85296 comment 19.
Reply and Reply-all on messages sent "From: myself" should consider all account identities when setting To field.
| Assignee | ||
Comment 1•20 years ago
|
||
also cleans up a warning an some extra whitespace
Assignee: nobody → mkmelin+bugzilla
Status: NEW → ASSIGNED
Attachment #203731 -
Flags: review?(bienvenu)
Comment 2•20 years ago
|
||
Comment on attachment 203731 [details] [diff] [review]
proposed fix
this seems to me to cast too wide a net of identities - it uses all the identities on all the servers that use the current identity. I think the following approach might be more precise:
See what account the message came in from. If we find that, just check the identities for that account (that only works for pop3 messages, I believe). If we can't find the account, check the server of the folder the message is in, and use the identities for that server (which in general is the imap case)
What do you think? My suggestion would miss the case where an imap message is moved to an other account, but yours might too, but mine would avoid more false positives.
Here's some pseudo code, w/o error checking:
msgHdr->GetAccountKey(getter_Copies(accountKey));
if (!accountKey.IsEmpty())
{
am->GetAccount(accountKey, getter_AddRefs(account));
account->GetIdentities(getter_AddRefs(identities));
}
else
{
msgHdr->GetFolder(getter_AddRefs(folder));
folder->GetServer(getter_AddRefs(server));
am->GetIdentitiesForServer(server, getter_AddRefs(identities));
}
Attachment #203731 -
Flags: review?(bienvenu) → review-
Comment 3•20 years ago
|
||
I would like to request that there is at least an option to do this for all available identities.
Background: as a workaround for bug 166293, I have two different accounts for the same IMAP server, so messages I am replying to may "randomly" belong to a different account.
| Assignee | ||
Comment 4•20 years ago
|
||
This patch addresses the review comments, I hope. It also introduces a boolean pref "mailnews.reply_to_self_check_all". When set to true, all available identities are considered.
Attachment #203731 -
Attachment is obsolete: true
Attachment #205548 -
Flags: review?(bienvenu)
Comment 5•20 years ago
|
||
Comment on attachment 205548 [details] [diff] [review]
proposed fix, v2
this looks good - I'll try running with it when I'm back from vacation on Wednesday, and if it works ok, I'll check it in. One thing we should add is a default value for the new pref in mailnews.js...
Attachment #205548 -
Flags: review?(bienvenu) → review+
Comment 6•20 years ago
|
||
I fixed the braces style, and changed the name of the pref slightly, and added it to mailnews.js
Comment 7•20 years ago
|
||
fix checked in, thx!
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 8•20 years ago
|
||
Comment on attachment 206309 [details] [diff] [review]
fix as checked in.
Sister bug 85296 is on the branch, time for this one too?
Attachment #206309 -
Flags: approval-branch-1.8.1?
Comment 9•20 years ago
|
||
*** Bug 209329 has been marked as a duplicate of this bug. ***
Comment 10•20 years ago
|
||
Comment on attachment 206309 [details] [diff] [review]
fix as checked in.
yup, time for this one too.
Attachment #206309 -
Flags: approval-branch-1.8.1? → approval-branch-1.8.1+
| Assignee | ||
Updated•20 years ago
|
Whiteboard: [checkin needed (1.8 branch)]
Updated•20 years ago
|
Keywords: fixed1.8.1
Whiteboard: [checkin needed (1.8 branch)]
Updated•18 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•