https://trekmail.net/?utm_source=facebook_page&utm_medium=main_link&utm_campaign=FB, https://www.linkedin.com/company/tr

TrekMail, 1207 Delaware Avenue, #2058, Wilmington, DE (2026)

06/20/2026

TrekMail Update: Late June 2026
Another strong update is live.

🌍 13 languages across the product
TrekMail is now localized across the dashboard, public pages, login, registration, 2FA, marketing pages, and webmail.
Supported languages include English, German, French, Spanish, Italian, Portuguese, Dutch, Russian, Japanese, Korean, Chinese, Arabic, and Hebrew.
Language is detected automatically, can be changed in settings, and is remembered on your account.
Arabic and Hebrew also get full right-to-left layout support.

🎨 Per-domain White Label branding
White Label is now much more flexible.
Each domain can have its own logo, colors, sender identity, and branded experience.
That means agencies and resellers can manage different customer brands from one TrekMail account without everything looking the same.
We also added a new Branding tab with live preview, DNS checks, and light/dark logo support.

💳 Plans page redesign
The Plans page was rebuilt with cleaner pricing cards, clearer comparison, localized pricing, and the foundation for a new Dedicated IP add-on.

↪️ Safer forwarding setup
Forwarding got a small but important redesign.
Saved forwarding destinations are now shown as a read-only list with explicit edit and delete actions.
That means password managers can no longer accidentally overwrite a forwarding address.

🔐 Security and data protection
We shipped another broad security pass.
Password reset is safer, tokens are invalidated properly after password changes, exports are better protected, sensitive diagnostics are redacted, and ownership checks were tightened across contacts, calendars, Drive sharing, tickets, tokens, and bulk previews.
Thanks again to the researchers who reported issues responsibly through our Security Hall of Fame program.

🛠️ More reliability
TrekMail now does more self-healing in the background.
Sending state is reconciled automatically, stale domains get a longer warning window, special folders are repaired daily, Drive uploads and sharing are steadier, migrations resume more safely, and billing/currency edge cases were cleaned up.

🌐 White Label, docs, and policies
We refreshed the White Label landing page, updated public policies, improved affiliate materials, and clarified docs around Calendar, Contacts, shared mailboxes, per-domain SMTP, trusted devices, and Dedicated IP.

Overall, this update makes TrekMail more global, more brandable, safer, and more reliable.

06/19/2026

There's a DNS record called TLS-RPT. Almost nobody sets it up. Almost nobody reads it.

Here's what it does: when a server tries to deliver email to your domain and the TLS connection fails, TLS-RPT tells the sending server where to send a failure report.

Without it, encrypted delivery can fail silently. Your domain says "use TLS" but the connection breaks, and nobody on your side knows.

Setting it up takes one DNS TXT record:

_smtp._tls.yourdomain.com
v=TLSRPTv1; rua=mailto:[email protected]

That's it. Now when TLS delivery to your domain fails, you get a report explaining why.

Most businesses skip this because it isn't required. But if you care about whether your email actually arrives encrypted, it's the only way to know.

Have you set up TLS-RPT on your domain?

This sounds obvious but most people get it backwards.you@yourdomain.com is YOUR address. It lives in YOUR DNS. It goes w...

06/17/2026

This sounds obvious but most people get it backwards.

[email protected] is YOUR address. It lives in YOUR DNS. It goes wherever YOU point it.

The provider is just the host — the server that stores and sends. Like a building your office rents. You can move offices without changing your business name.

When your MX records point to Provider A and you want to switch to Provider B:

1. Set up mailboxes on Provider B.
2. Change MX records in your DNS.
3. Import old messages via IMAP.

Your address stays the same. Your clients notice nothing. The provider changed, the identity didn't.

This only works with your own domain. If your email is .com or .com, you don't own the address. They do.

Do your team members use company domain email, or are some still on free accounts?

06/14/2026

TrekMail Update - Mid-June 2026

This update continues the June release with two major new features - Shared Mailboxes and Per-Domain SMTP — plus another large round of reliability, security, webmail, billing, Drive, API, and white-label improvements.

👥 Shared Mailboxes
Shared mailboxes are now live.
Teams can now use addresses like support@, sales@, billing@, or info@ without turning them into separate personal accounts.
A shared mailbox can be created directly, or an existing mailbox can be converted into a shared one. Team members can be added with access to read and, when allowed, send from that mailbox.
In webmail, shared mailboxes now appear in the mailbox switcher, with a clear active-mailbox banner so users always know which mailbox they are working in. Reading, replying, sending, attachments, calendar, contacts, and mailbox Drive all follow the selected mailbox context.
Shared mailboxes also have cleaner management inside the dashboard, including access controls, shared badges, better warnings, unread indicators, and safer handling when a shared mailbox has no members.

⚙️ Per-Domain SMTP
TrekMail now supports SMTP routing per domain.
This means each domain can use its own SMTP connection instead of forcing the whole account to use one global sending route.
For agencies, resellers, and multi-brand setups, this opens much more flexible sending workflows. One account can now manage multiple domains while keeping sending routes separate where needed.
There is also an account-level default SMTP route, so domains can either use their own route or simply inherit the account default.
The old SMTP setup has been cleaned up, the interface is clearer, and domain-level sending settings are easier to understand and manage.

🖼️ Sender Avatars and Profile Photos
Webmail now supports sender avatars using Gravatar.
Profile photo setup is also easier: users can click the avatar area directly, with a cleaner hover state and a small shortcut in Settings.
This makes the webmail experience feel more personal and easier to scan, especially in busy inboxes.

📬 Mailboxes
The rebuilt mailboxes page received another large polish pass.
Mobile views are cleaner, grouped and flat views behave better, bulk actions are easier to use, and mailbox notes now feel more natural with inline editing.
Pending invitations are clearer, shared mailbox actions are easier to find, and guided tours were simplified so new users can understand the page faster.
Bulk invites also improved. Users can now work with mixed-domain batches more comfortably, set a default domain, or specify domains line by line.

🔀 Forwarding and Routing
Forwarding is now safer and more reliable.
TrekMail handles external catch-all forwarding more cleanly, catches risky routing setups earlier, and has stronger protection against forwarding loops and invalid destinations.
This helps prevent confusing delivery issues before they happen.

🗂️ Drive and Sync
Drive received another reliability pass.
Uploads, device handling, WebDAV behavior, trash cleanup, quota tracking, sharing, storage add-on billing, and background cleanup jobs were all tightened.
The result is a more predictable Drive experience, especially for larger accounts and accounts using extra storage.

🤖 API, MCP, and AI Agents
API and MCP coverage continued to expand.
Shared mailboxes, per-domain SMTP, account-default SMTP routing, and improved bulk invites are now better covered across automation workflows.
The API and MCP tool counts were also cleaned up across the product so documentation and interface numbers stay consistent.
AI agents now have a stronger foundation for working with mailboxes, shared mailboxes, Drive, verification, sending, and account workflows more safely.

🔐 Security Hardening
Another large security pass landed across TrekMail.
We tightened 2FA flows, recovery codes, mailbox resets, reCAPTCHA, OAuth login flows, CSV exports, unsubscribe links, internal support access, API access, file handling, disposable-domain checks, and several edge cases around account security.
A lot of this work is invisible when everything works correctly - which is exactly the point.

💳 Billing and Platform Reliability
Billing, trials, promo codes, crypto payments, affiliate tracking, backups, subscription migration, grace periods, past-due handling, and background jobs all received reliability improvements.
We also improved safeguards around stuck trials, failed invoices, storage add-ons, webhook retries, currency conversion, and deployment alerts.
This should reduce edge cases, billing confusion, and manual cleanup.

📨 Webmail
Webmail received another round of fixes and polish.
Spam training works better, draft dates are more reliable, menu labels and translations were cleaned up, mobile and RTL behavior improved, and compose windows behave more safely when switching mailbox context.
Shared mailboxes also now behave correctly in webmail, including sending, replying, reading, attachments, unread counts, and active-context switching.

🏷️ White-label
White-label tenants now get a more consistent branded experience.
Guided tours work better for white-label customers, brand colors apply more consistently across forms and focus states, dark mode follows branding more cleanly, and white-label DNS validation was improved.

🚀 Platform
Across the product, TrekMail received hundreds of smaller fixes and improvements covering onboarding, domains, mailboxes, SMTP, Drive, webmail, billing, security, API, MCP, documentation, landing pages, partner pages, analytics, and background reliability.

The result: fewer confusing states, fewer edge cases, better team workflows, stronger sending flexibility, and a more consistent product overall.

06/12/2026

Here's the thing about spam folders: they're silent.

Your email gets delivered. Technically. It arrives at the recipient's server. No bounce, no error, no notification.

But the recipient never sees it. It sits in a folder they check once a month, if ever.

You keep sending. You assume everything's fine because nothing bounced. Weeks later a client says "I never got your invoice." By then your domain reputation has been quietly degrading.

The fix starts with monitoring, not guessing:

- DMARC reports tell you who's sending as your domain and whether authentication passes.
- TLS-RPT reports tell you when encrypted delivery fails.
- Bounce logs tell you which addresses are dead.

None of this requires expensive tools. It requires setting up the DNS records and actually reading what comes back.

When was the last time you checked where your emails actually land?

06/10/2026

Most email providers tie your mailbox and your sending together. Same server reads your mail and sends it.

That works until it doesn't.

When your sending volume grows, when you need dedicated IP reputation, or when compliance requires a specific sending provider — the bundled model breaks.

BYO SMTP (Bring Your Own) separates the two layers. Your mailbox stays where it is. Your sending goes through AWS SES, SendGrid, Mailgun, or whatever you choose.

Why this matters:
- Your sending reputation is yours, not shared with thousands of other users.
- You control rate limits, warm-up, and bounce handling.
- You can switch sending providers without touching mailboxes.

TrekMail supports BYO SMTP on every plan, including the free one.

Do you control your own sending infrastructure, or does your provider?

06/09/2026

TrekMail Update — June 2026

Big update this time.
Over the last stretch, we shipped a large round of improvements across domain management, mailboxes, Drive, Webmail, forwarding, billing, security, white-label, API, MCP, and the affiliate platform.
The main goal was simple: make TrekMail cleaner, safer, faster, and easier to use every day.

🌐 Domain Settings redesign
Domain management got a full redesign.
The page is now cleaner, easier to understand, and much better on mobile.
Adding domains is smoother, bulk setup is clearer, DNS errors are more human, and Cloudflare setup now gives a much better step-by-step flow with previews, conflict handling, and clearer choices before anything changes.
We also added better setup guides for popular email apps, improved DNS status messages, and made domain deletion safer with a proper impact dialog.

📬 Mailboxes redesign
The mailboxes page was rebuilt too.
It now feels much more consistent with the rest of the dashboard, works better on smaller screens, and handles mailbox notes, pending invitations, bulk actions, and grouped views more cleanly.
Bulk mailbox creation and bulk invites also got major improvements, including better previews, mixed-domain batches, generated passwords, clearer limits, and stronger validation before anything is created.

⚙️ Mailbox settings improvements
Mailbox settings now have a cleaner layout and a new Security tab.
Users can see 2FA status more clearly, manage storage, reset recovery codes, handle forwarding, filters, aliases, Sieve rules, and mailbox actions from a more polished interface.
White-label brand colors now apply much more consistently across this area too.

🔀 Better forwarding and routing
Forwarding is now stronger and safer.
TrekMail now handles multi-destination forwarding more reliably, includes better loop protection, supports external catch-all forwarding more consistently, and gives clearer validation when something would create a bad routing setup.

🗂️ Drive and sync improvements
Drive got a large reliability pass.
Device and app-password handling is safer, WebDAV behavior is more consistent, uploads are more resilient, quotas are stricter and clearer, sharing is better scoped, trash behavior is cleaner, and the Drive Storage Add-on billing lifecycle is more reliable.
This is not just polish. It is the foundation for Drive becoming a serious file layer inside TrekMail.

🤖 API, MCP, and AI Agents
API and MCP coverage keeps expanding.
The API and MCP account page was redesigned, MCP tooling was updated, and several Drive, invite, verifier, mail, sharing, and security flows were tightened.
AI agents now have a cleaner and safer foundation for managing TrekMail workflows through approved tools.

📈 Affiliate, partner, and promo systems
The affiliate and partner systems got a major cleanup pass.
Attribution is more reliable, partner-network tracking is safer, commission handling is clearer, tax-form flows are stronger, promo code behavior is more consistent, and analytics are more accurate across providers and currencies.

💳 Billing and subscriptions
Billing also got another round of hardening.
Failed-payment recovery, resubscribe flows, invoice handling, crypto payments, tax previews, subscription states, and payment-method changes are now more reliable.
The goal is fewer edge cases and fewer confusing billing states.

🔐 Security hardening
A large security pass landed across the platform.
We tightened 2FA flows, session handling, password reset behavior, recovery codes, CSV exports, OAuth, unsubscribe links, support replies, file handling, redirects, logging, and API/MCP access controls.
We also added more responsible researchers to the TrekMail Security Hall of Fame.

📨 Webmail improvements
Webmail also got a lot of fixes and polish.
Login is faster, folder loading is smoother, calendar and contacts are more reliable, drafts and message formatting behave better, attachment and sharing behavior is cleaner, and several mobile and reading-pane issues were fixed.

