CalendarScheduling
CalendarScheduling
Section titled “CalendarScheduling”Configures calendar scheduling, iTIP messaging, and HTTP RSVP settings.
This object can be configured from the WebUI under Settings › Calendar & Contacts › Scheduling
Fields
Section titled “Fields”enable
Section titled “enable”Type:
Boolean· default:trueEnables the scheduling features for calendar events, allowing users to send and receive invitations
httpRsvpEnable
Section titled “httpRsvpEnable”Type:
Boolean· default:trueEnables the HTTP RSVP feature for calendar invitations, allowing users to respond via a web interface.
httpRsvpLinkExpiry
Section titled “httpRsvpLinkExpiry”Type:
Duration· default:"90d"Sets the expiration duration for HTTP RSVP links, after which they will no longer be valid.
httpRsvpUrl
Section titled “httpRsvpUrl”Type:
Uri?Specifies a custom URL for the HTTP RSVP endpoint, where users can respond to calendar invitations.
autoAddInvitations
Section titled “autoAddInvitations”Type:
Boolean· default:falseAutomatically adds incoming invitations to the user’s calendar.
itipMaxSize
Section titled “itipMaxSize”Type:
Size· default:"512kb"· min: 100Sets the maximum iCalendar object size for incoming iTIP messages.
maxRecipients
Section titled “maxRecipients”Type:
UnsignedInt· default:100· min: 1Sets the maximum number of recipients for outbound iTIP messages.
emailTemplate
Section titled “emailTemplate”Type:
Html?· enterpriseSpecifies the HTML template used for rendering iMIP invitations.
httpRsvpTemplate
Section titled “httpRsvpTemplate”Type:
Html?· enterpriseSpecifies the HTML template used for rendering HTTP RSVP confirmations.
JMAP API
Section titled “JMAP API”The CalendarScheduling singleton is available via the urn:stalwart:jmap capability.
x:CalendarScheduling/get
Section titled “x:CalendarScheduling/get”This is a standard Foo/get method as defined in RFC 8620, Section 5.1.
For singletons, the ids argument should be the literal singleton (or null to return the single instance).
This method requires the sysCalendarSchedulingGet permission.
curl -X POST https://mail.example.com/api \ -H 'Authorization: Bearer $TOKEN' \ -H 'Content-Type: application/json' \ -d '{ "methodCalls": [ [ "x:CalendarScheduling/get", { "ids": [ "singleton" ] }, "c1" ] ], "using": [ "urn:ietf:params:jmap:core", "urn:stalwart:jmap" ] }'x:CalendarScheduling/set
Section titled “x:CalendarScheduling/set”This is a standard Foo/set method as defined in RFC 8620, Section 5.3.
For singletons, only the update argument with id singleton is accepted; create and destroy arguments are rejected.
This method requires the sysCalendarSchedulingUpdate permission.
curl -X POST https://mail.example.com/api \ -H 'Authorization: Bearer $TOKEN' \ -H 'Content-Type: application/json' \ -d '{ "methodCalls": [ [ "x:CalendarScheduling/set", { "update": { "singleton": { "enable": true } } }, "c1" ] ], "using": [ "urn:ietf:params:jmap:core", "urn:stalwart:jmap" ] }'stalwart-cli wraps the same JMAP calls. See the CLI reference for installation, authentication, and general usage.
stalwart-cli get CalendarSchedulingUpdate
Section titled “Update”stalwart-cli update CalendarScheduling --field enable=true