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
We’ve reactivated support for DNSWL (www.dnswl.org) in SpamAssassin. The following tests have been enabled:
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.
Twitter is currerntly suffering from outages today (October 21, 2016) and may be unavailable.
As a reminder our third party hosted status page is at: www.rollernetstatus.com
We’re now blocking submissions on our outbound mail service (SMTP AUTH) that contain URIs on blacklists we check outgoing content against. Previously we would include them as part of a score, however we started to see unacceptable stuff pass because it didn’t matching anything except the bad URI. Scoring is still in effect, but the score for a URI match alone is now above threshold.
Exceptions are being made for the following recipient addresses:
Contact support if you have any questions or have a reporting service address like Spamcop you believe should also be whitelisted.
Yesterday a customer’s compromised outbound accounts (albeit brief) caused our SMTP AUTH server to become blacklisted at Proofpoint. Outbound mail authorization was revoked for that customer in accordance with our policies, however the Proofpoint block lingers.
If you are having trouble contacting someone behind Proofpoint you should encourage them to contact their mail host and/or Proofpoint for resolution. Although we are attempting to reach out ourselves, companies like Proofpoint are more likely to listen to their own customer’s complains about losing legitimate mail than they will listen to us.
As far as we are aware this issue is limited to Proofpoint.
UPDATE : This issue has been resolved as of August 23, 2016.