When replying to an email in a conversation, the system resets the current email account to the default, and not retaining the email being used in the conversation.
Example:
You have multiple accounts: xxx@xxx.com and yyy@yyy.com
- email 1
From: yyy@yyy.com
To:anyone@anything.com
....
- email 2
From:anyone@anything.com
To: yyy@yyy.com
- email 3 - by pressing replying button:
From: xxx@xxx.com
To:anyone@anything.com
When a reply is made with multiple accounts, there should be a way to retain the one email - i.e. - If I have a started a conversation with a client on my business email, and another conversation with a friend on a personal email account, then when I reply to the business client it should not use my default account (yes, I know that is what "default" technically means, but this is not how it *should* work).
Thanks
From: Changes on Reply with Multiple Accounts
-
- Posts: 2
- Joined: June 3rd, 2014, 4:27 pm
From: Changes on Reply with Multiple Accounts
Last edited by andykw on June 5th, 2014, 9:08 am, edited 1 time in total.
- therube
- Posts: 21698
- Joined: March 10th, 2004, 9:59 pm
- Location: Maryland USA
Re: From changes on Reply
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
-
- Posts: 2
- Joined: June 3rd, 2014, 4:27 pm
Re: From changes on Reply
Wow - closer to this one:
https://bugzilla.mozilla.org/show_bug.cgi?id=327713#c53
*** 8 year old bug!!! ***
This should get fixed - it is very frustrating, and with today's users integrating more work and personal items, it is glaringly bad that SeaMonkey Mail hasn't corrected this issue yet.
https://bugzilla.mozilla.org/show_bug.cgi?id=327713#c53
*** 8 year old bug!!! ***
This should get fixed - it is very frustrating, and with today's users integrating more work and personal items, it is glaringly bad that SeaMonkey Mail hasn't corrected this issue yet.