Welcome to our Knowledge Base. Search or browse through the topics below to find answers to your questions.
Categories: SmartPOP2Exchange | Show all categories
SpamAssassin, checks SPF records. You will find the default settings in the file 25_SPF.cf and the corresponding scores in the file 50_scores.cf. Both files can be found in the directory "C:\ProgramData\JAM Software\spamdService\sa-rules\updates_spamassassin_org".
If you are using the Exchange Server Toolbox or SmartPOP2Exchange, we recommend using the built-in editor to create customised SpamAssassin configuration files. You can find this under the Spam options. You can customise the scores of the SPF rules to your own requirements. To do this, add "score" followed by the name of the rule, followed by the new score in the configuration file: "score RULE_NAME 3.8".
Alternatively, you can also manually create your own .cf file in which you define your rules. Please note that this file should come last in alphabetical order, as SpamAssassin analyses the .cf files in numerical-alphabetical order. An example of the file name could be XMySettings.cf. For detailed information and instructions on writing rules in SpamAssassin, you can consult the official article in the SpamAssassin documentation. Here is the direct link to the article: Writing Rules in SpamAssassin
Don't forget to enter the SPF records in your MX record to ensure optimal functionality.
You can test spoofing using www.sendanonymousemail.net. This tool allows you to send anonymous emails, which can be useful for testing purposes.
Please note that this tool must not be misused for illegal activities or for sending spam. It is important to act responsibly and in accordance with applicable laws. Misuse can lead to serious legal consequences.
You can find more information about the possibilities with SpamAssassin on the official website: Apache SpamAssassin Wiki
URIBL (https://www.uribl.com) is a DNS-based Blackhole List which tracks IP addresses which are commonly used for sending spam mails. URIBL is enabled by default for SpamAssassin installations but allows only a certain amount of requests from the same IP every day. If this amount is exceeded, any further requests will be blocked by the URIBL servers with the info notification above.
This typically happens for SpamAssassin installations that use public DNS resolvers such as Google. As any request that is forwarded via the Google servers has the same IP when it reaches the Blackhole list, all requests will share the same limit. For usage of an alternative DNS, please follow these instructions.
For the following domains it is currently useful to set up forwarding to ensure the full functionality of SpamAssassin:
Now determine the name server for each of the mentioned domains.
Open a command prompt and issue the following command (e.g. for "lists.dnswl.org"):
nslookup -querytype=ns list.dnswl.org.
Attention: Do not omit the dot at the end of the domain, otherwise nslookup will append your local domain and the command will not work.
Example output:
list.dnswl.org nameserver = b.ns.dnswl.org
list.dnswl.org name server = c.ns.dnswl.org
b.ns.dnswl.org internet address = 74.208.14.82
c.ns.dnswl.org internet address = 173.255.241.134
c.ns.dnswl.org AAAA IPv6 address = 2600:3c01::21:1000
If you are using an enterprise firewall, you can also make these settings there. The function can be found in the 'DNS' section and is called 'DNS Request Routing' or 'DNS Redirection' or similar.
This happens if SpamAssassin finds rules with a score of zero. Tests with such a score a generally used in third party rule sets.
They check for a specific spam or ham sign but do not actually assign a score to leave it to the SpamAssassin admin if they want to use it or not to optimize their spam detection.
The message can be avoided by assigning a score to the related test or by removing the channel which belongs the particular rule from the sa-update call.
To assign a score, open 'local.cf' in the configuration directory (<%SACONFIGPATH%>) and add the line following line:
The path to rules and/or config dir is invalid. Make sure you run the executable (spamd.exe, spamassassin.exe, ...) from their main directory instead of specifying an absolute path to run.
Most likely SpamAssassin is not able to find a valid rule set. Please run sa-update.bat to download the latest rules.
Please see the official Wiki:
https://cwiki.apache.org/confluence/display/SPAMASSASSIN/
and the official documentation:
In case the required ports are not open, SpamAssassin scans will take much more time - which may cause a timeout.
The integrated SpamAssassin uses DNS (target port 53, TCP and UDP) for blacklist (RBL) requests. You also need to allow requests to target port 2703 (TCP) for Razor2. Otherwise spam scans may last longer than a minute. Alternatively, you may disable Razor2:
We do not work with activation codes because you can find them very easily on the internet. Typically software manufacturers protect against this problem using online activation, but this would make customer dependent on the availability of our activation servers and an internet connection.
We are working with separate trial and full versions instead, where the full version is not freely available for download and must be installed over the trial version. After purchasing our software, customers get an account for our customer area where they can download the full version for at least 12 months. Our customers will also receive a personalized license key, with which they can install the full version. Login data and key should be stored in a safe place. Installing the full version over the trial version will preserve your existing data and settings.
You need to configure a connector to send mail using Office 365 SMTP relay. A detailed help can be found on the Microsoft Help Center.
When using online Exchange Server/Office 365 you need enter the SMTP server name of your online Exchange Server.
This is not "smtp.office365.com".
For a domain like "myDomain.com" the server name is usually composed like "myDomain-com.mail.protection.outlook.com".
To get the correct SMTP server address you need to do a lookup for the registered MX server.
The SMTP server you get for your domain MX lookup has to be used as SMTP server in the SMTP setting of your SmartPOP2Exchange account.
Keep using port 25 and do not use authentication.
Additionally you should add the externally visible IP address of the server running SmartPOP2Exchange as accepted IP in the connection filter settings of your online Exchange Server.
