In many companies, email quarantine is considered a standard component of IT security. What may seem like a sensible protective measure at first glance actually entails significant legal risks in practice. A ruling by the Federal Court of Justice makes it clear that companies should reassess the consequences of email quarantine.
After installing cumulative Windows security updates starting in January 2026, some users may no longer be able to log in to the NoSpamProxy Web App. This is due to a new, mandatory Microsoft security feature and a firewall setting. We’ll show you how to resolve the issue.
Your customers are under attack every day: with spoofed sender domains, authentic-looking phishing attempts, malicious attachments and AI-generated text that even experienced employees can no longer distinguish from genuine corporate communications. Email is and remains the preferred entry point for cybercriminals. The question isn’t whether your customer will be affected, but when. You are responsible for the security and satisfaction of your customers and for the quality of your recommendations. That is exactly why it’s worth taking a closer look at NoSpamProxy.
The certification authority SwissSign is revoking a large number of S/MIME Silver certificates. Customers who use NoSpamProxy in conjunction with SwissSign Managed PKI (MPKI) may be affected. There is no security risk for emails or encrypted content. Nevertheless, affected customers should take immediate action.
Imagine this: You receive an email with a seemingly harmless ZIP file attached, just a few kilobytes in size. Your system begins to unzip the file, and crashes. What follows is a system failure, wasted storage space, or, in the worst case, a gateway for further malicious code. The cause is a ZIP bomb, detonating within your IT infrastructure. In this blog post, we explain what ZIP bombs are, how they overload systems through extreme data compression and serve as a distraction for attacks, what variants exist, and how to effectively protect against them using multi-layered security mechanisms like NoSpamProxy.
CEO fraud, phishing, ransomware via infected attachments: Email remains the preferred entry point for attackers. In enterprise environments, the risk is magnified: more mailboxes, more locations, more entry points. And the attacks are becoming more sophisticated. AI-generated text, spoofed sender domains, context-specific attempts at deception – what used to be recognizable by poor spelling is now almost indistinguishable from a genuine sender. Enterprise organizations with hundreds or thousands of mailboxes, complex IT landscapes, and strict compliance requirements have unique needs. This is where NoSpamProxy comes in.
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.
You are currently viewing a placeholder content from Google Maps. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More Information
