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:
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:
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.
With the SSL setting SmartPOP2Exchange version V8.9 supports SSL up to version V3.0 and TLS up to version V1.2. The exact encryption type and version is defined during the connection. If your provider offers only TLS V1.2, SmartPOP2Exchange uses this version.
With the TLS setting STARTTLS is always used automatically. After TLS V1.0 and V1.1 are no longer available TLS V1.2 is used.
Below is help on configuring Office 365, as an SMTP server, to work with SmartPOP2Exchange.
Office 365 SMTP Relay Connector
To ensure smooth collaboration between Office 365 and SmartPOP2Exchange, you need to configure a connector on the Office 365 to send emails with Office 365 SMTP relay.
Please see the following link for detailed instructions from Microsoft: Configuring a Connector to Send Emails with Office 365 SMTP Relay.
Summary of configuration:
1. Determine the public (static) IP address from which SmartPOP2Exchange will operate. A dynamic IP address is not supported.
2.Select Domains and make sure your domain is enabled and determine the MX record for your domain under Manage DNS.
3.In Office 365, open the Exchange Admin Center. Under Message Flow -> Connectors, create a new connector using the IP address determined from step 1 as the IP address of the sender server.
4.Update your DNS record on the domain registrar website if necessary.
5.In SmartPOP2Exchange, enter the POINTS TO ADDRESS value of the MX record from step 2 as the SMTP/Exchange server.
This is only a rough summary of the full configuration. For detailed information please visit the Microsoft help website linked above.
Please make sure that the connector you use for communication between the Exchange server and SmartPOP2Exchange or the Exchange Server Toolbox allows outgoing emails. Otherwise, your Exchange Server will automatically reject all outgoing messages sent to external recipients.
This problem can be caused by the Windows Defender or other third party anti virus solutions. Add the following paths to the exclusions:
C:\Program Files (x86)\Common Files\JAMSoftware\ClamAVInABox\sanesecuritydbtemp