Bug 4328 - Event reply is sent by an unexpected account
Summary: Event reply is sent by an unexpected account
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Plugins/vCalendar (show other bugs)
Version: 3.17.4
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2020-04-01 12:57 UTC by Alexander Kurakin
Modified: 2020-05-08 00:16 UTC (History)
1 user (show)

See Also:


Attachments

Description Alexander Kurakin 2020-04-01 12:57:29 UTC
1. I have "EMAIL_ONE" and "EMAIL_TWO" email accounts in Claws.
2. I get calender-event-email addressed to "GROUP_EMAIL_THREE" group email. "EMAIL_TWO" is a part of "GROUP_EMAIL_THREE" group so I see this message **in "EMAIL_TWO"'s messages list**.
3. I click "Accept" message/event button.
4. Expected behavior: Claws sends a message via "EMAIL_TWO" account.
   Actual behavior: Claws sends a message via "EMAIL_ONE" account.
Comment 1 Alexander Kurakin 2020-04-22 13:57:26 UTC
Maybe, it uses default account to reply instead of current folder's...

Or, first of "To:" e-mails?
Comment 2 Paul 2020-04-22 14:13:16 UTC
It searches the accounts for an email address which matches an address from all those associated with the event, uses your default account if there is no match.
Comment 3 Alexander Kurakin 2020-04-22 14:44:58 UTC
Well, two thoughts.

1. Should message's folder's account have higher priority?

2. The original email message doesn't contain "EMAIL_ONE" at all in source.
    But I see "EMAIL_ONE (didn't reply on)" in GUI.
    Why?

(BTW, I don't see "EMAIL_TWO" in source, too. I didn't know it. But I got message at "EMAIL_TWO"'s Inbox.)
Comment 4 Paul 2020-04-22 14:48:38 UTC
> 1. Should message's folder's account have higher priority?

Do you mean that you have set a default account in the folder Properties?
Comment 5 Alexander Kurakin 2020-04-22 14:58:54 UTC
> > 1. Should message's folder's account have higher priority?

> Do you mean that you have set a default account in the folder Properties?

No.

* I'm replying on message inside "EMAIL_TWO"'s Inbox folder. (Message has come there.)
* Default account is "EMAIL_ONE".

I think, "EMAIL_TWO" should have priority in such situation.
Comment 6 Paul 2020-04-22 15:02:06 UTC
What sort of mailbox is that, MH or IMAP?
Comment 7 Alexander Kurakin 2020-04-22 15:04:00 UTC
> What sort of mailbox is that, MH or IMAP?

IMAP.
Comment 8 Paul 2020-04-22 15:09:09 UTC
Right-click the top-level mailbox folder, open 'Properties', go to the Compose page, check the 'Default account' button and select the appropriate account, check the 'Apply to subfolders' button, and click OK.

If the automatic-account-selection can't match anything, then the default account is used. Setting a default account for a folder overrides this.
Comment 9 Alexander Kurakin 2020-04-22 15:22:16 UTC
Thanks!

Which "Default account" value is default for a IMAP's folder?

I mean, is it
* set to undefined (so, it is equal to global default account),
* or set to IMAP folder's account?

I see that "first" but want to to clarify...
Comment 10 Alexander Kurakin 2020-04-23 16:01:26 UTC
And, please:

> 2. The original email message doesn't contain "EMAIL_ONE" at all in source.
>     But I see "EMAIL_ONE (didn't reply on)" in GUI.
>     Why?
Comment 11 Paul 2020-05-06 10:20:53 UTC
*** Bug 4340 has been marked as a duplicate of this bug. ***
Comment 12 Paul 2020-05-06 10:48:06 UTC
> Which "Default account" value is default for a IMAP's folder?

The "Default account" is indicated, and can be changed in 2 places:

* The account selected and displayed in the account selector in the lower right-hand corner of the main window.

* The account in bold text in /Configuration/Edit accounts, where you'll see a button, 'Set as default account'
Comment 13 Paul 2020-05-06 10:52:23 UTC
Apologies, a correction to comment #12:

The lower right-hand corner indicates the currently selected account, not the default account.
Comment 14 Alexander Kurakin 2020-05-06 11:46:42 UTC
Paul, thanks! Also, write please about comment #10 (the same is bug #4340).
Comment 15 Alexander Kurakin 2020-05-07 23:27:32 UTC
Paul, answer please comment #10 (bug #4340 is the same).
Thanks.

Note You need to log in before you can comment on or make changes to this bug.