SecureMail · comparison

NoSpamProxy and Conbool — side by side.

If you're evaluating an email security solution with encryption, it pays to look directly at the differences. This page compares publicly verifiable points — as of May 2026.

In three sentences

What matters.

NoSpamProxy is an established email-security suite by Net at Work GmbH in Paderborn, Germany, typically delivered as three modules (Protection, Encryption, Large Files) with long DACH market presence. Conbool SecureMail is a German alternative with a pure cloud architecture, modular per-feature licensing and an integrated message portal. Which fits best depends on your architectural preference, module choice and hosting approach.

The five most common questions, side by side.

Every statement about NoSpamProxy links to a public source. Every Conbool claim is verifiable in a demo.

How is the architecture set up?

Conbool SecureMail

Pure cloud solution. Conbool runs the entire email security in EU data centres on ISO 27001-certified infrastructure. No server setup at the customer site, no appliance, no hardware. Contract party and data processor is Conbool GmbH in Germany.

NoSpamProxyNoSpamProxy

NoSpamProxy is typically installed on-premise at the customer site. Net at Work also offers cloud or hosted options. Which variant fits is your choice.

Source: nospamproxy.de / netatwork.de — product pages. Please check the concrete hosting option directly with the vendor.

Why it matters: on-premise gives full control over data and configuration, but requires operation (server, patches, certificates). A pure cloud solution is faster to deploy and documentable without running your own gateway.

How is the module structure organised?

Conbool SecureMail

Four modules bookable individually: MailGuard (filtering, anti-spam, anti-malware), SecureMail (encryption via S/MIME, PGP, message portal), SecureFiles (large-file transfer) and Disclaimer (centralised signatures). Each module can be enabled or disabled independently.

NoSpamProxyNoSpamProxy

NoSpamProxy is typically organised in three modules: Protection (spam, malware, anti-phishing), Encryption (S/MIME, PGP) and Large Files. The modules are usually licensed as a package.

Source: nospamproxy.de — product and module overview. Current module and bundle conditions via the vendor.

Why it matters: a module suite covers multiple use cases from one vendor. Per-feature licensing makes it possible to enable individual functions selectively and avoid bundle licenses for unused modules.

Which encryption methods are supported?

Conbool SecureMail

TLS (transport encryption), S/MIME and PGP for end-to-end encryption. Additionally an integrated message portal as recipient fallback: recipients without an S/MIME certificate or PGP key receive a secure link to the protected web portal.

NoSpamProxyNoSpamProxy

NoSpamProxy traditionally supports TLS, S/MIME and PGP. The Encryption module covers both internal and external encryption. In this area the core methods of both solutions are similar.

Source: nospamproxy.de — feature description of the Encryption module.

Why it matters: TLS, S/MIME and PGP are established standards and available with both vendors. The difference lies in the recipient fallback — anyone without a certificate needs either a web portal or an alternative delivery path.

How is licensing structured?

Conbool SecureMail

Modular per feature. Term monthly or yearly, no multi-year minimum. You pay per mailbox only for the modules you actually use — MailGuard, SecureMail, SecureFiles and Disclaimer activate independently.

NoSpamProxyNoSpamProxy

NoSpamProxy is traditionally billed per mailbox (or by license tier), combined with the active modules. On-premise operation adds server or hosting costs. Exact conditions are negotiated by the vendor directly.

Source: nospamproxy.de — licensing model and price request. Current pricing via the vendor.

Why it matters: bundle licenses are often cheaper per module if you need all features. Per-feature licensing pays off if you only need individual modules (e.g. encryption only).

How much setup and maintenance is required?

Conbool SecureMail

Pure cloud service. The Outlook add-in is rolled out centrally, configuration runs in the admin portal. First users can be productive within hours. No server maintenance, no patches, no TLS certificate rotation on the customer side.

NoSpamProxyNoSpamProxy

With the on-premise variant a classic installation and configuration is needed (server, AD integration, mail routing, certificates). The cloud or hosted variant reduces this effort according to the vendor.

Source: nospamproxy.de / netatwork.de — installation notes and cloud product page.

Why it matters: setup and maintenance effort is a direct cost driver. Cloud saves server operations and patching, on-premise gives full data sovereignty and control over your own gateway.

Migration checklist

What to watch for when migrating away from NoSpamProxy.

Replacing NoSpamProxy typically runs in five steps — regardless of whether you operate the on-premise install or the cloud variant.

  1. 1. Document NoSpamProxy configuration and active modules

    Capture the active modules (Protection, Encryption, Large Files), license tier, mail-flow rules, AD integration and routing configuration. This inventory is the basis for the later Conbool configuration and is also useful for compliance documentation.

  2. 2. Export existing S/MIME certificates and PGP keys

    Export all active S/MIME certificates and PGP keys from the NoSpamProxy key store. They are imported into the Conbool tenant so that recipient encryption and internal signatures continue without a break.

  3. 3. Move MX routing to Conbool (parallel operation for the test phase)

    Conbool is first activated for a pilot group (e.g. a subdomain or selected mailboxes). NoSpamProxy stays in production. After a successful test phase, MX routing for the main domain is switched over step by step.

  4. 4. Import domain configuration into Conbool

    Modules (MailGuard, SecureMail, SecureFiles, Disclaimer) are activated in the Conbool admin portal. Filter rules, disclaimers and encryption policies are migrated based on the NoSpamProxy inventory. The Outlook add-in is rolled out centrally.

  5. 5. Decommission NoSpamProxy server or let the cloud tenant expire

    Once all mailboxes are migrated and the audit log is archived, the on-premise server can be deactivated. Cloud variant: terminate the tenant at the end of the contract. Archive retention data per GDPR Art. 30.

These steps apply to current NoSpamProxy versions. For connectors to DMS systems, archiving or specific 32Guards configurations we review the integration in the consult.

Decision aid

When Conbool, when NoSpamProxy.

Conbool SecureMail fits when …

  • You want a pure cloud solution without running your own servers.
  • You want modular per-feature licensing instead of a module bundle.
  • An integrated message portal as recipient fallback simplifies your workflow.
  • You want monthly or yearly cancellable billing, no multi-year lock-in.

NoSpamProxy fits when …

  • You need on-premise operation with full data sovereignty over your own gateway.
  • You prefer the established Net at Work ecosystem and support from Paderborn.
  • You have already invested in NoSpamProxy server infrastructure and want to keep using it.
  • A module suite (Protection, Encryption, Large Files) from one vendor fits strategically.

Also compared

Further email-security alternatives and cross-comparisons.

NoSpamProxy is often weighed up against SEPPmail, Hornetsecurity, Mimecast and Cryptshare. Here are the direct comparison pages.

Frequently asked

See Conbool SecureMail in your own setup.

30-minute demo. Cloud service hosted in the EU.

Sources and fairness note

Statements about NoSpamProxy rely exclusively on publicly accessible sources: nospamproxy.de, netatwork.de and the related product and module descriptions. Claims about internal processes or architecture details not publicly substantiated are avoided. Statements about Conbool rely on our product documentation and contractual commitments.

As of May 2026. For your final decision we recommend you ask both vendors directly about the points relevant to you and get statements confirmed in writing.

NoSpamProxy is a trademark of Net at Work GmbH, Paderborn. Conbool is a trademark of Conbool GmbH. This page is an editorial comparison — not official NoSpamProxy or Net at Work material.