Mail invitation - There was an error updating your attendance status.

[netaviator]

Steps to reproduce

1. Create an appointment
2. Add attendee to meeting -> mail is created
3. Click accept button in mail

Expected behaviour

Status of attendee should be updated in the calendar view.

Actual behaviour

The following error is shown: There was an error updating your attendance status. Please contact the organizer directly.

Already tried

I already found this post with the same problem and tried to use another mail address for my Nextcloud account without success. There is currently no user sharing the exact same mail address. https://help.nextcloud.com/t/solved-cannot-accept-calendar-invitation/50154

Server configuration

Operating system: Ubuntu 16.04 Web server: Apache Database: MySQL PHP version: 7.2.12 Server version: (see your admin page) 15.0.7 Calendar version: (see the apps page) 1.6.5 Updated from an older installed version or fresh install: Yes, updated since ownCloud 8 Signing status (ownCloud/Nextcloud 9.0 and above):

No errors have been found.

List of activated apps:

Enabled:
- accessibility: 1.1.0
- activity: 2.8.2
- admin_audit: 1.5.0
- bruteforcesettings: 1.3.0
- calendar: 1.6.5
- cloud_federation_api: 0.1.0
- contacts: 3.1.1
- data_request: 1.2.0
- dav: 1.8.1
- deck: 0.6.1
- federatedfilesharing: 1.5.0
- federation: 1.5.0
- files: 1.10.0
- files_markdown: 2.0.6
- files_pdfviewer: 1.4.0
- files_sharing: 1.7.0
- files_texteditor: 2.7.0
- files_trashbin: 1.5.0
- files_versions: 1.8.0
- files_videoplayer: 1.4.0
- gallery: 18.2.0
- groupfolders: 3.0.0
- lookup_server_connector: 1.3.0
- notifications: 2.3.0
- oauth2: 1.3.0
- password_policy: 1.5.0
- provisioning_api: 1.5.0
- quota_warning: 1.4.0
- sharebymail: 1.5.0
- tasks: 0.9.8
- theming: 1.6.0
- twofactor_backupcodes: 1.4.1
- twofactor_totp: 2.1.2
- twofactor_u2f: 2.1.3
- updatenotification: 1.5.0
- workflowengine: 1.5.0
Disabled:
- comments
- encryption
- files_external
- files_retention
- firstrunwizard
- logreader
- nextcloud_announcements
- serverinfo
- support
- survey_client
- systemtags
- user_ldap

Nextcloud configuration:

{
"system": {
"instanceid": "***REMOVED SENSITIVE VALUE***",
"passwordsalt": "***REMOVED SENSITIVE VALUE***",
"secret": "***REMOVED SENSITIVE VALUE***",
"trusted_domains": [
"cloud.xxxxxxx.xxxxxxx"
],
"datadirectory": "***REMOVED SENSITIVE VALUE***",
"overwrite.cli.url": "https:\/\/cloud.xxxxxxx.xxxxxxx",
"dbtype": "mysql",
"version": "15.0.7.0",
"dbname": "***REMOVED SENSITIVE VALUE***",
"dbhost": "***REMOVED SENSITIVE VALUE***",
"dbport": "",
"dbtableprefix": "oc_",
"dbuser": "***REMOVED SENSITIVE VALUE***",
"dbpassword": "***REMOVED SENSITIVE VALUE***",
"logtimezone": "UTC",
"installed": true,
"maintenance": false,
"loglevel": 2,
"theme": "",
"trashbin_retention_obligation": "auto, 14",
"mail_domain": "***REMOVED SENSITIVE VALUE***",
"mail_from_address": "***REMOVED SENSITIVE VALUE***",
"mail_smtpmode": "sendmail",
"mail_smtpauthtype": "LOGIN",
"updater.release.channel": "stable"
}
}

Are you using external storage, if yes which one: local/smb/sftp/... no

Are you using encryption: yes/no no

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/... no

Client configuration

Browser: Firefox , Chrome

Operating system: Windows 10, macOSX, iOS

CalDAV-clients: iOS

Logs

Web server error log

Nothing

Log file (data/nextcloud.log)

Nothing

Browser log

Nothing

[Beheadedstraw]

I said easiest, I didn't say most logical. Nextcloud was never meant to be a public cloud software anyways so it makes sense to keep mostly everything local to nextcloud.

The more logical approach is to just use a token based system for meeting/calendar confirmations and store the email into an "unregistered users" table of sorts so they can register as a user later if given permission.

Feel free to submit ideas of how to fix it instead of complaining and not giving a solution to the problem.

On Tue, Jun 27, 2023 at 1:21 PM Nik @.***> wrote:

The easiest way to fix this right now is to just not allow invitations to anyone outside of Nextcloud.

Oh, then I know how solve all bug and problems in any software: just avoid using it! Problems?

— Reply to this email directly, view it on GitHub https://github.com/nextcloud/server/issues/15814#issuecomment-1610010165, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNNBZYMRT7PXMG6FT3ZGITXNMQCRANCNFSM4HRDVYWQ . You are receiving this because you commented.Message ID: @.***>

-- Devin Arendt Cell: 815-751-7723

