IMAP & SMTP Settings for All Clients
Find TrekMail incoming and outgoing server names, secure ports, login details, and connection limits for any email app.
Article details
Type, difficulty, plans, and last updated info.
▼
Article details
Type, difficulty, plans, and last updated info.
- Type
- Guide
- Difficulty
- Beginner
- Plans
- Nano · Starter · Pro · Agency
- Last updated
- Sep 9, 2026
The easiest option is Apps & devices, which gives you guided steps and the exact server names for the selected mailbox. Use the reference below when an app asks you to enter the details manually.
Who this is for
- Users configuring a desktop or mobile email client.
- Developers configuring a script to send email.
1. Incoming Mail (IMAP)
Use these settings to receive email.
| Setting | Value |
|---|---|
| Server Hostname | Copy the incoming hostname from Apps & devices. The platform default is imap.trekmail.net. |
| Port | 993 |
| Encryption/Security | SSL or SSL/TLS |
| Username | Your full email address (e.g., alice@example.com) |
| Password | An app password, or the mailbox password if the mailbox still accepts it (see Passwords and app passwords below) |
Note: TrekMail does not support POP3. Use IMAP to keep folders and message state synchronized across devices.
2. Outgoing Mail (SMTP)
Use these settings to send email.
| Setting | Value |
|---|---|
| Server Hostname | Copy the outgoing hostname from Apps & devices. The platform default is smtp.trekmail.net. |
| Port | 465 (Recommended) or 587 |
| Encryption | SSL/TLS (for 465) or STARTTLS (for 587) |
| Username | Your full email address |
| Password | An app password, or the mailbox password if the mailbox still accepts it (see Passwords and app passwords below) |
| Authentication | Required ("Password" or "Normal") |
A verified White Label setup can show branded IMAP and SMTP hosts. Use those values when they appear; do not replace them with a hostname guessed from the mailbox address. Port 587 with STARTTLS is the supported SMTP alternative when port 465 is blocked.
IMAP Connection Limits
To ensure fair resource usage and server stability, TrekMail enforces concurrent IMAP connection limits based on your subscription plan.
| Plan | Connections per IP | Total Connections |
|---|---|---|
| Nano | 10 | 15 |
| Starter | 25 | 40 |
| Pro | 50 | 80 |
| Agency | 100 | 150 |
- Per IP: Maximum simultaneous connections from a single IP address (e.g., your home network).
- Total: Maximum simultaneous connections across all devices and locations.
What happens if I exceed the limit?
Your email client will receive a "Maximum connections exceeded" error and won't be able to establish new IMAP connections until existing ones are closed.
Tips to avoid connection limits
- Close unused email clients: If you have multiple devices, close email apps you're not actively using.
- Check client settings: Some email clients open excessive connections. Configure them to use fewer simultaneous connections.
- Upgrade if needed: If you regularly hit the limit with normal usage, consider upgrading to a higher plan.
CalDAV / CardDAV (calendar and contacts)
In addition to IMAP/SMTP for mail, TrekMail exposes calendar and contacts over CalDAV/CardDAV. This is what your phone or desktop calendar app uses to sync events and contacts.
| Setting | Value |
|---|---|
| Server / Base URL | Standard service: https://trekmail.net/dav/. Use a branded DAV address only when your provider has supplied and verified it. |
| Discovery | Auto-detected by Apple Calendar, iOS, Android (DAVx⁵), Thunderbird via .well-known/caldav and .well-known/carddav |
| Username | Full email address (e.g. alice@yourdomain.com) |
| Password | An app password, or the mailbox password if the mailbox still accepts it; you can create a separate app password for calendar and contacts sync |
| Encryption | HTTPS, required, no plain HTTP |
| Authentication | HTTP Basic |
For platform-specific guides see: Apple · iPhone/iPad · Android · Thunderbird · Outlook (caveats).
Passwords and app passwords
Each regular mailbox has one of two sign-in modes for mail apps, including calendars and contacts. Apps & devices shows which one applies to the selected mailbox. Shared mailboxes have no app passwords or mode; members open them with their own mailbox credentials.
| Mode | What an email app can use |
|---|---|
| App passwords only | An app password. The mailbox password is refused by mail apps but still works in webmail. |
| Mailbox password or app passwords | Either the mailbox password or an app password. Existing mailboxes keep this mode at rollout. |
New mailboxes follow Account settings > New mailboxes > Mail apps need app passwords, which is on by default. Changing it never switches existing mailboxes. When creating a single mailbox in the dashboard, Mail apps sign in with lets you choose differently.
- Where to create one: in webmail under Settings > App passwords, or in the dashboard under Mailboxes > your mailbox > Security > App passwords (anyone allowed to set the mailbox password can do this). In Apps & devices, a mailbox that needs an app password also shows a Create an app password link.
- What it looks like: 16 letters, shown only once and grouped in four blocks of four. Spaces and capital letters do not matter. A mailbox can have up to 25 active app passwords, so give each device its own.
- Where it works: IMAP, SMTP on ports 465 and 587, ManageSieve, and CalDAV/CardDAV. It never opens the new webmail or the dashboard. New webmail uses the mailbox password, plus a code if two-factor authentication is on. Classic webmail uses an app password for App passwords only mailboxes. Two-factor authentication protects webmail sign-in only; mail apps and classic webmail never ask for a code.
- If the app shows this error: "Sign-in failed. This mailbox accepts app passwords only: create one in webmail under Settings > App passwords." The mailbox refused its mailbox password. Create an app password and enter it in the app instead. Some apps only report a generic password failure, so check the mode in Apps & devices too.
- When app passwords stop working: Replace ends the old secret immediately; Revoke stops that password. An account admin setting a new mailbox password in the dashboard, API, or an AI agent revokes all app passwords. A user's own password change in webmail keeps them unless they select Also revoke all app passwords (off by default). Password reset or recovery, sign-in suspension, conversion to a shared mailbox, and moving to Recently deleted revoke all of them. Restoring a mailbox does not restore its app passwords. A device whose app password was replaced or revoked needs a new one.
For the full guide, see Mail app passwords.
Important Notes
- Username: Always use the full email address. Just
alicewill fail. - Passwords: Use an app password or the mailbox password, as described above, never your TrekMail account password for the dashboard.
- Custom SMTP routing: If your plan does not include managed sending, configure your provider under the domain's SMTP settings first. Your email app still connects to the outgoing TrekMail or branded host shown in Apps & devices with the same password it uses for IMAP. TrekMail applies the private provider route behind the scenes; do not place the provider's secret credentials in an end user's email app.
Related articles
Jump to nearby guides that continue the workflow.