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.

Direct link to the entry

Yes, SmartSerialMail works with any SMTP server. This includes your Exchange Server.

It is also possible to connect SmartSerialMail to your Exchange Server using Exchange Web Services (EWS).

Direct link to the entry

This email does not imply that someone hacked your email account.
I can assure you that this email was not sent from our company.
Probably someone who bought SmartSerialMail or tested our trial version entered  your email address by accident. If his email server is not configured  correctly, he can write anyone's email address into the "from" field of the  email. But that does not mean that he has access to your email account.

What you see in the "from" field of an email or what is used as reply address  must not necessarily identify the person who really sent the email. This  applies to all emails and does not depend on SmartSerialMail.

Direct link to the entry

Most email servers use so-called spam filters. These filters evaluate an incoming email and decide whether the message is a desired email or so-called spam.

SmartSerialMail generates a spam report by means of the software SpamAssassin. Please note that this spam report may differ from the actual spam scoring of the sent email.

The spam report can help you identify and solve potential spam issues before you will send your email.

Unfortunately, it is virtually impossible to design an email that does not match any spam criteria. Since this depends on many factors (content, language, used images, sender’s email address etc.) there is a variety of spam rules for evaluating an email.

For this reason, we regret that we cannot provide any assistance for the individual spam rules that your spam report may include.

Direct link to the entry

Detecting bounces is not trivial.
There are several types of bounces:
- bounces caused by temporary errors
- bounces caused by permanent errors
- bounces formatted as RFC compliant report
- bounces not formatted RFC compliant, only "usual" e-mail messages with some error text

SmartSerialMail Enterprise collects all bounces with permanent errors and ignores temporary errors.
It decides this by regarding the SMTP error code inside oft he bounce message.
This works well for all RFC compliant bounces, but no for all non RFC compliant messages. Some of the non RFC compliant bounces are covered by the SmartSerialMail detection (those from well known MTAs).

Direct link to the entry