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

# Email and SMTP

> How customer emails are branded, and how to send them from your own domain.

<Frame caption="Email — your own SMTP, with a required test before it goes live.">
  ![The Email screen with SMTP host, port, credentials and test controls](https://app.gfxtoolz.ai/docs-assets/reseller/email.png)
</Frame>

Your customers receive email from your panel — invitations, password resets and account notices. Those emails carry **your** brand whether or not you configure anything here.

## What happens with no setup

Emails to your customers are automatically rebranded: your business name replaces GFXToolz, and links point to your domain rather than ours.

<Note>
  A customer who gets a password-reset email from your panel is sent to **your** sign-in page, never to a GFXToolz one. This works out of the box.
</Note>

The one thing you cannot change without SMTP is the **sending address** — the technical `from` header.

## Sending from your own domain

<ParamField path="Host" type="required">
  Your provider's SMTP server, e.g. `smtp.yourprovider.com`.
</ParamField>

<ParamField path="Port" type="required">
  Usually **587** with STARTTLS, or **465** for implicit TLS.
</ParamField>

<ParamField path="Secure" type="toggle">
  On for 465. Off for 587, where the connection is upgraded after connecting.
</ParamField>

<ParamField path="Username" type="required">
  Usually the full mailbox address.
</ParamField>

<ParamField path="Password" type="required">
  Your SMTP or app password. **Write-only** — once saved it is never shown again, not even to you. Leave it blank when editing other fields to keep the stored one.
</ParamField>

<ParamField path="From email" type="required">
  The address customers see, e.g. `support@yourbrand.com`. It should be on a domain you control and match the account you authenticate with.
</ParamField>

<ParamField path="From name" type="optional">
  The display name beside the address — usually your business name.
</ParamField>

## Test before it goes live

There is a **send test email** action, and it is not optional in practice: SMTP will not be used for real customer mail until a test has passed.

<Steps>
  <Step title="Save your settings" />

  <Step title="Send a test to an address you can check" />

  <Step title="Confirm it arrives — check the spam folder too" />

  <Step title="Enable it" />
</Steps>

<Warning>
  Enabling untested SMTP is the fastest way to silently stop every customer email. If invitations and password resets stop arriving, check here first.
</Warning>

## Landing in the inbox

Correct credentials get mail *sent*. Correct DNS gets it *delivered*.

<AccordionGroup>
  <Accordion title="SPF">
    Authorises your provider to send for your domain. Your mail host gives you the record.
  </Accordion>

  <Accordion title="DKIM">
    Signs your mail so receivers can verify it was not tampered with.
  </Accordion>

  <Accordion title="DMARC">
    Tells receivers what to do when SPF or DKIM fail. Start with a monitoring policy.
  </Accordion>
</AccordionGroup>

<Tip>
  Use a real mail provider — Google Workspace, Zoho, Brevo, Mailgun, Postmark. Sending from a self-hosted server on a fresh IP usually means the spam folder.
</Tip>

## Choosing a from address

<CardGroup cols={2}>
  <Card title="Good" icon="circle-check">
    `support@yourbrand.com`

    `hello@yourbrand.com`
  </Card>

  <Card title="Avoid" icon="circle-xmark">
    `noreply@` — customers do reply, and you want to receive it.

    A free Gmail or Yahoo address — fails authentication and looks unprofessional.
  </Card>
</CardGroup>

## If you would rather not bother

Skipping SMTP is perfectly reasonable. Emails still go out, still carry your branding and still link to your domain — only the technical sending address is ours.

Many resellers never configure SMTP, because they deliver temporary passwords over WhatsApp and barely use email at all. See [Users](/panel/users).