As of April 1, 2022, the requirements for email certificates will be tightened. SwissSign will stop issuing e-mail certificates with a 3-year term in March 2022. Only e-mail certificates with a validity of one or two years will then be available. Certificates with a validity of 3 years issued before April 1 will remain valid after the cut-off date and will not be revoked.
Since this week, we have been noticing a new wave of attacks with RTF documents, where spammers use various “file type evasion tricks”.
Since 12 March 2021, we have been aware of problems sending emails to United Internet services. This includes both WEB.de and GMX. These problems result in the connection being refused by the server there and it is therefore no longer possible to send emails to these services. This is the equivalent of a temporary rejection, […]
On February 24, 2021, GlobalSign will have to withdraw some intermediary GlobalSign certificates for compliance reasons. This affects, among others, all “PersonalSign certificates” issued before November 12, 2020 and expiring after February 24, 2021. The affected customers have already been informed about this process by GlobalSign via email. NoSpamProxy customers who obtain their S/MIME certificates from a GlobalSign EPKI must exchange the affected certificates by February 17.
Certain software versions will no longer be supported in the future version 14 of the NoSpamProxy. To avoid problems when updating from version 13.2 to version 14, you should check your infrastructure early and update software that is no longer supported. The following discontinuations do not affect version 13.2 but only version 14.
Currently, due to a security vulnerability, criminals are apparently able to smuggle malicious code into iPhones and iPads via emails. Affected are iOS devices on whichenen the software is installed in version 13.4.1 or a previous version up to version 6 . The Federal Office for Information Security (BSI) assesses the vulnerability as very critical […]
In March, Microsoft will suppress insecure connection requests to Windows domain controllers. This change was announced in August. NoSpamProxy customers can sit back and relax because they only have to check the Active Directory synchronization of NoSpamProxy – in case this hasn’t already been done. If necessary, firewall ports will have to be adjusted.
Dear NoSpamProxy customers,
since a few hours we see in customer environments that send outgoing e-mails from O365 via NoSpamProxy the error “Unable to relay”. We found that Microsoft uses a new certificate to identify all Office 365 email servers, which was issued by a GlobalSign CA rather than Microsoft’s own CA. The NoSpamProxy security check to see if the server is a valid “company e-mail server” fails and the e-mails are rejected. A new Fast Channel Version is available to fix this issue.
We apologize for any inconvenience caused.
Your NoSpamProxy Team
NoSpamProxy
Latest News
Faulty DNSSEC Validation in NoSpamProxy: Causes and Workarounds13.10.2026 - 15:24
NoSpamProxy Inducted Once Again into the Email Security Hall of Fame13.10.2026 - 10:00
ATP and Sandboxing Compared: Two Approaches to Enhancing Email Security08.10.2026 - 10:00




