Spamassassin blacklists
Blacklists are maintained by different organizations or individuals. DNS blacklistsīlacklists are lists of email servers that are known to send spam.
Spamassassin blacklists install#
To use SpamAssassin with hMailServer, you must install SpamAssassin separately. It does hundreds of checks on the email message to determine whether the email message is spam. SpamAssassin is a popular 3rd part y spam system. This test is expected to catch little spam, since spammers can simply skip including the DKIM-Signature header.
Spamassassin blacklists verification#
If DKIM verification is enabled, hMailServer will look for a DKIM-Signature header in every message. If the header is found, hMailServer will verify that the content of the message matches the signature. If no DKIM-Signature header is included, no DKIM verification will be done. The recipient can verify that the message is sent from a server authenticated to send from the senders domain, and that the message content has not been modified in transit. Verify DKIM-Signature headerĭKIM, Domain Keys Identified Mail, is a method to sign the content of messages. For example, if an automatic email is generated by and does not have valid MX records, the email will be deleted (assuming the spam score reaches the delete-threshold). The downside of this option is that the server may reject legitimate email. Turning this feature on prevents hMailServer from accepting them. Some spammers send email from bogus domains that do not exist. If it hasn't, the email is dropped (if the spam score reaches the spam delete threshold). For example, if sends you an email, hMailServer will check if the domain,, has DNS-MX records. If you enable this option, hMailServer will check if the domain name in the sender's email address has DNS-MX records. While this method can be used to detect spam, a lot of legitimate domain owners do not configure their server correctly. The downside with this method is the risk of false positives.
![spamassassin blacklists spamassassin blacklists](https://namecheap.simplekb.com/SiteContents/2-7C22D5236A4543EB827F3BD8936E153E/media/pl_assassin_8.png)
If you have configured hMailServer to check the host in the HELO command, hMailServer will do a DNS lookup and confirm that the sending server has given a correct host name. When another email server delivers an email to hMailServer, it has to identify itself by sending its own host name. hMailServer only treat SPF FAIL-result as spam. More information about SPF can be found on. If not, the email message will be treated as spam. If you enable SPF in hMailServer, hMailServer will check if the sender's IP address matches the IP address in the DNS-TEXT record. Domain owners can, by means of a TEXT record in their DNS, identify the email servers that are allowed to send email from their domain. This page describes the different options. This needs to be regularily run so sa-update is a good candidate to be placed in a nightly cron job.HMailServer includes a number of anti-spam features, which can be found in hMailServer Administrator, under Settings -> Anti-spam.
![spamassassin blacklists spamassassin blacklists](https://help.exacthosting.com/hc/article_attachments/115012215947/mceclip1.png)
![spamassassin blacklists spamassassin blacklists](https://static.proisp.org/img/guides/en/configure-spamassassin-and-spam-box-cpanel/configure-spamassassin-and-spam-box-cpanel-03.png)
![spamassassin blacklists spamassassin blacklists](https://docs.iredmail.org/images/iredadmin/user_profile_spampolicy.png)
To keep the Spam Assassin Rulesets up to date, Spam Assassin includes a program named sa-update. It is no means an exhaustive explanation but like most of my posts, I hope they are helpful to get you up and running so you can explore further on your own systems. That is a brief introductuon on setting up SpamAssassin and showing how it works.