HMailServer believe enabling this can cut down spam by as much as 15-25% and we would recommend enabling the default lists: If the sending IP is blocked, it will reject the message. When these are enabled it will check domains that email your server to ensure they are not on any blocklists. An example implementation can be found on the hMailServer forum:ĭNS Blocklists are lists maintained by different organisations that track IPs’ associated mail traffic. 20 minutes) but we would highly recommend it. SpamAssassin requires some setup (allow approx. SpamAssassin is a popular, third-party mail filter that is updated regularly with additional rules for detecting spam messages. If no DKIM signature is included in the message’s headers, this check will not be executed. We recommend leaving this at the default value. If the relevant sending domain has a DKIM DNS record, hMailServer will check to make sure the message’s DKIM signature matches. Verify DKIM-Signature header - Default value is 5. As such, we recommend setting this score to 5. Any legitimate domain sending mail should have MX records. This will make sure that the sender domain has MX records. We would recommend changing this to 3.Ĭheck that sender has MX DNS records - Default value is 2. This will compare the hostname used in the sending mail server’s HELO to its rDNS ( PTR) record. You can read further about SPF in our main SPF guide.Ĭheck host in the HELO Command - Default value is 2. As such if you are seeing issues with spam, we would recommend changing this to 5. This will only trigger when a domain hard-fails an SPF check. Higher values will result in greater CPU usage. In normal conditions you will not need to increase this above 1024. Maximum message size to scan (KB) is the maximum size an email can be and still be scanned. We would not normally recommend a value any lower than 10. Spam scores should be reviewed for a period of time prior to lowering this. This is usually set to 20 which is quite lenient. Mail items deleted in this manner cannot be recovered. Spam Delete Threshold will delete an email if it is scored at or above the specified value. This is useful for review, providing the specific score individual mail items have received.Īdd x-hMailServer-Reason will show the justification for an email’s spam score. People using Outlook can also create rules in Outlook to automatically move emails marked with tag to their ‘Junk’ folders.Īdd x-hMailServer-Spam will insert the score an email has received into the message headers. This is useful as it will alert your Accounts in hMailServer that an email may be spam. You can modify this text to say something else if needed. When an email hits your Spam Mark Threshold score it will have the start of its Subject line marked with. We recommend leaving this at the default of 5 and changing this higher or lower after a period of testing.Īdd to message subject is used in conjunction with Spam Mark Threshold. Lowering this figure will make your server stricter with spam but also heighten the chance of false-positives, potentially marking legitimate mail as spam if set too low. Spam mark Threshold is used to determine how high a score an email needs before it is marked as spam. Once signed in proceed to Settings > Anti-Spamįrom here we will be configuring hMailServer’s anti-spam settings, covering them tab-by-tab. This can be found in the Start Menu on your server. Start by logging into your hMailServer Administrator program. This article is designed to help you make sure this is configured and provide some further options to help make it its spam detection even better. HMailServer comes with some Anti-Spam protection enabled out-of-the-box.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |