Revision history [back]
 | 1 | initial version | posted 2014-07-23 23:19:30 +0200 |
[Bug?] draft Exchange email is sent via Jolla Default mail account instead of Exchange account?
It seem the exchange email (saved as draft) is not sent via exchange client.
Instead it is sent via mail account, which is set as default mail account in 'system => settings'
Imho the draft mail should sent out based on the mail account where the draft folder is.
The current implementation even changes the from: email address even the draft mail would be originally reply to ongoing email thread.
most likely to in-reply-to header is also renewed in this situation - didn't check though...
Is this caused by the Exchange protocol as my account is created before than latest 1.0.8.19 update?
[Bug?] draft Exchange email is sent via Jolla Default mail account instead of Exchange account?
It seem the exchange email (saved as draft) is not sent via exchange client.
Instead it is sent via mail account, which is set as default mail account in 'system => settings'
Imho the draft mail should sent out based on the mail account where the draft folder is.
The current implementation even changes the from: email address even the draft mail would be originally reply to ongoing email thread.
most likely to in-reply-to header is also renewed in this situation - didn't check though...
Is this caused by the Exchange protocol as my account is created before than latest 1.0.8.19 update?
| | 3 | No.3 Revision |
[Bug?] draft Exchange [Bug] Draft email is sent via Jolla Default default mail account instead of Exchange account?the account it was created on
It seem the exchange email (saved as draft) is not sent via exchange client.
Instead it is sent via mail account, which is set as default mail account in 'system => settings'
Imho the draft mail should sent out based on the mail account where the draft folder is.
The current implementation even changes the from: email address even the draft mail would be originally reply to ongoing email thread.
most likely to in-reply-to header is also renewed in this situation - didn't check though...
Is this caused by the Exchange protocol as my account is created before than latest 1.0.8.19 update?