View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006229SOGoBackend Calendarpublic2026-07-09 10:222026-07-09 10:22
Reporterisyssoftwaregmbh Assigned To 
PriorityhighSeverityfeatureReproducibilityalways
Status newResolutionopen 
Product Version5.12.8 
Summary0006229: Store server-side calendar iMIP/iTIP messages in organizer's Sent folder
Description

When SOGo sends calendar invitation emails server-side via CalDAV/iMIP/iTIP scheduling, the messages are delivered correctly to attendees, but no copy is stored in the organizer's IMAP Sent folder.

This makes it difficult for users to track which calendar invitations, updates or cancellations were sent.

From a user's perspective, a calendar invitation sent on their behalf is still an outgoing message. Therefore, users expect these messages to appear in their Sent folder, just like normal sent emails.

Normal sent emails are stored correctly in the Sent folder. The configured Sent folder itself works as expected.

Expected behavior:

When SOGo sends calendar-related iMIP/iTIP messages on behalf of a user, SOGo should optionally append a copy of the generated message to the user's configured Sent folder.

The target folder should preferably use the existing setting:

SOGoSentFolderName

For example, if SOGoSentFolderName = Sent; is configured, server-side calendar invitation, update and cancellation messages should be stored in the user's Sent folder.

A possible configuration option could be:

SOGoStoreCalendarMessagesInSent = YES;

This should apply at least to:

  • calendar invitations
  • calendar updates
  • calendar cancellations
  • possibly attendee replies, if SOGo sends them on behalf of the user
Steps To Reproduce

  1. Configure SOGo with server-side calendar scheduling enabled.

  2. Make sure calendar email notifications are enabled, for example:
    SOGoAppointmentSendEMailNotifications = YES;

  3. Make sure a Sent folder is configured, for example:
    SOGoSentFolderName = Sent;

  4. Use a CalDAV client such as Thunderbird, or the SOGo web interface.

  5. Create a calendar event with at least one attendee.

  6. Save/send the event invitation.

  7. Verify that the attendee receives the invitation email.

  8. Check the organizer's Sent folder.

Actual result:
The invitation email is sent successfully to the attendee, but no copy appears in the organizer's Sent folder.

Expected result:
The invitation email should also be stored in the organizer's configured Sent folder.

The same behavior can be reproduced with event updates and event cancellations.

Additional Information

Environment:

  • Deployment: mailcow-dockerized
  • Mail client: Thunderbird
  • Protocols used: IMAP, SMTP, CalDAV
  • Calendar scheduling mode: server-side scheduling via SOGo
  • SOGoAppointmentSendEMailNotifications: enabled
  • SOGoSentFolderName: Sent

Why client-side sending is not a good workaround:

Thunderbird provides an option for client-side email scheduling for CalDAV calendars.

When this option is enabled, invitation emails are stored in the user's Sent folder because Thunderbird sends them via the user's mail account.

However, this causes other problems in a SOGo environment with server-side scheduling:

  • Duplicate invitation or response emails may be sent.
  • Cancellation emails are not always sent reliably. Mostly not sent at all.
  • Responsibility for calendar scheduling becomes unclear between Thunderbird and SOGo.
  • Behavior differs between SOGo Webmail and Thunderbird.

For this reason, server-side scheduling should remain enabled and Thunderbird client-side scheduling should stay disabled.

This request is not about changing the SMTP sending behavior itself. The current server-side sending behavior should remain unchanged.

The requested feature is only about additionally storing a copy of the generated outgoing calendar message in the organizer's Sent folder.

TagsNo tags attached.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2026-07-09 10:22 isyssoftwaregmbh New Issue