mail:u Disclaimer
Centralized and legally compliant email disclaimers, seamlessly integrated
Why an Email Disclaimer?
Legally compliant email disclaimers are an essential part of corporate communication. As a fully integrated module of the mail:u Gateway, our solution ensures that all outgoing emails are automatically provided with the correct, legally binding information and consistent signatures.
Centrally controlled by the workflow engine or via the Outlook add-in, this eliminates any manual effort for your end users.

Since the processing of signatures and disclaimers takes place directly at the server level in the mail:u Gateway, seamless compliance is ensured.
Regardless of whether your employees send emails via Microsoft Outlook, from a smartphone, or from the webmail client – the legally required information is always attached reliably and in a tamper-proof way.
This protects your company from legal risks and ensures that formal requirements for business communication are always met 100%.
Through seamless embedding in the mail:u workflow engine, you gain unlimited flexibility in assigning your disclaimers. Instead of rigid, global texts, you can use the template engine and variables to define exactly when which signature is applied.
Use expressions, header information, or sender groups to control different disclaimers for different clients, departments, or target domains.
This makes it possible, for example, to ensure that internal emails stay lean while external messages receive the full company disclaimer.
Clever Use Cases in Everyday Life
Many companies view email signatures purely from the perspective of legally required information. However, deep integration into the workflow engine opens up far more dynamic use cases, in which the module stands out clearly from rigid, off-the-shelf tools.
Contextual Control
The system can detect whether an email is being sent to external contacts and only then attach current marketing banners or event notices.
If, on the other hand, it is an internal message or a reply within an already long email thread, an alternative condition applies, attaching only a minimalist short signature so as not to disrupt the reading flow.
Dynamic Content
Using the integrated templates, the system can embed variables such as the sender's name directly into the URL structure.

The goal of the mail:u disclaimer module is maximum technical depth and customizability for your administrators. The module is deliberately designed as a powerful expert tool and forgoes limiting standard building blocks in favor of absolute design freedom.
Using the integrated template editor, employee-specific information such as name, department, phone number, or location can be dynamically embedded into signatures. The system automatically accesses connected directory services such as Microsoft Entra ID, LDAP, or internal data sources for this purpose.
The editor is based on Go templates and integrates the Sprout library, giving you unimagined possibilities at the code level:
- Dynamic Variables: Seamlessly insert placeholders such as
{{.Firstname}}or{{.Department}}into your HTML or text signatures. - Complex Logic: Use if/else conditions, loops (range), and helper functions directly in the editor to dynamically adapt layouts based on available employee data.
- Safe Rendering: Ensure that dynamic links and parameters for tracking or appointment bookings are generated and encoded completely error-free, supported by "safe functions" that don't abort the rendering process on errors.
The technical process of attaching signatures takes place as a fully automated step deep inside the mail:u workflow engine, before any further cryptographic actions take effect.
- Receipt & Condition Check: The email arrives at the gateway via SMTP. The workflow engine compares the message in real time against the condition catalog (e.g. sender group, target domain, file type, or specific header flags).
- Data Retrieval via Directory Sync: If a rule matches, the system retrieves the sender's current attributes (such as givenName or department) via the connected Microsoft Entra ID or LDAP interface.
- Template Rendering: The Go-based template editor now parses the MIME components of the email. The placeholders defined in the editor (e.g.
{{.Firstname}})are replaced with the retrieved directory data. - Delivery & Cryptography: The final rendered signature HTML is inserted into the email body according to standards. Only immediately afterward does the engine execute subsequent actions – such as signing or encrypting via S/MIME or PGP – and hand the message over for delivery.
