Rounded Top
Password Hint If you have not signed in recently, your password may be your Customer ID. Check your email archives for your Customer ID or reset your password.

Knowledge Base

Known Issues

Article was last updated on February 12, 2016. View products that this article applies to.

IP Whitelist - Inconsistent Related IP Logging

Version: 5.4 Severity: Minor

Published

First published on February 12, 2016.

Description

Due to a bug in the IP Whitelist implementation, ORF may log the IP address of the last relaying host instead of the source IP of the inbound email. Consequently, the ORF Log Viewer's Related IP column may show the wrong IP address for IP Whitelist events. The bug only affects the On Arrival filtering point and the ORF text logs, but it has no effect on the filtering process itself.

Workaround

There is no workaround for this bug.

Fix

The bug will be fixed in the next ORF version.

External Agents - Exit Code Action State Ignored

Version: 5.4 Severity: Medium

Published

First published on January 21, 2016.

Description

Command-line executables linked to ORF as External Agents return their test results as exit codes when they finished testing the incoming email. Different actions can be assigned to these exit codes, however due to a bug, the state of the exit code actions (enabled or disabled) is ignored by ORF. As a result, the configured exit code actions are always treated as enabled and cannot be disabled.

Workaround - Option 1

Delete the unused or disabled exit codes.

  1. Start the ORF Administration Tool
  2. Navigate to the Blacklists / External Agents page
  3. Select the External Agent and click Modify
  4. Select the Exit Codes tab and select the disabled exit code
  5. Click Delete and click Yes in the confirmation dialog
  6. Click OK and save your configuration to apply the changes (Ctrl + S)

Workaround - Option 2

Use an unexpected exit code in place of the disabled - but valid - exit code, so the actions associated with it will never be triggered. Use this option if you want to preserve the settings and actions associated with the original exit code.

  1. Start the ORF Administration Tool
  2. Navigate to the Blacklists / External Agents page
  3. Select the External Agent and click Modify
  4. Select the Exit Codes tab and select the disabled exit code
  5. Click Modify and replace the valid exit code with an unexpected one
  6. Consider saving the original exit code by adding it to the comments
  7. Click OK and save your configuration to apply the changes (Ctrl + S)

Fix

The bug will be fixed in the next ORF version.

SPF Policy Tester - RFC-7208 Standards Violation

Version: 5.4 Severity: Minor

Published

First published on September 28, 2015.

Description

The overall DNS lookup limit (max. 10) for SPF terms ("include", "a", "mx", "ptr", "exists" and "redirect") is currently 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 exceed the limit specified in RFC-7208 (Section 4.6.4), unless the limit is reached in a recursive evaluation. The bug has no adverse effect on the outcome of the SPF test.

Workaround

There is no workaround for this bug.

Fix

The bug will be fixed in the next ORF version.

Incorrect Severity Level Assigned to "ESpfTempError"

Version: 5.4 Severity: Minor

Published

First published on September 21, 2015.

Description

When a time-out occurs during the retrieval of an SPF record, ORF logs the event "Unexpected SPF Test error. ESpfTempError" with Error instead of Warning severity. Even though the bug does not affect the outcome of the SPF evaluation, you might receive unwanted email notifications if you have ORF configured to notify you about Error type events.

Workaround

Disable email notifications for Error type events:

  1. Start the ORF Administration Tool
  2. Navigate to the System / Log page
  3. Click Configure under Email Notifications
  4. Uncheck the 'Send email about events with "Error" severity' checkbox
  5. Click Ok
  6. Save your configuration to apply the changes (Ctrl + S)

Fix

The bug will be fixed in the next ORF version.

Applies To

The article above applies to the following products and versions:

  • ORF 5.4