IceWarp EPOS 3 Server – Release Notes (Version 14.3.0.10)
Pinned FeaturedIceWarp EPOS Server – Release Notes
Version 14.3.0.10 | September 1, 2026
This release focuses on new features, stability, performance, and numerous improvements to the core IceWarp Server, highlighted below.
Several fixes address issues reported in production environments, including a new capability to set 2FA at the user level, improved DKIM validation, fixed duplication of recurring events in GroupWare, fixed duplication of documents in WebDocuments and the connectivity between Mailstore and IceWarp.
Administrator Impact Summary
|
Item |
Status |
|
Service restart required |
Yes |
|
Configuration changes required |
No |
|
Database migration |
No |
|
Breaking changes |
No |
|
Security-related release |
No |
|
Recommended action |
Planned update |
New Features
- SERVER - Added the ability to set 2FA requirements at the user level, allowing for greater customization of security settings.
Improvements & Optimizations
- SERVER - Reviewed the DKIM validation issue caused by a custom footer, noting that it fails when enabled and passes when disabled.
Fixed Issues
- WEBCLIENT - Fixed intermittent failures in renaming newly created folders by addressing the syncing issue with the indexing service.
- WEBCLIENT - Fixed the issue of multiple Background folders being created erroneously for users during login.
- WEBCLIENT - Fixed the duplication of recurring events in the GroupWare application.
- WEBCLIENT - Fixed the issue preventing users from dragging and dropping contacts into the mail compose window.
- WEBCLIENT - Fixed the issue of missing images from pasted screenshots in emails for the India customer.
- WEBCLIENT - Fixed the double-click functionality on calendar events to allow users to edit them.
- WEBCLIENT - Fixed the issue causing an SQL error when searching in all folders.
- SERVER - Fixed the synchronization issue preventing the creation of subfolders in Outlook with Outlook Sync.
- SERVER - Fixed the SMTP access violations as outlined in the support comments.
- SERVER - Fixed SMTP access violations and resolved MDA issues as detailed in the Zendesk Support tab.
- SERVER - Fixed the issue of email messages being stuck in MDA following a mass delivery.
- SERVER - Fixed the duplication of edited web documents when closing the editing session.
- SERVER - Fixed the rejection of static routes with a value in the anti-spam feature on RHEL 9.
- SERVER - Fixed a bug where slow emoji loading in mail composition disrupts autocomplete and email sending functionalities.
- SERVER - Fixed the issue causing Tool.exe to stop working after upgrading to builds 7 or 8.
- SERVER - Fixed the issues with distribution and backup domains as noted in the support comments.
- SERVER - Fixed the connectivity issue between Mailstore and IceWarp as reported in the support tab.
- SERVER - Fixed the backup domain forwarding issue where emails were not directed correctly for non-existent and disabled accounts.
- OUTLOOK SYNC - Fixed the IceWarp Outlook Sync error related to license validation by creating a new license, but the issue persists.
Security Updates
- none
Breaking Changes & Deprecations
- none
Upgrade Notes
- Downtime required: Yes (service restart required)
- Estimated downtime: Up to 15 minutes when upgrading from 14.2.X
- Backup recommendation: Full configuration and data backup before upgrade
- Rollback supported: No
Compatibility & Configuration Notes
- No changes to default configuration values.
- Fully compatible with existing LDAP and Active Directory integrations.
- No changes to supported browsers for WebClient.
Supported systems
- Windows Server (2016 or newer) and Linux (RHEL 8/9, Rocky Linux 8/9, CentOS Stream 9)
- Outlook Sync (14.1 or newer)
- IceWarp Desktop Client (10.0 or newer)
- IceWarp FileSync (14.1 or newer)
- IceWarp mobile app (5.0 or newer) and Authenticator (1.1 or newer)
Support & Feedback
If you experience any issues after upgrading, contact IceWarp Support and reference IceWarp Server 14.3.0.10. Please include the server version, operating system, database type and version and relevant logs when opening a support case.
Post is closed for comments.
Comments
0 comments