MultiSendcon™
Multiple Send Connectors for Exchange — Based on Sender
Microsoft Exchange routes all outgoing mail through a single SMTP relay. MultiSendcon breaks that constraint: route each sender's outbound email through the correct relay server, with the right credentials — automatically.
Common scenarios
Multiple companies, one server
You host Company A and Company B on the same Exchange. Each company uses a different mail provider. MultiSendcon routes each domain through the correct relay — automatically.
Mix corporate and Google Workspace addresses
Staff use both @company.com (Exchange) and @gmail.com (Google Workspace) addresses. MultiSendcon sends the Google addresses through Gmail's SMTP relay so authentication works correctly.
IP reputation management
Route high-volume bulk mail through a dedicated IP or provider while keeping transactional mail on your primary relay. Protect your main IP's sender reputation.
What MultiSendcon does
Routes each outgoing message to a different SMTP relay server based on who sent it. Configure unlimited routing rules — by sender email address, domain, or wildcard pattern.
Each routing rule carries its own SMTP relay login credentials. One sender can authenticate to Office 365, another to your ISP, a third to a dedicated transactional mail service — all from the same Exchange server.
All relay connections use TLS encryption. Supports STARTTLS and implicit TLS (port 465 / 587) for every configured outbound route.
Bind outgoing connections to specific local network interface IP addresses per sender. Required when you need outgoing mail from different IPs for deliverability or compliance reasons.
Host multiple companies or domains on a single Exchange server and route each domain's outgoing mail through the correct relay — different provider, different credentials, fully isolated.
Route mail based on the recipient domain in addition to sender address. Useful when a specific destination requires a dedicated relay or authentication.
Works with every version of Exchange Server ever released — through Exchange Server SE (Subscription Edition) — including all Small Business Server editions. No Exchange Online requirement.
The LITE edition (single relay account, no per-sender routing) is bundled free. Useful for Exchange 2003 and earlier when SSL support for outbound SMTP is needed without the full multi-account feature set.
MultiSendcon vs MultiSendcon LITE
Choose the edition that matches your environment.
- Unlimited routing rules by sender
- Per-sender SMTP credentials
- TLS 1.2 / 1.3 support
- Local IP address selection per sender
- Recipient-dependent routing
- Multi-domain / multi-company support
- 30-day free trial
- Single relay account
- SSL / TLS support for outbound SMTP
- Useful for Exchange 2003 and earlier
- Multiple routing rules
- Per-sender credentials
- IP address selection
Common questions
How does MultiSendcon decide which relay server to use?
MultiSendcon intercepts outbound Exchange email before it leaves the server and matches the sender address against your configured routing rules. The first matching rule determines which SMTP relay server and credentials to use. Rules can match by exact address, domain, or wildcard pattern.
Can I route email from different departments through different SMTP accounts?
Yes. Configure one rule per department's sender domain or address pattern. For example: sales@company.com → Office365 SMTP, info@anotherdomain.com → Gmail SMTP. Each rule has its own credentials, TLS settings, and relay server address.
Does MultiSendcon work with Office 365 or Google Workspace?
Yes. Configure an SMTP account pointing to smtp.office365.com (port 587, STARTTLS) or smtp.gmail.com (port 587) with the appropriate credentials. Sender-address-based rules then route each email through the correct provider's relay. If you see "504 5.7.4 Unrecognized authentication type" with Office 365, see our Knowledge Base for the connector configuration fix.
What happens to emails that don't match any routing rule?
Emails that don't match a specific rule fall through to the "Master Relay" configuration — a default SMTP relay used for all unmatched senders. You can also configure MultiSendcon to pass unmatched emails directly to Exchange's built-in send connectors.
How do I install the Exchange Send Connector?
The MultiSendcon installer can automatically create the Exchange Send Connector that routes outbound mail through MultiSendcon. If your environment requires manual setup (e.g., PowerShell remoting is disabled), see our Knowledge Base article "How to manually create the Send Connector in Exchange".
What Exchange versions are supported?
Exchange 2003 through Exchange 2019 and Exchange Server SE. MultiSendcon installs as a Windows service and integrates with Exchange's Send Connector framework — it does not require Exchange agents or transport pipeline plugins.
Version history
Start your 30-day trial today
Full-featured. No credit card. When you buy a license, just enter your key — no reinstallation needed.