0005348: Invitation send to alias address cannot be accepted nor added to calendar - SOGo | BTS

ID	Project	Category	View Status	Date Submitted	Last Update
0005348	SOGo	Web Mail	public	2021-07-01 12:26	2021-09-02 13:12

Reporter	bahnkonzept	Assigned To	francis
Priority	normal	Severity	major	Reproducibility	always
Status	resolved	Resolution	fixed
Product Version	5.0.1
Fixed in Version	5.3.0

Summary	0005348: Invitation send to alias address cannot be accepted nor added to calendar
Description	If an invitation is send to alias@example.com which redirects to the SoGO user user1@example.com, then user1@example.com is not able to accept this invitation nor is there any possibility to add the invitation to the calendar.
Steps To Reproduce	user1@example.com as SoGO user with an alias address alias@example.com external user sends invitation to alias address alias@example.com SoGO user1@example.com tries to accept or add the invitation to his calendar
Additional Information	.
Tags	appointment, calendar, invite

bahnkonzept 2021-07-01 12:26 reporter	CleanShot 2021-07-01 at 13.41.57@2x.png (96,402 bytes) CleanShot 2021-07-01 at 13.41.57@2x.png (96,402 bytes)

bahnkonzept 2021-07-01 14:45 reporter ~0015347	Addenum: We would like to have an option to import and (possibly) accept invitations that have reached the recipient via an alias address or similar. Thank you very much. Or is there still an option to configure this behaviour?

francis 2021-07-06 12:21 administrator ~0015352	SOGo must known the mail aliases of the users. Make sure your user source fetches the mail aliases. You will likely need to define `MailFieldNames` (see documentation).

bahnkonzept 2021-07-09 12:29 reporter ~0015356	Actually the main use case for us are invitations sent to mailing lists which some of our users are subscribed to. In this case, it is not possible to add them to SOGos source of mail aliases. In this case, SOGo should at least provide the option to add the event to the calendar (accept / decline / ... buttons aren't necessary). Maybe this should be the case for any .ics attachment like in most other mail tools too?

mat1010 2021-08-29 18:25 reporter ~0015427	We have basically the same issue. Using `MailFieldNames` does not work for SQL based user source except with kind of hacking around it / using non common SQL techniques, or am I wrong? We would have to build something like a pivot SQL table to have a column for each mail address of a user, right? \| mailfield1 \| mailfield2 \| mailfield3 \| \| test1@acme.com \| test1@acme.org \| test1@acme.net \|

francis 2021-09-02 13:12 administrator ~0015433	Ref: https://github.com/inverse-inc/sogo/commit/56f9e3e398f3baae31674e52d3a51da1dd3a0fd1

Date Modified	Username	Field	Change
2021-07-01 12:26	bahnkonzept	New Issue
2021-07-01 12:26	bahnkonzept	Tag Attached: appointment
2021-07-01 12:26	bahnkonzept	Tag Attached: calendar
2021-07-01 12:26	bahnkonzept	Tag Attached: invite
2021-07-01 12:26	bahnkonzept	File Added: CleanShot 2021-07-01 at 13.41.57@2x.png
2021-07-01 14:45	bahnkonzept	Note Added: 0015347
2021-07-06 12:21	francis	Note Added: 0015352
2021-07-09 12:29	bahnkonzept	Note Added: 0015356
2021-07-21 09:15	ofd2	Issue cloned: 0005361
2021-07-21 09:15	ofd2	Relationship added	has duplicate 0005361
2021-08-29 18:25	mat1010	Note Added: 0015427
2021-09-02 13:12	francis	Assigned To	=> francis
2021-09-02 13:12	francis	Status	new => resolved
2021-09-02 13:12	francis	Resolution	open => fixed
2021-09-02 13:12	francis	Fixed in Version	=> 5.3.0
2021-09-02 13:12	francis	Note Added: 0015433