# Forward hello@yourdomain.com to the inbox you already use

> Forward domain email like hello@yourdomain.com directly to Gmail using thelastapi forwarding rules, DNS verification, and zero extra subscriptions.

**You can forward email from your custom domain to your Gmail inbox by adding a forwarding rule in thelastapi and setting your domain's MX and CNAME records.** Once configured, any incoming message sent to addresses like `hello@yourcompany.com` routes straight to the inbox you already check every day. When you hit reply in your email client, your message goes straight back to the original sender.

This guide walks you through creating forwarding rules, pointing your DNS records, inspecting forwarding logs, and understanding delivery limits.

## How domain email forwarding works

When someone sends an email to `hello@yourcompany.com`, the mail server responsible for your domain receives the message, inspects it for security risks, and transmits it onward to your personal destination inbox.

When thelastapi forwards a message to your inbox:

- **Sender header:** The incoming message displays as **"Sender Name via thelastapi"** inside Gmail or Outlook.
- **Replies:** When you reply, your client uses the original sender's address (or the `Reply-To` address they specified), so your reply goes straight to them.
- **Content:** The plain text, HTML formatting, and safe attachments all pass through intact.
- **Footers:** A discreet notice at the bottom reads *Forwarded by thelastapi for hello@yourcompany.com · Manage forwarding*.

