Skip to content

feat(kronolith): simplify iTIP invitation mail and templates#63

Merged
ralflang merged 1 commit into
FRAMEWORK_6_0from
feat/itip-invitation-mime
Jun 24, 2026
Merged

feat(kronolith): simplify iTIP invitation mail and templates#63
ralflang merged 1 commit into
FRAMEWORK_6_0from
feat/itip-invitation-mime

Conversation

@TDannhauer

Copy link
Copy Markdown
Contributor

Summary

  • Simplify outbound iTIP invitation MIME to multipart/alternative (plain, HTML, inline calendar)
  • Delegate envelope construction to Horde\Itip\Generator\MimeEnvelopeBuilder
  • Refresh notification templates and show recurrence details in mail body
  • Add Invitation: %s translations in all locales

Motivation

Invitation mail previously carried redundant MIME parts (duplicate ICS,
embedded icon) and templates did not surface recurrence information.

Changes

  • Kronolith::sendITipNotifications() uses MimeEnvelopeBuilder
  • Updated templates/itip/notification.html.php and notification.plain.php
  • locale/kronolith.pot and all locale/*/LC_MESSAGES/kronolith.po / .mo
  • Subject Invitation: %s for new invites; Content-Class: calendarmessage

Dependencies

  • Requires horde/itip MimeEnvelopeBuilder (separate PR)

Test plan

  • Manual: IMP attendee sees invitation without separate .ics attachment
  • Manual: recurring invite shows recurrence text in IMP mail body
  • Manual: ActiveSync MeetingRequest still exported for iOS
  • German subject shows Einladung: …

Build invitation MIME via MimeEnvelopeBuilder, remove duplicate
application/ics attachment and embedded icon, refresh notification
templates, show recurrence in mail bodies, and add Invitation subject
translations for all supported locales.
@TDannhauer TDannhauer requested a review from ralflang June 23, 2026 11:30
@ralflang ralflang merged commit d2b3390 into FRAMEWORK_6_0 Jun 24, 2026
0 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants