NoSpamProxy Server has proven itself over the years as a reliable on-premises solution for email security. Many companies have been using the solution for a long time—and for good reason: control over their own infrastructure, the ability to customize configurations, and independence from external services are compelling arguments for on-premises operation. But the IT landscape is changing—and cloud solutions are increasingly coming to the forefront. NoSpamProxy Cloud offers a compelling alternative to on-premises operation with NoSpamProxy Server. Both versions are developed on a shared codebase. Those who switch will find a familiar environment on the other side. In this article, we highlight the key differences between NoSpamProxy Server and NoSpamProxy Cloud—and explain how to successfully transition to the cloud step by step.
An accountant opens her mailbox in the morning. There is an email from her long-standing IT service provider – with an invoice for €14,800 attached. The IBAN looks strange, but a short note in the document explains: “Please note our new bank details.” She transfers the amount. Three weeks later, the real supplier sends the first reminder for the invoice – because the money was transferred to the wrong account. To an account abroad. The money is gone, irretrievably. Scenarios like this play out every day in companies around the world. This type of attack has a name: invoice fraud, a sub-form of what is known as Business Email Compromise (BEC). What is often overlooked is that there are always two victims. The recipient who transfers the money and the company whose identity was misused for the attack – and which may not even notice.
Effective immediately, public CAs (certification authorities) are no longer permitted to use the Extended Key Usages (EKU) id-kp-clientAuth and id-kp-serverAuth simultaneously in TLS certificates. Those who do not comply with this rule will no longer be included in the Chrome Root Program and will therefore no longer appear in the Trust Store. We provide information about who is affected and what you should do now.
DMARC reports are a key tool for checking whether a domain’s SPF, DKIM, and DMARC configuration is effective and whether all legitimate senders are being authenticated correctly. Deviations – especially inconsistencies or a lack of alignment between SPF and DKIM – indicate problems in the email infrastructure. A practical example shows why a detailed DMARC analysis is essential for detecting and permanently resolving such problems.
Traditional email security solutions check URLs when a message is received. If the linked page appears normal, the email is allowed to reach the inbox. But what if security systems see something different than the users who later click on the link? Cloaking techniques make this possible—and thus call into question a fundamental principle of URL filtering.
An accidentally deleted SPF entry, an unsuspecting email administrator, and weeks of undetected delivery problems—what sounds like a worst-case scenario actually happened. The case shows how 25Reports not only makes problems visible, but also enables them to be quickly resolved.
URL rewriting promises protection against phishing attacks by rewriting URLs in incoming emails and rechecking them every time they are clicked. Link wrapping attacks specifically exploit URL rewriting in emails. Learn how these attacks work and how you can effectively protect yourself against them.
Experts are warning of a critical security vulnerability in React Server Components (RSC), which are part of the popular JavaScript framework React. This vulnerability allows attackers to remotely execute their own code on vulnerable servers. There is no danger for NoSpamProxy customers.
NoSpamProxy
Partners
Latest News
Action Required: Renew Permissions for the Entra ID User Import14.08.2026 - 13:59
NoSpamProxy and TLS Certificates: What Will Change by 202907.08.2026 - 10:00