[matwacim]

however -> i use the calender only to invite nextcloud users. and i am nextcloud user myself. as far as i understand you the problem should not happen in this case but it is? It would be new to me that we have duplicate email adresses as it is also unique in the company. so i dont get the problem here. my case is pretty the simplest: nextcloud calender user is inviting another nexcloud calender user to an event. not working when accepting over email. should it?

[Beheadedstraw]

If it's another nextcloud user and there's no duplicate emails then that would be a different bug outside of the scope of the current issue being discussed. Honestly the two issues being discussed here (duplicate emails, non-nextcloud user) should be separated into different bug reports since they're two entirely different scenarios.

On Wed, Jul 5, 2023, 8:36 AM Mat @.***> wrote:

however -> i use the calender only to invite nextcloud users. and i am nextcloud user myself. as far as i understand you the problem should not happen in this case but it is? It would be new to me that we have duplicate email adresses as it is also unique in the company. so i dont get the problem here. my case is pretty the simplest: nextcloud calender user is inviting another nexcloud calender user to an event. not working when accepting over email. should it?

— Reply to this email directly, view it on GitHub https://github.com/nextcloud/server/issues/15814#issuecomment-1621774449, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNNBZ5G7SINCPDYIM5BXA3XOVUU7ANCNFSM4HRDVYWQ . You are receiving this because you commented.Message ID: @.***>

[wunschadresse]

At least for the duplicate email problem I found a thread: https://github.com/nextcloud/server/issues/17146 for the non-nextcloud user, i did not look.

however, both cases do not apply to my case (i am nextcloud user with unique email) , and yet i cannot accept calendar invites from calendars, that have not previously been shared with me. I am rather confused and somewhat surprised that the docs do not properly hint to what is possible under which circumstances and what is not.

[subnoodle]

Dears, i hit the same issue as i was searching for an alternative to my open source groupware (which has calender issues as well). I did not expect hitting this issue, since i now it worked earlier years ago (as far as i remember). So, in my scenario "duplicate email-address" and "Next-Cloud-User only" is not relevant: I want and have to use the calender full in Thundbird and Smartphone, both WITH invitations to any mail-adresses (users & non-users). Since i'm not using NextCloud as UI-client here, it's not a solution to build in some checks in the UI.

Someone asked for more constructive solutions how to solve it, like a token-table for non-user-invitations. This let's me assume that the NextCloud developers are maybe aware of the issue, but it's not that easy to solve.

Can someone of the developers role out the status quo of the invitations-mechanics in NC? (No, i cannot read all the code myself)

Would be a good start to have this years-long issue solve. Until now, this isssue is a showstopper using NC as ical-server.

Thank you, Thomas

[cwerstuik]

Maybe this will help future diagnostic efforts. I read through a number of comments and didn't see this mentioned:

I was able to solve the problem by going directly to the database and cleaning out old users that weren't showing up in the UI from the oc_accounts table. I'm using LDAP for user authentication and groups and so it seems like it would hide users that were removed from LDAP, but wouldn't remove them from the NC database, which is great. I see the benefits of that. But if a user was deleted in LDAP and then recreated with the same email, there would then be two users with the same email recorded in the DB but only one would show up in the UI making it look like there wasn't any duplicate emails.

Maybe it's possible there are other circumstances where user accounts are hidden from the UI, but still stored in the DB and thus cause this problem...

It seems cleaning up the DB of duplicate emails also solved the non-nextcloud invites since everything seems to be working flawlessly now, but I can't confirm this as I wasn't specifically thinking of this scenario. All I know is I couldn't seem to get accepting/declining invites to work at all before and now it all works fine.

Just some ideas: Maybe it would be helpful to have an oc_accounts cleanup option to automate this process or add it as a warning in the "Security & setup warnings" in the admin settings when there are duplicate emails in oc_accounts so it makes admins aware that this will cause problems.

[quenenni]

Hello,

Sorry for the bump, but it's a 5 years old ticket and nothing for the last 8 months for an important feature (we have lots of complains, people saying they are missing rdv etc..)

I understand it's not an easy problem to solve, but any idea when we can hope to see this problem resolved?

Thanks

[nderambure]

Hi @quenenni. I fixed this by unchecking the box "Restrict users to only share with users in their groups". Weirdly, it enables sharing calendar invitations to external users with no error. It's not convenient when you have multiple separate groups on your NXC instance, but it works.

I'm not familiar with the code that managed invitation validations, but it's bound to this checkbox. There is a knob here that should be fixed. Restrict to its own group should permit sharing invitations to external users too. And maybe a second checkbox to restrict to users with an account on the NXC.

[quenenni]

@nderambure Thanks for the tip, but we can't uncheck that box, to respect privacy. That's really something we can't do.

[nderambure]

@quenenni : yep, I'm affraid this is only usefull on NXC instance where you only have one group...kind of workaround.

[subnoodle]

Dear @quenenni, yes it might be a log running issue. But it‘s really important as you stated yourself. I follow it for some years, since this issue is the show stopper for desicion making for NXC for a plattform for calendar, contacts and issues-tracker. Thank you a lot for this engagement!