You do not need to log into a separate webmail dashboard just to check incoming messages. Everything lands in your primary inbox alongside your daily mail. If you later decide you want to send and manage mail directly under your custom domain inside a dedicated dashboard, you can upgrade that address to [a business inbox at your own domain: hello@yourcompany.com](https://thelastapi.dev/blog/business-inbox-own-domain).

## Step 1: Add a forwarding rule

You configure forwarding rules with the `vibiz` CLI or via HTTP requests to the API. You can direct a single address to an external email, or create a catch-all rule that captures everything sent to your domain.

To forward messages sent to `hello@sellshelf.app` to your Gmail account, run:

```bash
vibiz email forward hello@sellshelf.app me@gmail.com
```

If you want any other incoming message on your domain to reach your team, set up a catch-all rule using `*`:

```bash
vibiz email forward '*@sellshelf.app' team@gmail.com
```

You can route an individual domain address to up to 5 destination inboxes. Any incoming mail sent to an address without an explicit rule (and without a catch-all `*` rule) will not be delivered anywhere; it is recorded in the activity log with the outcome `no_rule`.

If you prefer to configure this via HTTP using your account key, send a `PUT` request to the domains forwarding endpoint:

```bash
curl -X PUT https://thelastapi.dev/v1/domains/sellshelf.app/forwarding \
  -H "Authorization: Bearer $VIBIZ_API_KEY" \
  -H 'content-type: application/json' \
  -d '{
    "rules": [
      { "address": "hello", "to": ["me@gmail.com"] },
      { "address": "*", "to": ["team@gmail.com"] }
    ]
  }'
```

### Destination inbox confirmation

Every destination inbox must confirm receipt before forwarding starts. As soon as you add a new destination address, thelastapi sends an email with the subject line "Confirm forwarding to this inbox".

No incoming mail will reach that inbox until the recipient clicks the confirmation button inside that message. If you ever need to remove a rule later, run:

```bash
vibiz email unforward hello@sellshelf.app
```

Running `vibiz email unforward sellshelf.app` without an address removes forwarding for the entire domain.

## Step 2: Configure your DNS records

For email to reach thelastapi so it can be forwarded, your domain's DNS records must point to our mail servers.

If you bought your domain directly through thelastapi using `vibiz domains buy`, these DNS records are written and verified automatically. If your domain is registered elsewhere, you must add four records at your DNS host:

| For | Type | Name | What it does |
| --- | --- | --- | --- |
| Receive | `MX` | `@` | Directs incoming domain mail to the forwarding servers |
| Receive | `CNAME` | `<token1>._domainkey` | Verifies ownership and validates DKIM |
| Receive | `CNAME` | `<token2>._domainkey` | Verifies ownership and validates DKIM |
| Receive | `CNAME` | `<token3>._domainkey` | Verifies ownership and validates DKIM |

To inspect the exact record values your domain needs and check if they are live, run:

```bash
vibiz email forwards sellshelf.app --check
```

You can also trigger a verification lookup over HTTP:

```bash
curl -X POST https://thelastapi.dev/v1/domains/sellshelf.app/forwarding/verify-dns \
  -H "Authorization: Bearer $VIBIZ_API_KEY"
```

The domain status moves from `needs_dns` to `verifying`, and finally to `active` once all four records resolve correctly.

### Handling existing mail providers

If your domain already receives mail through another email provider, its current MX records point there. thelastapi never overwrites or hijacks active mail routing silently.

When you run verification against a domain with existing MX records, you receive a warning that names the current mail servers. Once you update your MX records to point to thelastapi, only the addresses specified in your forwarding rules will receive mail. To confirm that you intend to replace your existing setup, pass the `--replace-mx` flag in the CLI:

```bash
vibiz email forward hello@sellshelf.app me@gmail.com --replace-mx
```

In the API, pass `"replace_mx": true` in your payload or send a request to `POST /v1/inbox/domains/:domain/replace-mx`.

## Step 3: Monitor delivery and view logs

You can monitor incoming traffic and inspect delivery statuses through the CLI or console. The forwarding log stores metadata for every inbound email for 30 days:

```bash
vibiz email forwards sellshelf.app --log
```

To fetch the log over HTTP:

```bash
curl https://thelastapi.dev/v1/domains/sellshelf.app/forwarding/log \
  -H "Authorization: Bearer $VIBIZ_API_KEY"
```

The log records the sender address, destination recipient, subject line, timestamp, and final outcome (such as delivered, dropped, or `no_rule`). To safeguard your privacy, email bodies are never stored in the forwarding log. Stored message files are deleted entirely after 30 days.

## Filtering and delivery limits

Email forwarding includes safeguards to keep your personal Gmail inbox clean and preserve server reputation:

| Rule or condition | Platform behavior |
| --- | --- |
| **Spam and viruses** | Messages identified as spam or carrying viruses are blocked. |
| **Authentication failure** | Mail that fails sender checks whose domain enforces a reject policy is refused. |
| **Executable attachments** | Executable files (`.exe`, `.js`, `.bat`) are stripped. A notice appears in the footer. |
| **Large attachments** | Attachments that cause the forwarded message to exceed 10 MB are dropped. |
| **Forwarding loops** | Messages forwarded 3 times or loops back to the domain itself are halted. |
| **Domain daily ceiling** | Up to 500 forwards per domain per UTC day. The owner gets an email when reached. |
| **Per-sender rate limit** | Up to 30 forwarded messages per sender per hour. |

If a forwarded inbox bounces or reports spam 3 times, forwarding to that destination is disabled automatically. The domain owner receives an alert. To re-enable delivery, address the issue and save the forwarding rule again to re-confirm the inbox.

AI agents working in your project can inspect your forwarding rules, verify DNS, and read the logs using the `vibiz_email_forwarding` tool. Modifying forwarding rules requires owner access. If an agent attempts to alter rules, the API returns an `owner_only` status along with a `console_url` where the owner can review and approve the change.

## When to use forwarding versus sending mail

Forwarding is an efficient way to receive inbound queries at `hello@yourcompany.com` without setting up a full workspace. However, forwarding only handles incoming traffic.

If your web application needs to send messages programmatically—such as confirmation links or purchase receipts—you do not need DNS setup for basic sending. Projects get an address on `<slug>.vibiz.app` right away. You can read more about how this works in [send transactional email from your app without touching DNS](https://thelastapi.dev/blog/send-transactional-email-no-dns).

When your app grows and you want to handle incoming conversations in a team interface, manage custom mailboxes, or dispatch broadcast updates, check the complete [Email documentation](https://thelastapi.dev/docs/email) to review mailbox configuration, marketing rules, and contact lists.

## Next steps

To forward your company domain email to Gmail, buy or connect your domain with `vibiz domains add yourdomain.com`, add your forward with `vibiz email forward hello@yourdomain.com yourname@gmail.com`, and check the confirmation link in your Gmail inbox.

## Frequently asked questions

### Why do forwarded emails say "via thelastapi" in Gmail?

Inbound messages are re-sent to your personal inbox through our mail servers, so modern email clients display the intermediary sender to reflect the forwarding path. When you hit reply, your client still addresses your response to the original sender's email or their specified Reply-To address.

### Can I forward one domain address to more than one Gmail account?

Yes, each address rule supports up to 5 destination inboxes. Every destination address receives a confirmation email from thelastapi and must click the confirmation button before forwarded mail starts arriving.

### What happens if an incoming email exceeds the 10 MB attachment limit?

If an incoming email carries attachments that would cause the total forwarded message size to exceed 10 MB, the attachments are dropped to protect inbox delivery limits. The email text and HTML body are still delivered to your destination inbox.

### What is the difference between an email forwarding rule and an inbox?

An email forwarding rule passes incoming messages straight to an external inbox like Gmail without saving bodies in the console. An inbox stores messages on the platform, lets you read conversations in the console, lets you reply directly as `hello@yourdomain.com`, and allows AI agents to read and respond to messages.

---

Published 2026-11-15 · https://thelastapi.dev/blog/forward-domain-email-to-gmail
