-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In specific inboxes, wrong account selected for reply [$10 awarded] #10
Comments
cc @tahaalibra let’s continue here – we moved repositories. :) |
can you provide screenshot or something. are others experiencing it too because i am not able to reproduce |
@jancborchardt i am also not able to reproduce it :( |
@ChristophWurst or anyone @nextcloud/mail are you not able to reproduce this? I have this issue all the time. :( |
The code to determine the right account was already in place, but it used a global jQuery selector. Since the view has not been attached to the DOM at that point, the selector doesn't select anything and the line of code has no effect. Fixes #10 Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
I can reproduce it in the pre-0.7 release: Set up multiple email accounts, select the second one and write a reply to an email with people in CC, the from: address is the one from the first account. If there is no one in CC, its working fine! |
@plastikschnitzer could you please file an issue for that? I'll have a look tomorrow :) |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and questions. |
I have 2 accounts configured. The first one has one alias.
When I am in the single inbox of the second one, whenever I open an email which has people in CC, the wrong email (the second one) is selected in the »from« dropdown. It’s fine when the mail is just sent to me without CC.
cc @tahaalibra since this appeared with the introduction of aliases.
The $10 bounty on this issue has been claimed at Bountysource.
The text was updated successfully, but these errors were encountered: