CONBOOL
  • Blog
  • Documentation
  • Partners
  • Contact
Get started
CONBOOL

Secure and automated email security for businesses - simple, centralized and reliable.

© Copyright 2026 Conbool. All rights reserved.

Awards
  • OMR Leader Badge für E-Mail-Sicherheit
Member of
  • Bitkom Mitglied – Digitalverband
  • BSI Allianz für Cyber-Sicherheit – Mitglied
About us
  • Blog
  • FAQ
  • Partners
  • Contact
Product
  • SecureMail
  • MailGuard
  • Disclaimer
  • Documentation
Add-ins
  • Disclaimer
  • SecureMail
Legal
  • Terms of Service
  • Privacy Policy
  • Legal Notice

FAQ

Frequently asked questions about the platform

Kategorien

FAQ – GeneralFAQ – Conbool SecureMailFAQ – Conbool MailGuardFAQ – Conbool DisclaimerFAQ – Setup, technology, and operationsFAQ – Security and trustFAQ – Pricing, licensing, and packagesFAQ – Typical use cases

FAQ – General

What is Conbool?
Conbool is a secure mail gateway platform for Microsoft 365, Exchange Online, and classic SMTP environments. It combines email security, encryption, and compliant signatures and disclaimers in one central system. The platform is multi tenant and designed for both organizations and IT service providers and partners.
Who is Conbool for?
For SMBs and mid market organizations, teams with strict compliance requirements, and IT service providers and managed service providers who want to roll out email security and compliance in a standardized way.
Does Conbool work with Microsoft 365 and Exchange Online?
Yes. Conbool is built for Exchange Online and integrates into common mail flows. It covers inbound and outbound email without requiring users to change how they work.
Does Conbool work without Microsoft 365?
Yes. Conbool can also be deployed in SMTP setups and hybrid environments.
Do we need to install anything on user devices?
In most cases, no. Conbool operates gateway and flow based. Some specialized features may require exceptions, but the goal is minimal client changes.
How fast can we deploy Conbool?
Typically in a few days rather than weeks. The exact effort depends on your mail flow, domains, tenant structure, and the policies you want to enforce.
Can we test Conbool first?
Yes. A trial or pilot is common. You can start with one tenant, one domain, or a pilot group and then roll out gradually.
How does multi tenant or partner operation work?
Conbool is designed for multi tenant operation. Partners can manage multiple customers separately and reuse standardized policies and templates.
Where is Conbool hosted?
Depending on the offering, as a hosted service or in an environment you control. Mail flows, logging, and retention rules are defined and documented clearly.
What data does Conbool process?
Conbool processes email metadata and, depending on enabled modules and policies, may also process message content and attachments. This is required for security and compliance functions such as scanning, DLP, signatures, or encryption logic. Scope, logging, and storage behavior depend on configuration and the operating model.
Does Conbool store emails permanently?
By default, Conbool is optimized for processing, not archiving. Temporary storage may be required for scanning, queues, and retries. Long term storage is only used if explicitly configured and required for the specific use case.
Can Conbool be used in a GDPR compliant way?
Conbool is designed to support GDPR compliant use. Whether a specific deployment is GDPR compliant depends on the scenario, for example the DPA, hosting, logs, retention, and DLP policies.
Which compliance topics does Conbool cover?
Typical topics include protecting confidential information, secure delivery, consistent signatures and disclaimers, traceability through logs, and policy and role based control.
Can Conbool replace existing email security?
Often yes, or Conbool can complement existing solutions. Many customers start with one module and consolidate over time.
How is Conbool different from single purpose tools?
Conbool combines multiple core capabilities in one platform. This reduces breaks in the mail flow, shortens deployment time, and simplifies operations, roles, templates, and policies.
Are roles and permissions available?
Yes. Typical roles include Administrator, Security Administrator, Compliance and Legal, Helpdesk and Operator, and Read only access.
Are audit logs available?
Yes. Changes to policies and configurations are logged. Depending on the module, security relevant events are also recorded.
How do onboarding and support work?
Onboarding typically includes mail flow validation, DNS and connector setup, a policy workshop, a pilot phase, and rollout. Support can be offered in tiers depending on your needs and operating model.

FAQ – Conbool SecureMail

What is SecureMail?
SecureMail enables secure email communication. It supports S/MIME and PGP, policy driven automatic encryption, and secure portal or fallback delivery when recipients cannot use encryption.

FAQ – Conbool MailGuard

What is MailGuard?
MailGuard protects inbound and outbound email against phishing, malware, spam, malicious links and attachments, and data leakage. Administration and enforcement are centralized and policy driven.

FAQ – Conbool Disclaimer

What is Disclaimer?
Disclaimer provides consistent email signatures, legal footers, and branding. Everything is centrally managed, multilingual, and rule based, without requiring users to manually maintain signatures.

FAQ – Setup, technology, and operations

How is Conbool integrated into the mail flow?
Typically via connectors, smarthost, or TLS routing for inbound and outbound email. The goal is a clear, auditable mail flow.

FAQ – Security and trust

Can Conbool read emails?
Conbool processes email to provide capabilities such as scanning, DLP, signatures, and encryption logic. Access, logging, and storage are restricted, role based, and configurable.

FAQ – Pricing, licensing, and packages

How is Conbool licensed?
Typically per user, domain, or tenant depending on the module and deployment model. For partners, multi tenant licensing and reseller terms are available.

FAQ – Typical use cases

We want consistent signatures for everyone. Is Disclaimer a fit?
Yes, especially if you have many devices, multiple clients, and different departments.
We are worried about phishing and fraud. Does MailGuard help?

Noch Fragen offen?

Wir helfen Ihnen gerne persönlich weiter. Kontaktieren Sie unser Experten-Team für eine individuelle Beratung.

Contact us
When do I need SecureMail?
When you send sensitive data by email or when external communication must be secure, traceable, and compliant.
Does SecureMail support S/MIME?
Yes. SecureMail can support S/MIME workflows including signing, encryption, certificate logic, and policy based control. The exact scope depends on your client and tenant environment.
Does SecureMail support PGP?
Yes, depending on the configuration and setup. The core concept is a policy that decides the secure delivery method, including fallback options.
What happens if the recipient does not have S/MIME or PGP?
A secure alternative is used, such as portal delivery or an encrypted retrieval method. The goal is strong security without extra effort for the sender.
Can rules decide when encryption is applied?
Yes. Examples include specific recipient domains, keywords, labels, file types, DLP matches, or recipient profiles.
Can internal and external recipients be handled differently?
Yes. A common setup is normal internal mail flow and policy driven encryption or portal fallback for external recipients.
Can we add subject prefixes and user notices?
Yes. You can centrally define subject prefixes, notices, multilingual text, and branding.
How are certificates and keys managed?
Depending on the setup, management is centralized and policy driven so mapping, renewal, and lifecycle can be controlled.
Can we confirm whether an email was delivered securely?
Yes. Reporting and logs show which delivery method was used and which rule triggered it.
Does SecureMail affect deliverability?
Security must work hand in hand with deliverability, for example TLS, DKIM, DMARC, headers, and size limits. SecureMail is designed to handle these factors in a controlled way.
Can SecureMail provide extra protection for attachments?
Yes, for example through secure retrieval mechanisms in portal fallback, or via policies in combination with MailGuard.
What does MailGuard protect against?
Typical scenarios include phishing and fraud attempts, malware in attachments, malicious or suspicious URLs, spam and graymail, and data leakage through DLP policies such as PII, IBAN, contract data, or keywords.
Does MailGuard work for inbound and outbound email?
Yes. Inbound it protects users. Outbound it helps prevent data leakage, misdelivery, and reputational risk.
Can policies be separated by department or domain?
Yes. Policies can be structured by tenant, domain, group, role, or other criteria.
Can we block, quarantine, or just tag emails?
Yes. Common actions include blocking, quarantining, delivering with warnings, adding subject prefixes, header tagging, URL rewriting, or removing attachments depending on the policy.
Can we rewrite links?
Yes, if enabled. Links can be routed through a safe redirect, for example with scanning, tracking parameter removal, and exceptions. Alternatively, suspicious links can be defanged.
What does defang mean?
Defanging makes a link non clickable without removing context, for example by using hxxp instead of http. This reduces accidental clicks.
Can MailGuard remove tracking parameters?
Yes. This can improve privacy and reduce tracking.
How does MailGuard handle attachments?
Attachments can be scanned, blocked, quarantined, or controlled via policies, for example by file type, size, or risk indicators.
Can we apply different rules for internal and external email?
Yes. For example, less restrictive internally and stricter externally, or the other way around depending on risk and requirements.
Can we manage false positives?
Yes. Through allow and block lists, exceptions, thresholds, and rule tuning.
Can signals like first time sender or look alike domains be used?
Depending on the feature set and setup, such signals can be used in rules and detection logic. The goal is to reduce impersonation risk early.
Is reporting available for security teams?
Yes. You get visibility into detections, actions, and trends such as top triggers, frequent patterns, and suspicious domains.
Why not just use Outlook signatures?
Outlook signatures are often inconsistent, hard to enforce centrally, and prone to errors, especially with device changes, mobile clients, and mixed client landscapes. Disclaimer solves this centrally and consistently.
Can we use different signatures for departments or locations?
Yes. Through rules, for example by domain, group, user attribute, recipient, or language.
Does Disclaimer support multiple languages?
Yes. Languages can be selected per recipient, per rule, or defined as a default per tenant.
Can we use placeholders?
Yes. Signatures can be populated dynamically from user and company data, for example name, job title, phone number, or logo.
Can we differentiate between internal and external signatures?
Yes. For example, a short footer internally and full legal details plus branding externally.
Can we show campaign banners temporarily?
Yes. This can be scheduled or targeted, for example only externally or only for specific domains.
Are existing user signatures overwritten?
In most cases the content is added server side or standardized. You can define whether user text remains and where Disclaimer is placed.
What happens on replies and forwards?
Disclaimer can distinguish between the first message and follow ups so threads do not grow unnecessarily.
Can we define exceptions?
Yes. Exceptions can be set for specific recipients, senders, subject content, or keywords in the body.
Can we use different layouts per brand or company?
Yes. Multi tenant capability enables different corporate design elements, logos, layouts, links, and legal text per tenant.
Is Disclaimer compatible with encryption like S/MIME?
This is aligned with your security model. Whether signatures and disclaimers are applied before or after encryption depends on your integrity and compliance requirements. Conbool is designed to control the sequence reliably.
Do we need DNS changes?
Usually yes. Depending on the setup this includes MX for inbound mail, SPF, DKIM, and DMARC for deliverability and authentication, plus additional records for validation.
Does Conbool support TLS and domain validation?
Yes. Secure transport and clear validation are standard requirements.
Can Conbool support DKIM and DMARC?
Conbool is designed to work cleanly with DKIM, DMARC, and SPF. The concrete implementation depends on your sending and signature setup.
What does a rollout typically look like?
A typical process includes discovery and current state analysis, a pilot, policy tuning, staged rollout, and then ongoing operations with monitoring and reporting.
Is there a quarantine?
Depending on configuration, yes, for example for spam, malware, or policy violations. Alternatively, messages can be tagged or blocked without quarantine.
Which identities does Conbool use?
Typically via tenant configuration and roles. User identities and attributes can come from directories such as Entra ID, depending on the setup.
Can we pull users and attributes from the directory?
Yes. Importing from Entra ID is common so signatures, group based rules, and policies stay dynamic.
How is monitoring implemented?
Through health and event views, logs, alerts depending on the operating model, and analytics on detection rates and policy effectiveness.
What happens during disruptions or outages?
Robust queueing and retry mechanisms and clear fallback strategies are part of the design. The exact behavior depends on the operating concept.
Who can access logs and content?
Only authorized roles and administrators, depending on your role model and operating setup. The goal is least privilege and traceable auditing.
How does Conbool prevent data leakage?
Through outbound DLP policies, policy driven actions such as blocking or quarantining, and consistent enforcement at the gateway.
How does Conbool protect against phishing and CEO fraud?
Through a combination of domain and URL signals, pattern detection, sender and header indicators, policies, warning mechanisms, and controlled exceptions and allow lists.
Can I buy only one module?
Yes. SecureMail, MailGuard, and Disclaimer can be started individually and combined later.
Are there enterprise features?
Typical topics include advanced roles, audit logging, complex policy models, integrations, and service level agreements.
Are there discounts for partners?
Usually yes, through partner terms and tiered pricing models.
Yes. MailGuard is designed to detect, stop, or clearly flag attacks and suspicious patterns.
We need to send confidential data securely by email. Is SecureMail a fit?
Yes. SecureMail covers encryption and secure delivery methods including fallback.
We want one system instead of three tools. Is that possible?
Yes. Conbool is designed to provide a central mail flow, a unified policy model, and a consistent admin experience.