-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handling calendar invitations and responses using email #2149
Comments
Thinking about an implemenation, I've no idea on how clients handle https / http addresses in CAL-ADDRESS value types for deeplinks (aka jumping into nextcloud). Refering to RFC 2445 any uri is allowed... http://www.kanzaki.com/docs/ical/calAddress.html .. but most clients may focus on mail. If a deeplink doesn't work, nextcloud may need to subscribe to imap. Although imap is a very interesting sharing / groupware protocol - imho it's out of scope to have a general imap-backend. Another idea is to have a mail server piping incoming emails to an adapter-script, posting the email's content .. but this may be nasty from an operations point of view. |
Duplicate of #2338 |
It's good to see the buttons in the email-body are working nicely. Still, from a usability perspective, it is a big wish to see the email-route working as well. The problem is
Are there any plans to do such server based processing of incoming emails? |
Refs:
From what I got, I can add participants to an event and they are invited by mail.
But: When I respond using the MUA, the response is sent to the authors private mailbox. Nextcloud doesn't get the status.
That's bad, since I need nextcloud to reflect the participant status of an event, even if no MUA updating the event using CalDav is present. This should happen without further processing at the site sending the invitation (Eg. logging in into nextcloud or acknowledging the response in nextcloud): In case of shared calendars, the participants status should be updated at once.
The text was updated successfully, but these errors were encountered: