One System, Many Senders: Introducing Outbound Email Profiles in Znuny 7.3
If your organization uses Znuny with multiple sender addresses — think support@, sales@, noreply@ — you've probably run into a familiar challenge: all outgoing emails go through a single, shared mail configuration. That works fine when everyone sends the same way. But in reality, different teams, domains, or compliance requirements often call for different transport settings, credentials, or even entirely different sending methods.
Znuny 7.3 solves this cleanly with Outbound Email Profiles without require 3rd party add-ons.
What Are Outbound Email Profiles?
Outbound Email Profiles let you define a dedicated email sending configuration for each sender address in your Znuny system. Each profile is independent — it has its own transport module, authentication settings, and server configuration.
When an outgoing email is sent, Znuny automatically matches the sender address to the right profile and routes the message accordingly. No manual selection, no workarounds.
Why Does This Matter?
Consider a few real-world scenarios:
- Your support team sends via your company's SMTP server with password authentication.
- Your sales team uses a Microsoft 365 account and needs to send via MS Graph with OAuth2.
- An automated notification address runs through a local sendmail setup on the server.
Before Outbound Email Profiles, you'd have to pick one configuration for all of these — or build custom workarounds. Now, each address simply gets its own profile.
How to Set It Up
Step 1: Enable MultiSendmail
First, activate the feature in your system configuration by setting the SendmailModule to:
Kernel::System::Email::MultiSendmailThis tells Znuny to use profile-based routing rather than a single global configuration.
Step 2: Create Your Profiles
Navigate to Admin → Outbound Email Profiles and click Add Outbound Email Profile.
For each profile, you can configure:
- Module — Choose the transport: SMTP, SMTPS, SMTPTLS, MS Graph, or Sendmail
- Host & Port — The mail server to connect to
- Authentication Type — Password-based or OAuth2 token
- OAuth2 Token Configuration — Link directly to an existing OAuth2 token config (ideal for GMail, MS Graph / Microsoft 365)
- Email Address — The sender address this profile applies to
- Fallback — Mark one profile as the default for any address without a dedicated profile
- Timeout & SSL options — Fine-tune connection behavior per profile
Not every setting applies to every module. For example, the Command field is only relevant for Sendmail, while Host, Port, and Authentication are used for SMTP-based setups.
Step 3: Match Profiles to Sender Addresses
Each profile is tied to a system email address configured in Znuny. When an outgoing email's sender matches a profile, that profile handles the delivery automatically.
If no match is found, Znuny falls back to whichever profile has the Fallback option enabled — so you're always covered.
A Practical Example
Let's say you have three sender addresses:
- support@example.com uses SMTPTLS with a password
- sales@example.com uses MS Graph with an OAuth2 token
- noreply@example.com uses Sendmail
With Outbound Email Profiles, each one gets its own dedicated setup. Your support tickets go out through your internal mail server, your sales emails authenticate via Microsoft 365, and automated notifications use the local sendmail binary — all without any manual intervention at send time.
The Bottom Line
Outbound Email Profiles provide the flexibility in email delivery that growing organizations genuinely need. Whether you're managing multiple brands, meeting compliance requirements, or simply mixing cloud and on-premise infrastructure, this feature gives you precise control over how every message leaves your system.
It's available in Znuny 7.3. Head to your Admin panel to get started.
- Blogpost
- Product Updates