> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sellauth.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Email Settings

> Send your shop's emails from your own domain with a custom SMTP server, and pick a provider that reaches inboxes.

SellAuth emails your customers on its own: delivery emails, invoice confirmations, ticket replies, subscription renewals and the rest. Out of the box those go out through a shared SellAuth sender, and there is nothing to configure.

Connecting your own **SMTP server** changes who they come from. Settings live under [**E-mail Settings**](https://dash.sellauth.com/email/templates), which also holds your email templates.

## Why use your own SMTP

**Emails come from your domain.** `orders@yourshop.com` instead of a shared address, which matters for a brand and for buyers deciding whether a delivery email is genuine.

**Deliverability becomes yours.** On a shared sender you inherit the reputation of everyone else using it. On your own domain, your sending history is your own, for better or worse.

**It unlocks marketing.** [Email marketing](/guides/email-marketing) campaigns can only be sent through your own SMTP server.

In exchange you own the setup: authenticating the domain, watching bounces, and keeping the reputation clean.

Requires a plan that includes SMTP.

## What you need

<Steps>
  <Step title="A domain you control">
    Ideally the one your shop runs on. You need access to its DNS records.
  </Step>

  <Step title="An account with an email provider">
    See the comparison below. Most have a free tier that covers a small shop.
  </Step>

  <Step title="Your domain verified at that provider">
    Providers ask you to add DNS records, usually SPF and DKIM, sometimes DMARC. This proves you are allowed to send as your domain, and mail sent without it lands in spam.
  </Step>

  <Step title="The SMTP details entered in SellAuth">
    Your provider issues these once the domain is verified.
  </Step>
</Steps>

## The settings

| Field | What goes in it |
| - | - |
| **SMTP Hostname** | Your provider's server, such as `mail.example.com` |
| **SMTP Port** | Usually 587 for TLS, or 465 for SSL |
| **SMTP Username** | Issued by your provider, often an address or an API-style key |
| **SMTP Password** | Issued by your provider |
| **SMTP Encryption** | TLS, SSL, or none. Match what your provider documents for the port |
| **Mail From** | The address customers see the email coming from |
| **Name From** | The sender name customers see, usually your shop name |

<Warning>
  **Mail From has to be an address on a domain you verified with the provider.** Sending as a domain you have not authenticated is the single most common reason emails land in spam or are rejected outright.
</Warning>

## Choosing a provider

Any provider offering SMTP credentials works. These four cover most cases:

| Provider | Suits |
| - | - |
| **SMTP2GO** | A straightforward first setup, with a free tier that covers a small shop |
| **Private Email** (Namecheap) | You bought the domain at Namecheap and want mailboxes and sending in one place |
| **Resend** | Clean domain verification and a modern free tier, if you are comfortable with developer tooling |
| **Postmark** | Transactional deliverability above all else, for shops where receipts must arrive |

Not endorsements, and not an exhaustive list. What matters when comparing: does it give you SMTP credentials, does it support domain verification with SPF and DKIM, and what are the sending limits on the tier you would be paying for.

<Note>
  A free Gmail or Outlook mailbox is not a sending provider. Those accounts have low daily limits and are not intended for automated mail, so a shop using one tends to hit the limit partway through the day.
</Note>

## Keeping emails out of spam

**Authenticate the domain properly.** SPF and DKIM at minimum, added exactly as your provider specifies, and DMARC once those work.

**Warm up a new domain.** A domain with no sending history that suddenly sends a thousand campaign emails matches the pattern spam filters look for. Let your delivery emails build a history first.

**Send marketing slowly.** Campaigns have a throttle setting for this. See [Email Marketing](/guides/email-marketing).

## Email templates

The same page holds the templates for every email your shop sends, which you can rewrite in full.

Editing templates requires a plan that includes it, and the syntax, the variables each email receives and the shared layout are documented in [Email Templates](/developers/email-templates).

## Troubleshooting

**Authentication failed.** Username or password wrong, or the provider expects an API key rather than your account login.

**Connection refused or timing out.** Wrong port, or the encryption setting does not match the port. Try 587 with TLS, or 465 with SSL.

**Emails send but land in spam.** The domain is not authenticated, or Mail From is on a different domain than the one you verified.

**Some emails arrive and others do not.** Usually a sending limit on your provider's plan. Check its dashboard for rejected or queued mail.

**Nothing sends at all after configuring.** Clear the settings to fall back to the SellAuth sender while you sort it out, so customers keep receiving their deliveries.

## Next steps

<CardGroup cols={2}>
  <Card title="Email marketing" icon="envelope" href="/guides/email-marketing">
    Campaigns and automations, which need SMTP configured.
  </Card>

  <Card title="Email templates" icon="code" href="/developers/email-templates">
    Rewriting the emails your shop sends.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.