According to this post, there is a major bug in .NET 4.6 which could have a serious impact on every NoSpamProxy installation. Please do not update to .NET 4.6.
On 13th June Version 11 has been released to the public. The new Disclaimer option is the key feature of this version. For the past IT departments had to provide some solutions installed directly on the Mailserver to provide a company wide footer or text signature in mails. This is no longer an issue. With NoSpamProxy you can do this on the central Gateway without the need to add something to your Mailserver.
Of course there has been a lot of improvements to existing features, too. The direct update is supported from 10.x on and will keep all your settings.
The new maintenance release 10.1.282 contains fixes for issues discovered since release of 10.1.196. This fixes cover all areas of NoSpamProxy. So it is recommended you update all components to this version. An optional Reverse-DNS-Check has been added as a new feature, also. Further minor improvements are part of this release, too.
Many customers ask how to block certain attachments, especially potentially harmful ones. Here is how it works.
First of all you have to define a ruleset which you want to use. We call it a content filter policy. Select Presettings (1) and Add (2) to create a new one. Give your policy a good name for what it will do. Now you have to define the attachment types you want to give a special treatment. Click Add (3) and create a new definition. Please be aware your definitions are evaluated from top to bottom and first matching entry will be applied. So if you allow invoice_0815-GmbH_*.zip this should be on top of rejecting *.zip-entry.
Since version 10 the full integration of NoSpamProxy in Office 365 is possible. This article describes the configuration steps required in both NoSpamProxy configuration and Office 365.
An article at Microsoft is worth mentioning in this context that no other SMTP hosts are allowed between an on-premises Exchange CAS or Exchange Edge Transport Server and Exchange Online Protection (EOP). Since NoSpamProxy always works before the complete Exchange infrastructure, this hint can be ignored.