🏷️ White-label polish
White-label customers now get a more consistent branded experience.
Brand colors apply better across the dashboard, tours now work for tenants, tenant sitemaps are safer, and white-label Drive and billing areas are more reliable.

📚 Docs and usability
We updated setup guides, improved help content, added more real email-client instructions, and made validation messages across the product softer and easier to understand.

TrekMail keeps getting better.

Cleaner dashboard. Stronger Drive. Better forwarding. Safer AI tools. More reliable billing. Better webmail. Stronger security.

And a lot more consistency across the whole platform.

06/05/2026

Most email travels encrypted. But not all of it.

SMTP was designed in 1982. Encryption was bolted on later with STARTTLS — and it's optional. A man-in-the-middle can strip the encryption silently. Your server tries TLS, gets told "not supported," and falls back to plain text.

MTA-STS (Mail Transfer Agent Strict Transport Security) fixes this. It publishes a policy on your domain that tells sending servers: "Only deliver to me over TLS. If encryption fails, don't deliver at all."

Setting it up requires:
1. A policy file hosted at mta-sts.yourdomain.com
2. A DNS TXT record at _mta-sts.yourdomain.com
3. Optional: a TLS-RPT record for failure reports

It isn't complicated. But almost nobody does it.

Have you checked whether your domain enforces encrypted delivery?

06/03/2026

Quick exercise.

Your agency manages email for 15 client domains. Average 8 mailboxes each. That's 120 mailboxes.

On a per-seat provider at $7/user/month: $840/month. $10,080/year.

On a flat-rate plan: under $25/month. $300/year.

Same IMAP. Same SMTP. Same SPF/DKIM/DMARC. Same clients who never notice the difference.

Per-seat pricing was designed for productivity suites — docs, video calls, calendars, chat. If you only need email, you're subsidizing features your clients will never open.

How much does your current email setup cost per mailbox?

05/29/2026

TrekMail Update — May 2026
A lot shipped over the last few days.

This update is mostly about making TrekMail more powerful, safer, and smoother across Drive, Webmail, Email Verifier, AI agents, forwarding, and domain-level email management.

🔄 Drive Sync foundation
We continued building the foundation for native Drive sync.
TrekMail Drive is moving beyond browser-only storage toward a more flexible sync experience, with device management, app passwords, WebDAV support, and better compatibility with desktop and mobile file clients.

🧪 Email Verifier redesign
Email Verifier got a full interface refresh.
The flow is now clearer, easier to follow, and better structured for both quick checks and deeper verification jobs.
We also improved credit handling, mobile layout, explanations in the UI, and job recovery.
The goal is simple: fewer confusing results, fairer credit usage, and a cleaner verification experience.

🤖 AI agents and MCP improvements
We shipped another round of improvements for AI-agent workflows.
Scheduled email support is stronger, Drive device tools are available through MCP, and the AI Agents page now explains better how TrekMail works with Claude, ChatGPT, Codex, Cursor, and other compatible clients.

📨 Multi-destination forwarding
Forwarding is now much more flexible.
A mailbox can forward incoming mail to multiple destinations instead of just one.
That makes real business workflows easier, like sending messages to a personal inbox, a team inbox, and an external system at the same time.

🖊️ Domain-level signatures
You can now manage email signatures at the domain level.
A company can apply a default or enforced signature across mailboxes on the same domain instead of configuring each mailbox manually.
Useful for teams, agencies, and businesses that want consistent branding in outgoing email.

🔐 Security hardening
We closed a large batch of security reports and strengthened several sensitive areas of the platform.
That includes safer sessions, better protection around password changes and 2FA, stronger file handling, safer unsubscribe links, cleaner redirects, and additional protections for API and MCP tools.
Several responsible researchers were also added to the TrekMail Security Hall of Fame.

🧰 Support and dashboard improvements
We improved support ticket handling, raised the message length limit for longer reports, fixed UI edge cases, and polished branded and white-label environments.

🚀 More reliability across the platform
We also shipped stability work across billing, migrations, Drive, Webmail, Email Verifier, scheduled sending, and domain setup.
Most of this is not something users need to think about.

That is the point.
The product should feel faster, safer, and more predictable.

TrekMail keeps getting better, with stronger Drive sync foundations, cleaner verification tools, more flexible forwarding, domain-level signatures, safer AI automation, and another big round of security improvements.

TrekMail

06/20/2026

06/19/2026

06/17/2026

06/14/2026

06/12/2026

06/10/2026

06/09/2026

06/05/2026

06/03/2026

05/29/2026

Address

Website

Alerts

Shortcuts

Share

Category