FAQ & 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

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:\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.

Your Exchange Server returns this error if the sender address is blocked by the sender filter of the Exchange Server: https://docs.microsoft.com/en-us/Exchange/antispam-and-antimalware/antispam-protection/sender-filtering?redirectedfrom=MSDN&view=exchserver-2019

Please deactive this filter or at least exclude SmartPOP2Exchange from ever being rejected.

SmartPOP2Exchange only deletes emails from the POP3 server if it has been successfully sent to the destination SMTP server.

If the SMTP server refuses the email more than 3 times it will be saved to the folder "<backup path>\DeliveryFailure" and a summary email will be generated and tried to be delivered instead.

This "error message" is caused by greylisting solutions.
For example, if you are using ESET for Server, even if you disable anti-spam capabilities in its configuration, it will not be greylisted.
To disable greylisting, the Exchange Server Transport Agent must be disabled by ESET: (in the Exchange Server PowerShell)
Disable-TransportAgent -Indentity "ESET FilterAgent

All entries (Page 3 / 13)