CalDAV:calendar-user-address-set ignored, when composing new meetings
I setup a new Collection (IMAP, CalDAV) account for user ccc@example.org . This user has as calendar-user-address only mailto:yyy@example.org . The meeting editor, once I select a calendar for the ccc-account, does not allow me to choose as organizer yyy@example.org, but ccc@example.org. It shows also the other mail aliases I have for IMAP accounts. Those aliases are in fact always selectable as organizer. Only the primary-account-email address can be selected after the calendar is selected.
I add yyy@example.org as alias to the mail account ccc@example.org . I start a new meeting. As organizer I cannot select yyy@example.org . I see as options the aliases I have set in the other (first) email account.
I delete the alias yyy@example.org as alias in the ccc@example.org account and add it as alias in my other/first/primary email account.
In the newly opened meeting composer, I select first yyy@example.org as organizer, as it is on the left on the window. Then I select a calendar of the ccc@example.org user. Evolution changes the organizer to ccc@example.org .
When I create a meeting with organizer ccc@example.org and PUT it over CalDAV, evolution does not offer to send iMIP mails. Neither the server nor Evolution send invitations, as yyy@example.org is not in the <calendar-user-address>
.
-
When Evolution creates meetings and the organizer is not in the calendar-user-address set for the CalDAV-account, evolution shall either ask the user to send invitations, to offer the user to change the organizer, or take confirmation to upload a meeting, for which neither CUA nor server will send invitations.
-
Evolution shall not set as organizer ccc@example.org, as this address is not the calendar-user-address-set and therefore does not do server side scheduling. Since yyy@example.org is the single email in the calendar-user-address-set, Evolution shall set this address as organizer.