Configuration Change Warning Not Displayed

Published

First published on November 28, 2018.

Description

When clicking the ’Connect...’ button on a test configuration page in subscriber mode, the ORF Administration Tool will connect to the publisher server right away without checking or asking whether any local configuration changes should be saved.

Workaround

There is no workaround.

Fix

The bug will be fixed in the next version.

Wrong Attachment Filtering Action on Memory Error

Published

First published on October 22, 2018.

Description

When the attachment evaluation process is interrupted by a memory error, the filtering action that is associated with the first filter expression on the attachment blacklist gets executed no matter the test result.

Workaround

There is no workaround.

Fix

The bug will be fixed in the next version.

Increased Memory Usage & Oversized PowerLog Reference File

Published

First published on October 22, 2018.

Description

Due to a bug in the PowerLog Reference module, the plogrefs.dat file that is used by ORF to reduce the size of PowerLogs (.opg files) can itself become oversized with time in case there are IP expressions on the IP Whitelist or IP Blacklist. Instead of creating a single reference entry (ID) for each IP expression on the lists, a new reference entry is added to the plogrefs.dat file on each IP Whitelist and IP Blacklist hit. This causes increased memory usage as the ORF service has to keep the content of the ever-growing reference file in memory which may lead to out-of-memory errors and crashes in extreme cases (once the plogrefs.dat file grows beyond ~100MBs)

Note, however, that unless your ORF server filters more than 10-20K emails a day and has several IP expressions on the IP Blacklist and IP Whitelist, chances are slim that you will encounter any issues any time soon, or at all.

Workaround

Disable the ORF PowerLogs (ORF will still create text logs):

1. Start the ORF Administration Tool
2. Navigate to the System / Log page
3. Click the Configure button under ORF PoweLogs
4. Remove the checkmark from the 'Enable ORF PowerLogs' checkbox
5. Click Ok
6. Save your configuration to apply the changes (Ctrl + S)

In case the plogrefs.dat file is larger than ~50MBs consider deleting it from the ORF program directory to reset its size (The ORF Service will recreate the file automatically). Note: The ORF Reporting Tool uses the the plogrefs.dat file together with the preprocessed PowerLogs (.ppr files) to generate reports, so we do not actually recommend deleting it unless you do not mind losing some of the data or you absolutely have to. The next version of ORF will repair the reference file automatically while making sure that the least amount of data is lost.

Fix

The bug will be fixed in the next version.