Meeting invitations to configured aliases are not treated properly
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Steps to reproduce
- configure email system so that main@example.com and alt@example.com arrive at the same mailbox
- add an account for main@example.com in nextcloud mail
- configure an alias alt@example.com to your main@example.com account
- send a meeting invitation from outlook to alt@example.com
Expected behavior
The meeting invitation should be treated in the same way as if it were sent to main@example.com:
- there should be options to accept, decline etc.
- the invitation should be added to the calendar if accepted
Actual behavior
The meeting invitation is recognised as such, but:
- the following message is displayed: This message has an attached invitation but the invitation does not contain a participant that matches any configured mail account address
- There is not way to accept, decline etc. and no way to add the meeting to the calendar
Mail app version
5.1.6
Nextcloud version
31.0.4
Mailserver or service
local mailserver (exim and dovecot)
Operating system
debian
PHP engine version
PHP 8.2
Nextcloud memory caching
No response
Web server
Apache (supported)
Database
PostgreSQL
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the invitation flow with main@example.com and the configured alt@example.com alias, then trace how the Mail app matches invitation participants to configured accounts. Done means invitations sent to the alias offer accept and decline actions and can be added to the calendar after acceptance, without the participant-mismatch message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- backend, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100