Knowledgebase

Starting from version 8.9, SmartPOP2Exchange supports the following encryption protocols:

• SSL up to version 3.0
• TLS up to version 1.2

The exact encryption type and version are determined during the connection. If your provider only offers TLS 1.2, SmartPOP2Exchange will use this version.

With the TLS setting, STARTTLS is always used automatically. After the deprecation of TLS 1.0 and 1.1, TLS 1.2 will also always be used.

The integrated versions of ClamAV and SpamAssassin are not updated manually, but with our software updates.

Below you will find assistance for configuring Office 365 as an SMTP server in conjunction with SmartPOP2Exchange.

To ensure smooth collaboration between Office 365 and SmartPOP2Exchange, a connector must be configured on Office 365 for sending emails using the Office 365 SMTP Relay. A detailed guide from Microsoft can be found at the following link: Set up a connector to send mail using Office 365 SMTP Relay.

1. Determine Public IP Address: Identify the static public IP address from which SmartPOP2Exchange will operate. Dynamic IP addresses are not supported.
2. Select Domain: Ensure your domain is activated and locate the MX record for your domain under "Manage DNS".
3. Exchange Admin Center: Open the Exchange Admin Center in Office 365. Create a new connector under "Mail flow -> Connectors", using the IP address from step 1 as the sender IP address.
4. Update DNS Record: If necessary, update your DNS record at your domain registrar's website.
5. Configure SmartPOP2Exchange: Enter the "POINTS TO ADDRESS" value of the MX record from step 2 as the SMTP/Exchange server in SmartPOP2Exchange.

This is a brief summary of the full configuration. For detailed information, please visit the Microsoft help website linked above.

If your Exchange Server is preventing the sending of automatic replies, it is often due to the settings of the connector that manages communication between your Exchange Server and SmartPOP2Exchange or the Exchange Server Toolbox.

For more information, please refer to the Exchange Server documentation.

This problem can be caused by the Windows Defender or other third party anti virus solutions. Add the following paths to the exclusions:

C:\ProgramData\JAM Software\ClamAVInABox\Signatures

C:\Program Files (x86)\Common Files\JAMSoftware\ClamAVInABox\sanesecuritydbtemp

This error message is caused by your Exchange Server and no problem of SmartPOP2Exchange.

Your Exchange Server also includes a simple spam filter module called imf. This one refuses messages detected as spam by default.

Because of this SmartPOP2Exchange saves the email and creates that notification message which is send to the user instead to avoid mail loss.

To solve the problem you need to change the behavior of the Exchange Server and make it accept any message from SmartPOP2Exchange.

You either should disable the content filter and sender filter of your Exchange Server or at least change the action to quarantine instead of refusing.

Please configure your Exchange Server to accept any message from SmartPOP2Exchange. Please note that messages in your POP3/IMAP account already count as finally delivered and because of this the behavior of refusing messages by the Exchange Server is similar to their deletion. If that is your intention we recommend you configure your Exchange Server to delete the messages or move them into quarantine. This avoids the error messages in the log of SmartPOP2Exchange and multiple delivery attempts.

Open the windows Event Viewer. You can find SP2Exchange under Applications and Services. Right-click it and press Properties. Here you can set the maximum log size.

Under certain circumstances a third-party virus scanner might prevent SmartPOP2Exchange from accessing the settings files. This results in SmartPOP2Exchange creating a new default settings file.

SmartPOP2Exchange regularly creates backups of the current settings. If your config file has not yet been overwritten it can easily be restored.

To prevent this add the folder "C:\ProgramData\Jam Software\SmartPOP2Exchange" which contains the config file to the exception list of the software that caused the problem. This is also the folder in which the backups are stored.

Third-party virus scanners sometimes detect the ClamAV signatures as viruses and move them into quarantine.

Please define exceptions for the following directories in your third-party virus scanner:

• "C:\ProgramData\JAM Software\ClamAVInABox\Signatures"
• "C:\Program Files (x86)\Common Files\JAM Software\ClamAVInABox"

You can train the Bayes filter with multiple emails at once. To do this create a POP3 account in your Exchange Server (e.g. named trainSpam) and setup an account in SmartPOP2Exchange pulling emails from that account.
Add a rule for this account applying for any message with the action to train the Bayes filter with spam. To use this account for training attach all spam emails as attachments to an empty email and send it to the trainSpam account. SmartPOP2Exchange will detect the empty wrapper message and only trian the attached messages.

The same can be done with a "trainHam" account.