Guides

# SMTP & IMAP Setup

Every Mission Inbox mailbox exposes standard SMTP and IMAP endpoints. Use them to send email from any language or tool that supports mail protocols, or to read incoming mail programmatically.

## Overview

SMTP

`cube1.missioninbox.com`port **465**SSL/TLS

Send outbound email from any SMTP-capable client or library.

IMAP

`cube1.missioninbox.com`port **993**SSL/TLS

Read and manage incoming mail — replies, bounces, warmup traffic.

SMTP via Mission Inbox uses the same mailbox that powers warmup and health checks, and sending through it counts toward your send statistics.

## Step 1 — Find Your Host & Credentials

The **cube host** is the single entry point for all SMTP and IMAP connections in your product. Every mailbox shares the same host — visible in the sidebar of this portal under the product selector (labelled "SMTP / IMAP Host").

| Credential | Value                                                                                |
| ---------- | ------------------------------------------------------------------------------------ |
| Host       | Entry point for SMTP and IMAP — cube1.missioninbox.com                               |
| Username   | Full mailbox email address (e.g. sender@yourdomain.com)                              |
| Password   | Returned in the create response and always retrievable via GET /api/mailboxes/:email |

To retrieve a mailbox's credentials at any time, call `GET /api/mailboxes/:email`. The response always includes the `password` field in plain text along with the full mailbox details.

cURL

```bash
curl "https://api.v4.missioninbox.com/api/mailboxes/sender@yourdomain.com" \
  -H "X-Server-API-Key: miacme_4eC8vKmN2pQrStUwXyZaB6dEfGhIjLoPqRsT9uVwX1b"
```

Response

```json
{
  "email": "sender@yourdomain.com",
  "fullName": "John Doe",
  "password": "SecurePassword123!",
  "domainName": "yourdomain.com",
  "isWarmupActive": true,
  "warmedDays": 14,
  "sent": 142,
  "createdAt": "2026-02-20T10:00:00.000Z"
}
```

If you need to change the password, update it via `PATCH /api/mailboxes/:email` with a `password` field. The new password takes effect immediately for both SMTP and IMAP.

## Step 2 — Configure SMTP

Use the settings below in any SMTP-capable client or library. Port 465 uses implicit SSL/TLS — the connection is encrypted from the first byte. Do not use STARTTLS (port 587) as it is not supported.

| Setting    | Value                                           |
| ---------- | ----------------------------------------------- |
| Host       | cube1.missioninbox.com                          |
| Port       | 465                                             |
| Encryption | SSL/TLS (implicit)                              |
| Username   | Full mailbox email address                      |
| Password   | Mailbox password (set at creation or via PATCH) |

## Step 3 — Configure IMAP

IMAP gives read access to the mailbox — use it to fetch replies, warmup responses, or any inbound mail delivered to the MX record on your domain.

| Setting    | Value                                           |
| ---------- | ----------------------------------------------- |
| Host       | cube1.missioninbox.com                          |
| Port       | 993                                             |
| Encryption | SSL/TLS                                         |
| Username   | Full mailbox email address                      |
| Password   | Mailbox password (set at creation or via PATCH) |

## Code Examples

Node.js — send via Nodemailer

JavaScript

```javascript
import nodemailer from 'nodemailer';

const transporter = nodemailer.createTransport({
  host: 'cube1.missioninbox.com',   // your product's SMTP/IMAP host (see sidebar)
  port: 465,
  secure: true, // SSL/TLS on port 465
  auth: {
    user: 'sender@yourdomain.com',  // full mailbox email address
    pass: 'your_mailbox_password',  // set at creation or via PATCH
  },
});

await transporter.sendMail({
  from: '"Your Company" <sender@yourdomain.com>',
  to: 'recipient@example.com',
  subject: 'Hello from Mission Inbox',
  text: 'Sent via SMTP.',
  html: '<p>Sent via SMTP.</p>',
});
```

Node.js — read via IMAP

JavaScript

```javascript
import Imap from 'imap';

const imap = new Imap({
  user:     'sender@yourdomain.com',
  password: 'your_mailbox_password',
  host:     'cube1.missioninbox.com',  // your product's cube host (see sidebar)
  port:     993,
  tls:      true,
});

imap.once('ready', () => {
  imap.openBox('INBOX', true, (err, box) => {
    console.log(`${box.messages.total} messages in INBOX`);
    imap.end();
  });
});

imap.connect();
```

Python — send via smtplib

Python

```text
import smtplib
from email.mime.text import MIMEText
from email.mime.multipart import MIMEMultipart

msg = MIMEMultipart('alternative')
msg['Subject'] = 'Hello from Mission Inbox'
msg['From']    = 'sender@yourdomain.com'
msg['To']      = 'recipient@example.com'
msg.attach(MIMEText('Sent via SMTP.', 'plain'))
msg.attach(MIMEText('<p>Sent via SMTP.</p>', 'html'))

# host = your product's cube host (shown in the sidebar of this portal)
with smtplib.SMTP_SSL('cube1.missioninbox.com', 465) as server:
    server.login('sender@yourdomain.com', 'your_mailbox_password')
    server.sendmail('sender@yourdomain.com', 'recipient@example.com', msg.as_string())
```

Python — read via imaplib

Python

```text
import imaplib

mail = imaplib.IMAP4_SSL('cube1.missioninbox.com', 993)
mail.login('sender@yourdomain.com', 'your_mailbox_password')

mail.select('INBOX')
status, messages = mail.search(None, 'ALL')
mail.logout()
```

## Troubleshooting

Connection refused on port 465

Make sure your client is configured for implicit SSL/TLS, not STARTTLS. Libraries like Nodemailer require secure: true when using port 465.

Authentication failed

Verify the username is the full email address (e.g. sender@yourdomain.com), not just the local part. Confirm the password is the one set during mailbox creation or via PATCH /api/mailboxes/:email.

Email delivered but not appearing in analytics

SMTP sends are tracked asynchronously. Allow a few seconds after sending before checking analytics or message status via the API.

IMAP returns empty inbox

The IMAP inbox only contains inbound mail — replies and warmup responses from other servers. Outbound sent mail is not stored in IMAP folders.

Reply-To header missing from sent mail

Outgoing mail never carries a Reply-To header; it is removed even when your client sets one, because it hurts deliverability. Replies come back to the sending mailbox. To also receive them at another address, set “Forward replies to” on the mailbox.

Firewall blocking outbound port 465

Some hosting environments block outbound port 465\. Ask your infrastructure provider to allow it — 465 with implicit SSL/TLS is the only supported SMTP port, so there is no alternative port to fall back to. Contact support if it cannot be unblocked.

[PreviousSend Your First Email](https://doc.v4.missioninbox.com/sales/guides/send-first-email.md)[NextWarming Up Mailboxes](https://doc.v4.missioninbox.com/sales/guides/warmup.md)
