Managed TrekMail SMTP: How It Works

Managed SMTP is the default outbound path for every paid TrekMail plan. You don't configure anything — when you send a message from webmail or any IMAP/SMTP-connected client, TrekMail's outbound infrastructure handles the relay, DKIM signing, reputation management, bounce processing, and rate limiting. This guide explains what's happening behind the scenes, when it's the right choice (almost always), and what the alternative — Custom SMTP — gives you.

When you want Managed SMTP

Use Managed SMTP if:

• You want a single bill for "email service" and don't want a separate Mailgun / SendGrid / Postmark subscription on top.
• You don't have specific reputation-management expertise on the team and trust TrekMail to handle it.
• You're sending normal volumes — under a few thousand a day on Starter, more on Pro and Agency.
• You want DKIM/SPF alignment out of the box. We sign every message with your domain's DKIM key automatically.

Use Custom (BYO) SMTP if:

• You have an existing relationship with a transactional provider (Mailgun, SendGrid, Amazon SES, Postmark) and want to keep using their dashboards and analytics.
• Your sending volume justifies a dedicated IP at an external provider.
• You need specific provider features TrekMail doesn't offer (event webhooks for opens/clicks at the provider's granularity, click-tracking, etc.).
• You're on Nano — Managed SMTP isn't available; Custom is your only path to outbound.

SMTP is chosen per domain: open Domains → pick a domain → SMTP and choose a route. To put a domain on managed sending, select the {Brand} SMTP radio. See Per-Domain SMTP & the Account Default for the full picker, the Make this the account default toggle (so new domains start on this route), and the Apply to all domains button.

Eligibility

On Nano specifically, the plan's can_send flag is OFF for Managed SMTP, which is why it doesn't appear as an option. Custom SMTP is gated only by configuration (BYO uses your external credentials, not TrekMail's send capacity), so Nano users can still send through their own external provider.

How it works end-to-end

When you press Send in webmail or your email client:

1. Your client connects to smtp.trekmail.net on port 465 (SSL/TLS) or 587 (STARTTLS) and authenticates with your mailbox credentials.
2. Our submission gateway accepts the message and validates the From address against the mailbox you authenticated with — you can't impersonate bob@yourcompany.com from alice@yourcompany.com's session.
3. The message is queued for outbound delivery.
4. Outbound delivery signs the message using your domain's DKIM key (dkim._domainkey.yourdomain.com) — the SAME key you published in DNS during domain verification.
5. The message goes through our outbound IP cluster. The IP pool is rotated to balance load and reputation across receivers.
6. Receivers (Gmail, Outlook, Yahoo, etc.) verify SPF (our IPs are in your SPF include) and DKIM (signature matches your published public key), and check DMARC policy. With both passing, the message is accepted.

You don't see any of this. From your side, you click Send and the email arrives. From the receiver's side, the headers look like a properly-authenticated message from your domain.

What "reputation management" actually means

TrekMail's outbound platform does several things automatically that you'd otherwise have to handle yourself or pay an external provider for:

• IP pool diversification. New domains start on lower-volume IPs to build a clean per-domain reputation before being promoted to higher-volume pools. This protects you from being pulled down by another customer's bad behaviour.
• Bounce processing. Hard bounces (recipient doesn't exist) are recorded against your domain and the address is automatically marked for backoff. Repeated hard bounces stop trying that address, saving your reputation from "trying to deliver to dead addresses" signals.
• Feedback loops. Major receivers (Gmail, Yahoo, Microsoft) report when a recipient marks your mail as spam. Those signals come back to us via Feedback Loop subscriptions; we lower the affected sender's reputation score and may pause sending if the complaint rate exceeds threshold.
• Bot-style sending detection. If your sending pattern matches known spammer behaviour (sudden volume spike, identical message body to many addresses, etc.), we pause sending and surface an alert in your dashboard. This is the deliverability-suspension flow described in I Can't Send Emails.
• DNSBL monitoring. We watch the major real-time blacklists (Spamhaus, Barracuda) for our outbound IPs and rotate around them automatically. If your domain itself is listed, that's not auto-fixed — you'd need to address the underlying issue.
• Warmup curve. For new domains, the first 7 days have reduced limits (40% day 1-3, 70% day 4-7, 100% day 8+) to build reputation gradually. See Domain Warmup Rules.

Connection details

When configuring an email client (Outlook, Apple Mail, mobile apps), use these settings:

The same smtp.trekmail.net server handles every customer's mail — it's a shared submission server. Authentication and routing per-customer are based on which mailbox credentials you authenticate with.

Sending limits

Each plan has separate caps for daily send volume and submission rate:

These caps are advisory floor + hard ceiling. Going significantly above the typical day-over-day pattern (e.g. you send 50/day usually, then suddenly 1000) can trigger spike detection that flags for review even within these limits.

For never-paid trial accounts, lower safety limits apply: 30/mailbox/day, 50/account/day, 10 recipients/message, 15 messages/hour. As soon as your first payment clears, full plan limits unlock.

DKIM, SPF, and DMARC alignment

This is where Managed SMTP earns its keep. When you send through our infrastructure:

• DKIM: Every message is signed with dkim._domainkey.yourdomain.com — your domain's actual key. Receivers verifying DKIM see "this signature is valid AND comes from yourdomain.com" — a strong authentication signal.
• SPF: Your SPF record (v=spf1 include:spf.trekmail.net -all) authorises our outbound IPs. Receivers verifying SPF see "this IP is allowed to send for yourdomain.com" — another strong signal.
• DMARC: With both SPF and DKIM passing, DMARC (your _dmarc TXT record) accepts the message. If you've set a strict DMARC policy (p=quarantine or p=reject), only properly-aligned messages get through — Managed SMTP achieves alignment automatically.

Why this matters: a third-party transactional provider that doesn't sign with your domain's DKIM (or whose servers aren't in your SPF) breaks DMARC. The message either gets quarantined or rejected at strict-DMARC receivers, or — at lenient receivers — degrades your reputation. Managed SMTP avoids this by being part of the authentication chain you've already configured.

What we don't do

Managed SMTP is for transactional and conversational email — replies, mailbox-user activity, normal business correspondence. It is NOT a marketing-email or bulk-marketing platform.

Specifically:

• No campaign tracking (opens, clicks, A/B testing, dashboards). If you need that, look at Mailgun / SendGrid / Postmark or other providers and route through Custom SMTP.
• No unsubscribe-link management. TrekMail's webmail and mailables include a default unsubscribe link for non-mandatory categories; bulk-marketing platforms have more sophisticated list-management built in.
• No marketing-acquisition list scrubbing. If you have a bought list, no SMTP platform will save you — you need to clean it first via the Email Verifier, then send slowly to engaged contacts.

Common errors and fixes

For full diagnostic flow: I Can't Send Emails.

Switching a domain to Managed SMTP from Custom SMTP

SMTP is set per domain, so you switch back one domain at a time:

1. Open Domains → choose the domain → SMTP.
2. Select the {Brand} SMTP radio (managed sending).
3. The change takes effect on the next outbound message from that domain.

If you want every domain on managed SMTP at once, select {Brand} SMTP on any domain and use the Apply to all domains button shown under the route — it switches every domain in the account to that route after a confirmation. To make managed SMTP the route new domains start on, flip the Make this the account default toggle.

Your existing emails (in Sent folder, archives, etc.) aren't affected — only outbound from now on uses the new path.