We don’t use marketing cookies. Functional cookies ensure a smooth performance of our website. If you continue to use our services, you agree to the use of cookies. Data protection at JAM OK

Knowledge Base

Welcome to our Knowledge Base. Search or browse through the topics below to find answers to your questions.

In general adding whitelist entries in SpamAssassin can be done by creating a custom SpamAssassin cf

For whitelisting a single address you may use one of the following syntax

 

whitelist_from user@domain.tld

or

whitelist_from *@domain.tld

to whitelist all senders from a single domain.

 

We recommend to create a new cf-file at  C:\ProgramData\JAM Software\spamdService\sa-config

and name it e.g. xWhitelist.cf. That way your custom whitelist will be parsed quite late during startup, thus preventing that any of your settings gets overridden by another config file. Please note that you

have to manually restart SpamAssassin Daemon control service to apply your changes.

 

You'll find a lot of information on the official docs or SpamAssassin Wiki.

Please run the setup of the licensed full version.
Please do not uninstall the previous installed trial version.
All settings will be retained.

Yes, the SpamAssassin used checks SPF records. The default settings for SPF can be found in 25_SPF.cf or the corresponding scores in 50_scores.cf. If you are using "Exchange Server Toolbox" the best way to set your own scores is to use the built-in editor for creating custom SpamAssassin config files which you can find under Spam Options.


For more information about the options, see:
https://cwiki.apache.org/confluence/display/SPAMASSASSIN/

Alternatively, you can manually create your own .cf file in which you define your "rules", this should only come last alphabetically, since SpamAssassin will evaluate the cf files in numerical-alphabetical order. (For example XMySettings.cf).

Translated with www.DeepL.com/Translator (free version)

URIBL (http://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:
- zen.spamhouse.org
- sbl.spamhouse.org
- list.dnswl.org
- multi.uribl.com


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.

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

  • Now create a "conditional forwarding" on your domain controller for each IP address.
  • Open the DNS management console on the server
     <Server Name> ' "Conditional Forwarding" ' Right click, "New Conditional Forwarding"
  • Enter the domain (in the example: "lists.dnswl.org") and then enter the IP addresses previously queried.

Please see the manual, section "Components and Plugins".

All entries (Page 1 / 5)

Current category: SpamAssassin in a Box