Connecting your sequencer
Once a domain is active and has a mailbox, connect that mailbox to your sequencer with an SMTP/IMAP password generated from the domain page.
Set a password
Open the domain’s page and find the mailbox under Mailboxes. Click Set password.

Click Generate password. The password is shown to you exactly once, right there in the dialog.

Warning
Save this password now. It is not stored anywhere and will not be shown again. If you lose it, generate a new one — doing so replaces the old password, so update your sequencer with the new one too.
Connection details
Each mailbox has its own credentials, scoped to its own domain:
| Setting | Value |
|---|---|
| SMTP host | smtp.<your-domain> |
| SMTP port | 587 with STARTTLS, or 465 with TLS |
| IMAP host | imap.<your-domain> |
| IMAP port | 993 |
| Username | The full mailbox address (e.g. sarah@getacme.com) |
| Password | The password you just generated |
Use the Copy button next to each field to copy it directly.
Adding the account to your sequencer
The exact steps vary by sequencer, but the general flow is the same in most tools:
- In your sequencer, find the option to add a new sending account or connect a mailbox via SMTP/IMAP (rather than connecting a mailbox provider like Google or Microsoft directly).
- Enter the SMTP host and port, then the username and password from above. Choose STARTTLS if you’re using port 587, or TLS if you’re using port 465.
- Enter the IMAP host and port (993) with the same username and password, so your sequencer can check for replies.
- Save and test the connection. Your sequencer should confirm it can send and receive through the mailbox.
Sending from an email client like Outlook
You can also connect a mailbox to an ordinary email client, such as Outlook or Apple Mail, and send hand-written emails from it. Add it as an IMAP account using the same connection details above. Sending, your Sent folder and replies all work as they would with any other email account.
Two things work differently from a typical email account, because Outbound applies the same sending checks to every message, whichever app sends it:
- Every recipient is validated before the first email to them goes out. If Truelist hasn’t checked an address yet, it starts checking it and temporarily refuses the message with “validating recipient, retry shortly”. A sequencer retries automatically. An email client usually shows you a send error instead.
- Everything counts toward the mailbox’s daily cap, including replies, CC and BCC recipients, and emails to colleagues. See The sending ramp.
Recommended workflow: verify first, then write
- Before you write to new prospects, verify their addresses in Truelist: use Verify Email for one address, or Verify List to upload a CSV of the prospects you plan to contact. Use the same Truelist account that has your Outbound plan. Each check uses a validation credit, and your plan includes 5,000 a month.
- Write only to addresses that come back ok or risky (risky includes accept-all and role addresses). Outbound refuses invalid addresses, and addresses Truelist couldn’t verify, so verifying first tells you before you spend time on the email.
- Send from your email client as usual. Addresses verified this way go out on the first try.
- If you write to an address you didn’t verify first and your email client shows the “validating recipient, retry shortly” error, send it again after a minute or so. Some mail servers take longer to check.
Note
Verification results last 60 days. After that, the next email to that address is checked again, so a follow-up sent long after you verified a prospect may be refused temporarily once.
Reply-To
Truelist has no Reply-To setting of its own, and it never sees or changes message headers — sending policy is applied before a message body exists. Set Reply-To in your sequencer if you want replies to go somewhere other than the sending mailbox. If you leave it unset, replies land in the sending mailbox itself, which your sequencer can collect over the IMAP connection above.
Set your sequencer’s daily limit
Set your sequencer’s daily sending limit for this mailbox at or below the mailbox’s current cap. See The sending ramp for the schedule and how to read the current cap.
Note
Caps are enforced on our end, not your sequencer’s. If your sequencer tries to send past the mailbox’s current daily cap, those sends are refused with a temporary error until the cap resets at midnight UTC. Keeping your sequencer’s limit at or below the cap avoids wasted sends and retry noise.