View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005117||SOGo||Web Mail||public||2020-08-03 13:09||2020-08-03 22:49|
|Fixed in Version||5.0.0|
|Summary||0005117: no identity selected when replying to a mail with self in bcc|
sogo 184.108.40.20600803-1 doesn't select a identity when a mail with multiple reciepients is received but the own mail address is only in the bcc.
|Steps To Reproduce|
login with sogo1 to demo.sogo.nu
new mail ->
to: sogo2@... sogo3@...
click on refresh mails
open mail + reply all
-> no identity selected
|Tags||No tags attached.|
Really glad to see confirmation this issue from someone else.
i didn't see the issue when using reply, only when using reply all.
instead of "Choose which identity to send this message from" always the default identity should be auto selected.
via bcc its just easy to reproduce, i guess it could happen with shared mailboxes, too.
When the user's email is not found in any of the to/cc headers, the favorite identity is chosen, which could be undefined if no identity is marked as favorite (heart icon from the identity manager).
Notice that SOGo doesn't know which user's address was used when the user was in bcc.
sadly this doesn't work: can be reproduced on demo.sogo.nu with one identity marked as favorite, too. it doesn't matter if one or multiple identities exists or if a favorite is selected or not.
IMHO still it should select the favorite: but it currently doesn't.
I use demo.sogo.nu.
abama: "i didn't see the issue when using reply, only when using reply all."
|2020-08-03 13:09||abma||New Issue|
|2020-08-03 13:24||wimmer||Note Added: 0014615|
|2020-08-03 13:31||abma||Note Added: 0014616|
|2020-08-03 14:33||francis||Note Added: 0014617|
|2020-08-03 14:38||abma||Note Added: 0014618|
|2020-08-03 14:56||wimmer||Note Added: 0014619|
|2020-08-03 15:09||wimmer||Note Added: 0014620|
|2020-08-03 22:49||francis||Changeset attached||=> sogo master d930821d|
|2020-08-03 22:49||francis||Assigned To||=> francis|
|2020-08-03 22:49||francis||Resolution||open => fixed|
|2020-08-03 22:49||francis||Status||new => resolved|
|2020-08-03 22:49||francis||Fixed in Version||=> 5.0.0|