All of our products are being developed in Delphi or C#. Although we use Log4Net with some of the components, they are safe to use, because the reported vulnerability applies to Log4J only.

None of our applications depend on Log4J or any other Java library and are thus not affected by this vulnerability.

This applies to all versions and editions of our applications (TreeSize, SpaceObServer, SpaceObServer WebAccess, HeavyLoad, SmartPOP2Exchange, Exchange Server Toolbox, SpamAssassin in a Box, SpamAssassin for Windows, SmartCallMonitor, SEPA-Transfer, ServerSentinel, and ShellBrowser). It is recommended to always use the latest available versions though to benefit from the latest patches, improvements, and features.

Direct link to the entry

The following folders should be excluded in any external security program to prevent problems with the Exchange Server Toolbox:

• C:\Program Files (x86)\JAM Software\Exchange Server Toolbox\bin
• C:\Program Files (x86)\Common Files\JAM Software\ClamAVInABox
• C:\Program Files (x86)\Common Files\JAM Software\Redis-EST
• C:\Program Files (x86)\Common Files\JAM Software\SpamAssassin
• C:\ProgramData\JAM Software\ClamAVInABox
• C:\ProgramData\JAM Software\Exchange Server Toolbox
• C:\ProgramData\JAM Software\spamdService
• And your configured Filesystem archive folder (if applicable)

This is important so that the Exchange Server Toolbox can check e-mails for viruses without interference. Since the Exchange Server Toolbox receives emails via TCP and temporarily stores them locally for virus scanning, the processes in the listed folders must be undisturbed during these operations. If security software interferes with the process, errors may occur during email processing.

In addition, it can happen that virus signatures used by ClamAV are detected as viruses. If something deletes or blocks the signatures, the Exchange Server Toolbox cannot provide virus protection.

For more information about using Exchange Server Toolbox and an external virus scanner at the same time, see the chapter Anti Virus in the help.

Direct link to the entry

To check if the Exchange Server Toolbox is the reason for emails not arriving, you can search for the email in the Event Viewer. To do this, you can filter by the email addresses or search for emails that were not delivered in the "Delivered" column. If the email is not listed or is marked as "Delivered", then Exchange Server Toolbox is not the reason the email was not delivered.

For more information relevant to the topic, see the articles linked below:

Here you can find instructions on how to remove Exchange Server Toolbox from the e-mail processing chain.

Here you can find information about checking if your Exchange Server is causing problems.

Direct link to the entry

You can check for errors with your Exchange Server using these programs:

https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/

This tool helps detect common configuration issues know for causing performance issues. It also collects useful information.

https://www.frankysweb.de/message-tracking-gui/

This tool provides an easy-to-use UI that makes it easy to track email history. To do this, it requires the Exchange Management Tool.

https://www.frankysweb.de/exchange-reporter-2013/

This tool collects various information and statistics about the email processing process and displays them graphically.

Here you can find instructions to check if the Exchange Server Toolbox might be the cause of the problem.

If you want to completely rule out the possibility that the Exchange Server Toolbox is responsible for problems, you can completely remove it from the email processing chain.

Direct link to the entry

You have two options to remove Exchange Server Toolbox from the email processing chain. Either uninstall the Exchange Server Toolbox or use these two commands in the Exchange Management Shell:

• Disable-TransportAgent "Exchange Server Toolbox Processing Smtp Agent".
• Disable-TransportAgent "Exchange Server Toolbox Processing Routing Agent

After that restart the MSExchangeTransport service. To enable processing again, use the same commands and swap the beginning with "Enable-TransportAgent [...] ". With "Get-TransportAgent [...]" you can check the current status.

Here you can find more information to check if your Exchange Server is responsible for problems.

Direct link to the entry