[GH-ISSUE #15] SCHEDULE-AGENT=CLIENT support #43

Closed
opened 2026-02-25 20:30:46 +03:00 by kerem · 5 comments
Owner

Originally created by @aluxnimm on GitHub (Jul 2, 2015).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/15

Originally assigned to: @aluxnimm on GitHub.

Using a SOGo server when inviting people to an event two invites are sent out to attendees. Once by Outlook and once by the SOGo server. This should be prevented by the use of "SCHEDULE-AGENT=CLIENT"(https://tools.ietf.org/html/rfc6638#section-7.1).

Is there a plan to support this or is it already supported?

Original comment by: johncobley

Original Ticket: outlookcaldavsynchronizer/45

Originally created by @aluxnimm on GitHub (Jul 2, 2015). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/15 Originally assigned to: @aluxnimm on GitHub. Using a SOGo server when inviting people to an event two invites are sent out to attendees. Once by Outlook and once by the SOGo server. This should be prevented by the use of "SCHEDULE-AGENT=CLIENT"(https://tools.ietf.org/html/rfc6638#section-7.1). Is there a plan to support this or is it already supported? Original comment by: johncobley Original Ticket: [outlookcaldavsynchronizer/45](https://sourceforge.net/p/outlookcaldavsynchronizer/45)
kerem 2026-02-25 20:30:46 +03:00
Author
Owner

@aluxnimm commented on GitHub (Jul 2, 2015):

SOGo bug report - http://www.sogo.nu/bugs/view.php?id=2599 for more information.

Original comment by: johncobley

<!-- gh-comment-id:126312229 --> @aluxnimm commented on GitHub (Jul 2, 2015): SOGo bug report - http://www.sogo.nu/bugs/view.php?id=2599 for more information. Original comment by: johncobley
Author
Owner

@aluxnimm commented on GitHub (Jul 2, 2015):

  • status: open --> accepted
  • assigned_to: Alexander Nimmervoll

Original comment by: aluxnimm

<!-- gh-comment-id:126312230 --> @aluxnimm commented on GitHub (Jul 2, 2015): - **status**: open --> accepted - **assigned_to**: Alexander Nimmervoll Original comment by: aluxnimm
Author
Owner

@aluxnimm commented on GitHub (Jul 2, 2015):

Thank you for that info. This feature is easy to add for the organizer. I will test it tomorrow and build a new release with it.

Original comment by: aluxnimm

<!-- gh-comment-id:126312231 --> @aluxnimm commented on GitHub (Jul 2, 2015): Thank you for that info. This feature is easy to add for the organizer. I will test it tomorrow and build a new release with it. Original comment by: aluxnimm
Author
Owner

@aluxnimm commented on GitHub (Jul 3, 2015):

  • status: accepted --> closed

Original comment by: aluxnimm

<!-- gh-comment-id:126312232 --> @aluxnimm commented on GitHub (Jul 3, 2015): - **status**: accepted --> closed Original comment by: aluxnimm
Author
Owner

@aluxnimm commented on GitHub (Jul 3, 2015):

0.98

Original comment by: aluxnimm

<!-- gh-comment-id:126312233 --> @aluxnimm commented on GitHub (Jul 3, 2015): 0.98 Original comment by: aluxnimm
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/outlookcaldavsynchronizer#43
No description provided.