How to use Read receipts in IceWarp EPOS Gen 3

IceWarp WebClient follows the more traditional enterprise-style handling of MDN read receipts rather than silently auto-sending them.

Based on the current behavior patterns across the platform:

• IceWarp supports standard MDN/read receipt headers (Disposition-Notification-To)
• The platform distinguishes between:
  • requesting read receipts when sending
  • handling incoming receipt requests

For the WebClient specifically, the practical behavior observed in most deployments is typically:

• when a message requests a read receipt:
  • WebClient shows a temporary notification
  • user can approve or deny sending the MDN
• the receipt is not usually sent completely silently by default
• administrators may influence behavior via server policies
• when the notification gets missed by the user, it can reappear by marking the message as unread

For the IceWarp Outlook Sync, the practical behavior is typically:

• Outlook’s native handling is intentionally disabled
• IceWarp’s own handler takes over
• receipt requests are then processed according to IceWarp logic/preferences (IceWarp Docs)

This aligns with enterprise expectations and RFC recommendations:

• avoid automatic disclosure without user awareness
• especially for external senders

Architecturally, IceWarp handles this at multiple layers:

• WebClient UI prompt layer
• IMAP/GroupWare backend
• SMTP MDN generation
• policy controls on the server side