Category: Changes

Categories
Announcements Changes

Mail: New Spamtrap-Based SpamAssassin Tests

We’ve added two new SpamAssassin tests using on our spamtrap data.

RCVD_IN_ROLLERNET_TRAP – This test means that an IP address matched one that was seen in the headers of a message submitted to a spamtrap. Since this includes all headers it’s possible for a faked IP to end up on this list, but at the same time that faked IP is being used as part of a spam run. Useful for scoring but possibly not outright blocking due to all headers being considered. Default score is 1.5

CLIENT_ROLLERNET_TRAP – This test means that the client IP address has submitted to a spamtrap. This should generally be safe for blocking and scoring since the IP is the actual connecting client address when it submitted something to a spamtrap. Default score is 3.

The spamtrap will exclude an IP address if it’s listed on DNSWL.org, but we do not check any further to see who the IP address belongs to. For example: if Gmail started spewing spam into the trap their IP addresses would be listed (unless it’s on DNSWL), so if gmail.com is critical to you and you want to use the spamtrap data you would want to add your own whitelist entry for gmail.com.

Categories
Announcements Changes Status

Mail: New URIBL Restrictions on SMTP AUTH

Starting on December 19th we’re no longer going to accept mail submitted to our SMTP AUTH system with a URI classified as black, grey, red, or gold on URIBL. These categories contain domains that are either actively used by spammers or found in unsolicited bulk mail. This is currently being treated as a trial change.

The “grey” category is a special case. It contains domains that are used by bulk or commercial mail, which may not be spammers in the strict sense, but are nevertheless against our policy for SMTP AUTH submissions (no bulk or marketing mail).

Our goal is quality of mail through our submission system in order to maintain a high reputation for our customers that depend on us for routine communication. Because we are not a “bulk mail” outfit we are unfortunately unable to accommodate bulk mail use cases, and it would be more appropriate to use the mailer’s service to send bulk mail instead of ours.

If you find you’re having trouble submitting messages after this change, contact support so we can investigate. Marketing-type mail should be sent directly to the intended recipient and not rely on forwarding or resending.

Categories
Announcements Changes

Mail: New Header X-Rollernet-Client

We’ve added a new header to mail we handle called “X-Rollernet-Client”. This header will contain the IP address of the server that connected to us without having to handle “Received” headers. This will put the client IP at the fingertips of customers that want post-process their mail and need the client address for any reason.

The IP address will be formatted in square brackets and IPv6 addresses will be fully expanded. An error is indicated by empty square brackets.

Normal IPv4 client example:

X-Rollernet-Client: [192.0.2.10]

Normal IPv6 client example:

X-Rollernet-Client: [IPv6:2001:0db8:4001:0c0b:0000:0000:0000:022b]

Error example:

X-Rollernet-Client: []
Categories
Changes

Mail: Support for DNSWL

We’ve reactivated support for DNSWL (www.dnswl.org) in SpamAssassin. The following tests have been enabled:

  • RCVD_IN_DNSWL_HI
  • RCVD_IN_DNSWL_LOW
  • RCVD_IN_DNSWL_MED
  • RCVD_IN_DNSWL_NONE
Categories
Announcements Changes

Secondary DNS Transition to Paid-Only

The next update to the account control center will remove free Secondary DNS and add the “Basic” paid service level. Existing Secondary DNS zones won’t be disabled at this time, but no changes will be allowed to them unless you have a paid account. Back in March we posted an announcement that we’re going to start discontinuing free services and this is the first step.

You can find that announcement here: http://www.rollernet.us/wordpress/2016/03/changes-are-coming-maildns-prices-free-accounts-and-spam-filtering/

A link to this announcement has also been shown in the account control center for the past 8 months. Although we’re sure to see some complaints no matter how much lead time we give, eventually we have to move forward. That time has come for Secondary DNS.

UPDATE: Effective June 5, 2017, Secondary DNS has become paid-only.