KB - ORF 6.9.2 Change Log

This article contains the complete list of changes implemented in ORF 6.9.2 compared to the previous 6.9.1 release.

Changes in version ORF 6.9.2

• IMPROVEMENTS
  • Service & Administration Tool
    • Event Notifications can now be customized to limit the number of email alerts sent for warning, error, critical, and info severity events within a defined time frame.
    • Management Tools (Administration, Log Viewer, Reporting) are now automatically force-closed if reopened after the initial warning before the uninstallation process starts, ensuring no leftover files remain.
• BUGFIXES
  • Service & Administration Tool
    • The Built-in DNS Resolver did not adhere to the configured timeout settings, leading to excessive email processing times when DNS communication was blocked or interrupted, such as by firewall rules or network issues.
    • The DKIM Test signature verification process terminated prematurely upon encountering a DNS timeout error, which could affect the validation of emails with multiple DKIM signatures.
    • Using the Recipient Whitelist in inverse mode ("Exclude all addresses from filtering, except the list below") triggered a filtering error for incoming emails, allowing them to bypass filtering, except for those subject to tests specified in Whitelist Test Exceptions.
    • Configuration Snapshots created in versions prior to 6.8 were not reloadable in the Configuration Snapshot Manager due to a parsing error.
    • The Statistics page displayed incorrect status and statistic information for GeoIP Blacklist filtering.
    • When closing the Administration Tool or disconnecting from an ORF instance an unexpected error message could occasionally appear.
    • Minor UI fixes and improvements.
  • Logging & Log Viewer
    • The Built-in DNS Resolver did not log the TCP fallback message when the DNS response exceeded the UDP packet size limit.
    • The DKIM Test results summary was not logged when all signature checks resulted in DNS timeouts; only DNS timeout warnings were recorded.
    • The SPF Test incorrectly logged "none" (indicating no record) for SPF mechanisms like "include" and "redirect" when related DNS queries timed out, instead of reporting a temporary DNS error.
  • Reports & Reporting Tool
    • A preprocessing issue could lead to truncated data, causing missing statistics in the generated reports.