KB - ORF 5.4.1 Change Log

ORF 5.4.1 Change Log

Article was last updated on January 9, 2017. View products that this article applies to.

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

Changes in version ORF 5.4.1

  • NEW: Microsoft® Exchange 2016 compatibility
    Although ORF 5.4 worked fine with Exchange 2016, the platform was detected by ORF as Exchange 2013. Version 5.4.1 has been updated to detect Exchange 2016 as a separate Exchange version.
  • NEW: Microsoft® Windows Server 2016 compatibility
    ORF is now officially supported on Windows Server 2016.
  • CHANGE: Removed dead surbl.org zones
    A few surbl.org zones went offline since the last version. The default definition set included with ORF now reflects this change.
  • BUGFIX: External Agent exit code actions always enabled
    Fixed bug with ORF ignoring the enabled/disabled state of External Agent exit codes actions.
  • BUGFIX: Inconsistent IP Whitelist logging
    Due to a bug in the IP Whitelist implementation, ORF did not always select the right IP address to be logged as "Related IP" address when a hit occurred. The bug affected only ORF Text Logs and the On Arrival filtering point.
  • BUGFIX: SPF evaluation limit counters do not propagate out from recursion
    The overall DNS lookup limit (max. 10) for SPF terms ("include", "a", "mx", "ptr", "exists" and "redirect") was not tracked as a single global limit for all evaluations, but just for a single instance of a recursive evaluation. Because of this, the total number of DNS queries triggered by the SPF terms might have exceed the limit specified in RFC-7208 (Section 4.6.4), unless the limit was reached in a recursive evaluation.
  • BUGFIX: Incorrect severity level assigned to ESpfTempError exception
    Timeout occuring during the retrieval of an SPF record resulted in ORF logging an ESpfTempError exception with Error severity, instead of a more informative message with the proper Warning severity.
  • BUGFIX: Before Arrival SMTP actions for the HELO Blacklist cannot be edited
    Changes made to the SMTP action of the HELO Blacklist were not persisted in the configuration.

Applies To

The article above applies to the following products and versions:

  • ORF 5.4.1
hnp1 | hnp2