Welcome
Thank you for joining us to test the latest version of ORF! Version 6.10 brings a variety of new features, enhancements, and refinements. These include new filtering actions, additional filtering options, improved greylisting and various other changes. In addition, we have addressed several bugs to improve overall performance.
Your feedback is important to us, so please take some time to explore and let us know what you think.
Read on to learn what's changed and get the new beta.
What's New?
NEW: Service & Administration Tool
-
ORF now officially supports Microsoft® Windows Server 2025
-
A new action called Insert Security Banner has been added to the list of Accept & Modify filtering actions. It allows inserting
a security notice into blacklisted emails to alert recipients to suspicious messages
-
A new option has been added to the Accept & Modify filtering actions to send a copy of the email rather than redirecting it. This allows the original message to continue to its destination while also being delivered to an alternate recipient
-
New local policy options are now available in the DMARC Test settings, providing the ability to filter emails when the author (From) cannot be verified due to a missing policy record or specific verification issues
-
A new error type, "Vulnerable signature", has been added to the DKIM Error List. This entry is configurable when "Blacklist emails on neutral and
permerror" is enabled in the DKIM Test settings. It currently targets DKIM signatures that use the potentially insecure "l=" (length) tag,
as noted in RFC 6376, Section 8.2.
-
The SPF Test log settings now include an option to record the queried domain's SPF record in related log messages
-
A feedback window now appears after updating ORF, allowing you to easily share your thoughts with us
IMPROVED: Service & Administration Tool
-
Greylisting logic has been enhanced to eliminate excessive delays caused by certain mail service providers (e.g., Google) that retry email delivery from different mail servers with varying IP addresses after the initial temporary rejection
-
Data Source Names (DSN) are now displayed in the SQL External Database Configuration
-
Updated SMTP response codes for the DKIM Test and DMARC Test
-
Improved default SMTP responses for the DKIM Test "neutral" and "permerror" results
-
Added DMARC author domain to the SMTP response field list
-
Added a domain format check to the ARC Signing settings page
IMPROVED: Logging & Log Viewer
-
Data Source Names (DSN) are now displayed in the Log Viewer for SQL connections
-
Improved error handling when the Log Viewer is connected to a remote ORF service without remote administration rights
-
DMARC Test logs now indicate when SPF and/or DKIM checks are skipped due to domain misalignment
-
GeoIP database initialization failures are now recorded in the logs
CHANGE: Service & Administration Tool
-
The "NiX Spam" service has been removed from the default DNS Blacklist configuration
-
Greylisting now automatically removes database entries that have not received a delivery retry within 12 hours
-
DKIM signatures using the "l" (length) tag now return a "neutral" error result to better align with RFC 6376, Section 8.2.
-
IPv6 resolution is now enabled by default in the built-in DNS resolver
-
The IPv6 parser now accepts the non-standard shortening of a single 16-bit zero field
-
"None" results from DKIM and SPF checks are no longer added to Authentication-Results and ARC-Authentication-Results
headers if the checks were skipped during DMARC testing
-
The License Manager will no longer fall back to the Windows system proxy settings if Direct connection (no HTTP proxy) is configured in the
HTTP Proxy Settings and the connection fails
-
The Import button in the HTTP Proxy Settings window has been repositioned and redesigned. It now also supports importing proxy settings
from the Windows system settings
-
The Web Access test on the Information > Status page now verifies both HTTP and HTTPS connections
CHANGE: Logging & Log Viewer
- DNS lookup errors occurring during ARC Signing are no longer logged
BUGFIXES: Service & Administration Tool
-
A file creation error (EFCreateError) could prevent saving the configuration or completing installation
-
Fixed a bug in the SPF Test module that could cause IPv6-originating emails to fail SPF verification when ORF’s built-in DNS resolver handled
A, MX, PTR, or %{i} lookups returning AAAA records
-
Domain names with specific syntax errors could trigger a DMARC verification error during processing
-
DKIM "neutral" and "permerror" entries were missing from the Authentication-Results and ARC-Authentication-Results header
-
SMTP responses configured in Custom Actions on the Filtering > Actions page were being overwritten by the SMTP responses defined in
the Default Action settings
-
When remotely connected to the ORF service, opening the Pending Submissions queue while it contained a GeoIP Blacklist entry resulted
in an error
-
The "Search in logs..." feature of the User-Defined URL Blacklist did not utilize the defined Comment field to locate
related event records in the logs
-
License expiration notifications that appear in the Notifications area were created with an incorrect timestamp
-
Restarting the ORF service could occasionally trigger a license check error in Demo Mode
-
The Repair feature on External Database Configuration > Management ignored "UPDATE" statement errors
-
On some systems, the Network Settings page failed to display the DNS and HTTP proxy configuration summaries
BUGFIXES: Logging & Log Viewer
-
The Resend feature of the Attachment Quarantine failed to group attachments by their original emails before releasing them
-
Errors related to the Auto Sender Whitelist, Directory Harvest Attack (DHA), Greylisting, and Honeypot Test were
not included in the corresponding email event group
-
In Demo Mode, event records were incorrectly grouped in certain scenarios
-
GeoIP Blacklist hits in Test Mode polluted the logs with error messages
Fixed some keyboard shortcuts
-
Downloads
Be sure to read the Installation Notes before installing
the beta version.
ORF Fusion
for Microsoft® Exchange and IIS SMTP Service
version 6.10 BETA R02
released on May 7, 2025
expires on June 30, 2025
size 15.6 MB
Download
System requirements
A separate download of the ORF management tools is available below. Install this package
on workstations to manage ORF remotely. Note that management tools are included
in the full installer packages above (for local management).
The 6.10 Management Tools are not backward compatible. You can only manage ORF 6.10 installations
with the 6.10 Management Tools package. Side-by-side installation of 5.x or 6.x Management Tools is currently not
available.
Installation Notes
Please consider that this is pre-release software and may contain bugs. Install the beta for testing purposes
only.
Upgrading
When upgrading from an existing ORF installation, make sure to create a configuration backup
prior the upgrade,
as described by the Configuration
Backup Guide.
If you need to revert back to the previous version, this backup can be used to restore your previous version
quickly.
Important Exit from the Windows Event
Viewer MMC before the upgrade (see this FAQ article).
Known Issues
The list below contains the issues that we know about the
current beta release. This list is maintained during the lifetime
of the beta; be sure to check back here before reporting an issue.
Issue severity levels are
explained in the FAQ.
Severity |
Issue |
Minor
|
Memory usage
Slightly increased memory usage (does not affect filtering or system stability).
|
Minor
|
Some website links may not work
A few links pointing to our website from ORF and its help system will not be available until the final
release of ORF.
|
ORF Beta Issue History
The list below contains the issues that have been fixed since the R02 beta release.
There are currently no known issues with the latest beta release.
-
DKIM verification failure
Fixed an email body canonicalization issue that could cause DKIM (body hash) verification failures
-
Excessive CPU usage
Fixed a bug where utilizing the “Insert security banner” action could cause excessive CPU usage
-
Missing log details
Fixed missing Author details in logs when the From header email address contained an (invalid) non-FQDN domain
-
Excessive CPU usage
Fixed a bug where utilizing the “Insert security banner” action could cause excessive CPU usage
-
Group construct fix
Fixed a group construct (RFC6854#section-4) parsing issue that caused extraneous information to appear in Author details
-
RECENT Fixed IP reversion switch overwriting domain reversion settings in SURBL Properties
-
Implemented automatic creation of missing tables and updating of column properties for external SQL database configurations
Support
A dedicated support forum is available
for the beta version. Please use this forum for technical support and bug reports. Registration is not required.
Go to forum ⇾
Reporting bugs
When reporting bugs, please share any information with us that
you consider important for reproducing the bug. A few tips on
what we might need:
- Steps to reproduce the issue
- ORF log files (
*.log
) for the time of the issue
- Beta release number (e.g. R01, R02, etc.)
- Platform information (Windows® version, 32/64-bit, Exchange version, Internet Explorer® version)
When sensitive information (such as logs) needs to be shared,
please send these to
[email protected].
You can report issues of all severity, even the smallest things
like typos or grammatical errors.
FAQ
What are the limitations of the beta version?
The beta release is fully functional and contains all planned
features. It is also time-limited and the current release will
expire on June 30, 2025. We will release either the final version or
another beta release before the above date.
What do the different issue severity levels mean?
We define four simple levels for issue severity.
Cosmetic issues are harmless
and do not affect any functionality. These are typically
typos, grammar mistakes and other interface issues.
Minor issues render some
functionality of ORF broken, but they are generally harmless
and do not affect the overall operation of the product.
Medium severity issues cause an
important ORF functionality to be broken. If you rely on the
affected functionality, you may not be able to use the beta
until a fix is released.
Major issues affect the overall
reliability of the software. If such issue is published, you
are recommended to stop using the beta until a fix is released.
Make sure to read the description to understand the risks.
Unknown severity is assigned
to issues where the scope of the issue has not been determined
yet.
Setup says "DeleteFile failed; code 5.", how do I fix this?
You may receive "DeleteFile failed; code 5. Access denied." error from the
Setup regarding orfeesvc.exe
when updating an existing ORF
installation.
This is caused by a program that locks the Windows Event
Log message resource embedded in the ORF Service
binary orfeesvc.exe
. The typical offenders are
the Windows Event Viewer MMC and software
that uses WMI (Windows Management Instrumentation) for reading
the Windows event log.
To fix this problem, exit from the Event Viewer MMC and click "Retry". If the
file is still locked, shut down any software temporarily which
monitors the Windows event log and try again.
If the above does not help, go to the ORF installation
directory and rename orfeesvc.exe
to orfeesvc.bak
,
then click "Retry".
Can you add Feature X?
We are happy to hear your suggestions and they may make it into a
future ORF version.
What are the system requirements of ORF Beta?
The system requirements have not changed since the last ORF release. Check the current system
requirements here.
The Management Tools package can be installed on any modern Windows desktop
OS (Windows XP or later).
Just how stable is the beta?
Early ORF releases were tested in-house by Vamsoft developers for weeks on various platforms. Due to this,
we expect that most issues that may
arise will be lightweight.
Be sure to visit the beta forums every once
in a while, we will publish any bug reports there. You can
also subscribe to the RSS feed of the beta forum.
Can I upgrade to the new beta from ORF X.X?
Yes, the beta setup is fully backward compatible and will update
any earlier ORF Fusion or Enterprise Edition release.
Will I be able to upgrade to the final version from the
beta?
Yes, you will be able to upgrade from the beta in-place.
How do I revert to ORF X.X?
You can revert by uninstalling ORF Beta and installing
a previous ORF version. Once the installation is
complete, restore the configuration backup
you made previously (see the
Configuration Backup Guide).
When is the final version expected?
It depends on the beta test progress. We are committed to
release a stable ORF version to our clients, so the final release can be expected only once the preview
release reaches a reasonable level of reliability.
Will I get ORF free of charge upon its final release?
Your subscription guarantees access to any new ORF releases within the validity period
— this includes this version. Be sure not to let your subscription expire and you will get the new ORF at
no additional cost.
Where do I get more information?
Contact our Customer Service, we
are happy to answer any questions you may have.