Tuta Adds Email Forwarding and a Ticket System Interface, Without End-to-End Encryption
Tuta business customers can now forward custom-domain mail automatically and copy it into a ticket system or CRM, but that mail is not end-to-end encrypted.

Encrypted mailbox provider Tuta has added automatic email forwarding for addresses on a custom domain, and a separate interface that copies incoming mail to a ticket system or CRM. Both features were announced in a post on the Tuta blog dated 20 November 2026, and both are aimed at business customers.
The trade-off is stated plainly by Tuta itself: mail that is forwarded, or relayed to a ticket system or CRM, is not end-to-end encrypted. For a provider whose product is built around encryption, that makes the two features an explicit opt-out, switched on by support rather than in the settings.
Key facts
- Announced: 20 November 2026, on the Tuta blog
- Feature 1: automatic forwarding of mail received on a custom-domain address to another address
- Feature 2: an interface that delivers mail for a given address to Tuta and, at the same time, to a ticket system, CRM or similar tool that reads mail over IMAP
- Forwarding plans: Essential, Advanced and Unlimited business plans, according to the announcement
- Ticket system and CRM interface: Unlimited plan only
- Activation: by contacting Tuta support for both features
- Encryption: forwarded and relayed mail is not end-to-end encrypted
- Prices: no new price; the announcement links to the business plans
What Tuta launched
The first feature is classic automatic forwarding. Once it is enabled on a custom-domain address, Tuta keeps a copy of every message it receives and forwards the message to the address the customer chooses. The copy stays in the Tuta mailbox, so the forwarded address is an extra destination, not a replacement.
The second feature is built for teams that run support or sales from another tool. Mail sent to a chosen address is delivered both to Tuta and to a platform that collects mail over IMAP, such as a help desk or a CRM. Tuta notes that this needs an external email provider: the ticket system reads its copy from a mailbox hosted elsewhere, which the customer must create alongside the Tuta address. Before asking support to switch it on, the custom domain must already be set up with the correct MX records, and the address must exist both in Tuta and at the other provider.
Which plans get it
The announcement lists forwarding for the Essential, Advanced and Unlimited business plans, and also says it works with any business plan that uses a custom domain. Tuta's business plans page lists the three tiers as Essential for freelancers, Advanced for teams and Unlimited for businesses, with 3, 10 and unlimited custom domains respectively. The ticket system and CRM interface is reserved for Unlimited.
Tuta has not announced a separate charge for either feature. Neither is a self-service toggle: in both cases the customer opens a support request from the question mark icon in the app.
The encryption trade-off
Tuta encrypts stored mail and offers end-to-end encryption between Tuta users. A forwarding rule, by definition, sends a readable copy of the message to another server, and a ticket system needs readable mail to create tickets. Tuta says so directly: mail sent to forwarded addresses, and mail relayed to ticket systems or CRMs, is not end-to-end encrypted. The only safeguard it describes is the copy it keeps in the Tuta mailbox.
For a business, that means the confidentiality of forwarded mail now depends on the destination as much as on Tuta. Any address that forwards to a third party should be treated as a mailbox hosted at that third party.
What the announcement does not say
Forwarding is one of the most common reasons legitimate mail fails authentication. When a server forwards a message, the forwarding server becomes the sending IP, which usually breaks SPF for the original sender's domain; DKIM survives only if the message is not altered. Receivers then rely on techniques such as the Sender Rewriting Scheme (SRS) or ARC to judge the forwarded copy.
Tuta's announcement does not say whether it rewrites the envelope sender, adds ARC headers or changes forwarded messages in any way. Until that is documented, customers who forward Tuta mail to Gmail, Outlook or a help desk should check how forwarded messages are scored at the destination, especially mail from senders that publish a DMARC policy of quarantine or reject.
What it means for senders
What changes
Tuta business customers can now forward mail from custom-domain addresses automatically and copy it into a ticket system or CRM, at the cost of end-to-end encryption on that mail.
Who is affected
Tuta business customers on custom domains (forwarding) and on the Unlimited plan (ticket system and CRM interface), plus the teams and tools that receive their forwarded mail.
When
Available now on request to Tuta support, announced on 20 November 2026.
Action checklist
- Decide which addresses may lose end-to-end encryption before asking support to enable forwarding or the CRM interface.
- Check your MX records for the custom domain before requesting the ticket system interface.
- Create the matching mailbox at the external provider that your ticket system or CRM will read over IMAP.
- Send test messages from domains with a strict DMARC policy and confirm they reach the forwarded destination without landing in spam.
- Read the Authentication-Results header of a forwarded copy to see how SPF, DKIM and DMARC were scored.
- Review who can read the destination mailbox, since forwarded mail is only as private as the place it lands.
Sources
- Tuta blog: New in Tuta: Email Forwarding and Interface to Ticket System and CRM, 20 November 2026 (primary source)
- Tuta: business plans (primary source)
Related on SMTPedia
SMTPedia News follows our editorial standards. Spotted an error? See how we correct it.
Get SMTPedia news first on Google
Add us as a preferred source to see our stories in Top Stories and Discover.
Add as preferred sourceUseful story?
SMTPedia news is free and independent. A coffee helps us keep covering what changes for senders.
Buy SMTPedia a coffeeNewsletter