New available build notification (93858)

  • Friday, 20th November, 2015
  • 05:10am
This is our spam / virus filter update for customers on the mx1 / mx2.tnpw.net filtering cluster. The information is brought to you by our vendor, SpamExperts.

What's new this week:

Upcoming Debian Linux upgrade

We're continuing to process the manual upgrade requests to our latest OS version. We expect a full roll out to all customers to complete over the next weeks, and will announce that via this weekly update email in advance.

Wildcard Subdomains in sender white- and black-listing

The sender whitelist and blacklist, both for the incoming and outgoing products, will now accept “*” to match sub-domains.  For example, if you wish to accept all mail from billing.example.comoutgoing.example.comreports.example.com, and anything else that ends with “.example.com”, rather than have to individually whitelist each of these domains, you can just whitelist “*.example.com”.  The same applies for blacklisting, if you wish to reject all mail from addresses at those domains.

This can be used with or without a local part, just as with the regular whitelist and blacklist functionality.  For example, perhaps you wish to blacklist sam@*.example.net so that messages from [email protected] and [email protected] and any other address like that is rejected.  The wildcard will also match any number of parts, so this would also block messages from [email protected] as well.

This functionality isn’t exposed in the web interface yet, but will be in an upcoming release, so you’ll need to set these values directly via the API for now.

Changelog:

Filtering (services):
  • Allow wildcard subdomains when blacklisting or whitelisting senders for Incoming or Outgoing Filtering (#25325)
  • The RFC1413 idents on Outgoing connections are now disabled (#26156)
Front-end / GUI:
  • Updated Twitter Bootstrap to the latest version (#22054)
  • Resolved issue with response parsing that could prevent the outgoing whitelisted IPs from being displayed in Spampanel (#26158)
  • Resolved issue with count option on 'API calls history' page as it could incorrectly display +1 (#26165)
  • Resolved issue with Sort by date option in 'API calls history' page (#25993)
  • The link for Microsoft Authenticator (Windows Phone) was updated to the current version in their app store (#26167)
  • Resolved Legacy API admin cleanup on Spampanel API admin/remove method (#26143)
Plugins & Integration tools:
  • No new updates this week
For more information, please do not hesitate to contact us.
« Back