We’ve added four new content tests to SpamAssassin for the Mailspike DNSBL.
- RCVD_IN_MSPIKE_ZBI 4.1 points
- RCVD_IN_MSPIKE_L5 4.1 points
- RCVD_IN_MSPIKE_L4 3.5 points
- RCVD_IN_MSPIKE_L3 2.9 points
Categories
Category: Announcements
On the heels of our previous announcements we have two more DNSBLs that we’re adding to the default list: ivmSIP and ivmSIP/24. These are available individually as “sip.invaluement.local” and “sip24.invaluement.local” through the account control center DNSBL settings. If you’re not using our default list you’ll need to add them to your configuration in order to take advantage of them. In our test phase we observed excellent results and decided to roll them out officially.
There’s also a new URI DNSBL to compliment content scanning: ivmURI. This has been added to SpamAssassin as INVALUEMENT_URI and INVALUEMENT_IP_URI. The DNSBL tests also have corresponding content tests: RCVD_IN_IVMSIP and RCVD_IN_IVMSIP24.
We’ve created a new internal DNSBL “cidr.dnsbl.rollernet.net” that contains networks that have spammed us directly, contain abusive mail hosts, or providers that are sources of such.
This is not a new feature, other than making it available as a DNSBL. For many years this list of blocked networks has been maintained internally and we handled whitelisting requests on a per-customer basis. By moving it to a DNSBL you will now see entries in the mail logs, can opt to omit it from the DNSBL config, and add whitelist entries online. Additionally, anyone not using the DNSBL feature but is using SpamAssassin will now have access to it through the “ROLLERNET_CIDR” test.
The disadvantage of moving to a DNSBL is that anyone with the DNSBL feature disabled (or aren’t using the default list) may start seeing spam from these networks that were previously directly blocked by the internal list. We recommend enabling DNSBL and configuring “cidr.dnsbl.rollernet.net” to return to the previous behavior.
Networks are added through direct observation (or brought to our attention) and correspond to “whois” or RIR boundaries. Once added to the list entries are generally never removed unless the network owner requests removal and we can verify in our logs that the listed network is now clean.
UPDATE: On January 11, 2019 the zone name was changed to cidr.dnsbl.rollernet.net. This zone is not accessible outside of our network.
Categories
Mail Mirrors by Date with Folders
We’re going to be adding a Sieve script option for Mail Mirror to file messages in IMAP folders by date, one per day, in the format YYY-MM-DD. Some customers with mirrors that are extremely large (over 30GB inbox size) will have this modification performed retroactively since inboxes that large may have IMAP login trouble due to the index file growing too large and hitting mmap limits. For everyone else this will be a handy way to organize a mirror, especially a full domain mirror which may have thousands of messages per day.
Don’t want to wait for us? Simply add this Sieve script to your existing mirror storage mail box:
require ["date", "variables", "fileinto"];
if currentdate :matches "date" "*" { set "date" "${1}"; }
fileinto "${date}";
All we will be doing is adding the Sieve script above at mirror storage creation time (or not, if you opt out).
Categories
Webmail Upgrade: Roundcube 0.7.2
We’ve upgraded our Roundcube webmail option to its latest stable version: 0.7.2. All basic functionality has been verified, but if you encounter any issues please reload or clear your browser cache before reporting them to us.