FAQs & Knowledge Base

Welcome to our Knowledge Base. Search or browse through the topics below to find answers to your questions.

Categories: SmartPOP2Exchange | Show all categories

During your maintenance period, you will find them at Downloads/Updates -> Older versions in your customer account. There are the installation files and keys of the two last major versions.

The followings paths should be excluded in any external security program:

  • C:\ProgramData\JAM Software\ClamAVInABox
  • C:\ProgramData\JAM Software\SmartPOP2Exchange
  • C:\ProgramData\JAM Software\spamdService
  • C:\Program Files (x86)\Common Files\JAM Software\ClamAVInABox
  • C:\Program Files (x86)\Common Files\JAM Software\SpamAssassin
  • C:\Windows\System32\config\systemprofile\.spamassassin

This is important so that SmartPOP2Exchange can check emails for viruses undisturbed. Since SmartPOP2Exchange 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 the virus signatures used by ClamAV are themselves detected as viruses. If something deletes or blocks the signatures, SmartPOP2Exchange cannot provide virus protection.

You can find further information on how to use SmartPOP2Exchange and an external virus scanner at the same time in the help under Anti-virus software.

In order to forward emails without a valid recipient to a collective address you need to configure an SMTP error rule. You can configure this rule for a single account or as a global role.

Go to SMTP Error Rules and add a rule with the condition "Match error code with [specified number]. The error number is 550. Add the action "Send copy to [specified recipient]" and set the collective address.

Please note that in order for this rule to work your email server needs to be configured to reject emails with an invalid recipient. You can find instructions on configuring your Exchange Server here.

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

All of our products are being developed in Delphi or C#. Although we use Spring4D(elphi) with some of the components, they are safe to use, because the reported vulnerability applies to Java Spring framework only.

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.

To install SmartPOP2Exchange on another server, do the following:

  • Stop the SmartPOP2Exchange service on the old server
  • File > Export settings
  • File > Export Accountdata
  • Stop SmartPOP2Exchange service on the old server
  • Install SmartPOP2Exchange on the new server
  • File > Import settings
  • File > Import Accountdata
  • Uninstall SmartPOP2Exchange on the old server

Yes, SmartPOP2Exchange and Exchange Server Toolbox can be installed together on the same server. When doing so, you should take this into account:

Problems with direction detection

In older versions there were problems with direction detection when SmartPOP2Exchange and the Exchange Server Toolbox were installed on the same server. To fix this, a rule is now created when SmartPOP2Exchange is installed that automatically assigns a new header field (X-JamMailSource) with a value (MailGateway) to all emails. In the Exchange Server Toolbox, this header is queried under Settings | Advanced | Mail Direction, and emails with this header field and header field value are always considered Incoming.

You can adjust these values if you want, but please make sure that they are the same in both programs.

Always keep versions up to date

Please note that you must always have the latest versions of both programs installed. Otherwise it is possible that SpamAssassin or ClamAV will be updated to a version that the other program cannot use.

Spam and virus scanning in one program only

To avoid wasting time and resources unnecessarily, you should run the spam and virus scans in only one of the programs. Since SmartPOP2Exchange and Exchange Server Toolbox share an installation of ClamAV and SpamAssassin, the scanning results are identical.

You should consider the following things when deciding which of the programs to use for scans:

Advantages of scans in the Exchange Server Toolbox

The Exchange Server Toolbox offers more configuration options and more rule actions for both scans. Therefore, the scans and especially the reaction to different results can be customized in much more detail.

Advantages of scans in SmartPOP2Exchange

Since in this configuration the Exchange Server Toolbox receives the emails directly from SmartPOP2Exchange, rejecting emails in the Exchange Server Toolbox should be avoided (otherwise this will lead to errors in SmartPOP2Exchange). So it is only possible to reject emails (based on scan results) with SmartPOP2Exchange. However, you should keep in mind that the emails have already been delivered to an account, so SmartPOP2Exchange not picking them up can be legally problematic.

This error is caused by new Windows security settings. To fix it, open the Exploit protection Settings. Here, switch to the program settings and specify all EXE files listed in the error message under Add program. You must overwrite the ALSR settings in each case.

Check the event log of the Exchange Server Toolbox or the Windows Event Viewer under Windows Logs | Application for the following message:

"The request was aborted: Could not create SSL/TLS secure channel"

If this is present, you can fix the problem this way:

  1. Press "Windows+R" and open "gpedit.msc".
  2. Navigate to Computer Configuration | Administrative Templates | Network | SSL Configuration Settings
  3. In the right pane, select "SSL Cipher Suite Order" and then click "Edit policy setting" in the center
  4. Select "Enabled" in the new window

You can now copy the contents of the text box under Options | SSl Encryption Collections into a text document. Append the following keys at the end:

  • TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
  • TLS_DHE_RSA_WITH_AES_256_GCM_SHA384

Follow the editing instructions in the right part of the window under "Help".

Then copy the text back into the text box and press "Apply" to save the settings. For the changes to be applied, you must restart the server.

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.

The mail address serves as a fallback for a catch-all account. Mails whose recipients do not exist on the target mail server are delivered to this address.

All entries (Page 1 / 12)