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

  • Check for Update
    • TCP and UDP Port 853
    • TCP Port 443
  • ClamAV
    • FreshClam (Signature Updater)
      • TCP Port 53
    • Rsync (SaneSecurity Signature Updater)
      • TCP Port 873
  • SpamAsassin
    • Razor (Regel Updater)
      • TCP Port 2703
    • Querying blacklists (RBLs)
      • TCP and UDP Port 53

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.

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

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:\ProgramData\JAM Software\ClamAVInABox\SignaturesC:\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.

Many spam emails contain syntactically invalid email addresses in the from field. Since most SMTP servers (including Exchange Server) refuse messages with invalid from addresses SmartPOP2Exchange gives a warning when it detects such an invalid address.

With SmartPOP2Exchange V7.2 detected invalid sender addresses are automatically replaced with "invalid@address.com".

For older versions you may create a global rule like this: Condition: "Messages with an invalid sender address" --> Action: "Replace sender address with 'postmaster@domain.com'".

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 which contains the config file (C:\ProgramData\Jam Software\SmartPOP2Exchange) to the exception list of the software that caused the problem. This is also the folder in which the backups are stored.

All entries (Page 2 / 12)