> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/sa-request-a-quote/emails/smtp.md).

# Send from your own address (SMTP)

Send quote emails from your own mail server instead of the app's default sender, using any of the nine supported providers.

By default, quote emails come from the app's own mail service at **<no-reply@samita.io>**. Setting up SMTP sends them from your own address instead — better for deliverability, and better for how your business looks.

The setting is on the **Email notifications** tab of **Advanced settings**, in the **SMTP** section. The app describes it as: "You can use either our default email service or your own by adjusting this setting. The sender email address will be used to send quote notifications to you and your customers."

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fgit-blob-9914b1646712b164a5060b71069bce7f9a88fae6%2Fscreenshot-advanced-settings-email-notifications.png?alt=media" alt="The SMTP section on the Email notifications tab with the provider dropdown set to Use the app&#x27;s default email"><figcaption><p>The <strong>SMTP</strong> dropdown, showing the default setting <strong>Use the app's default email</strong>.</p></figcaption></figure>

One setting covers both emails. Whatever you choose here is used for the notification you receive and for the confirmation your customer receives.

{% hint style="info" %}
SMTP is optional. Everything works without it — emails simply come from the app's default sender. **Custom SMTP mail server** is listed on the **FREE** plan, so it is available whatever you are paying.
{% endhint %}

## Supported providers

Choose one from the **SMTP** dropdown:

<table><thead><tr><th width="270">Option</th><th>When to use it</th></tr></thead><tbody><tr><td><strong>Use the app's default email</strong></td><td>The app sends the emails itself, from <code>no-reply@samita.io</code>.</td></tr><tr><td>Google</td><td>You run your business mail on Google Workspace or Gmail.</td></tr><tr><td>Sendinblue</td><td>You already send marketing mail through Sendinblue.</td></tr><tr><td>SendGrid</td><td>A common choice for transactional email at volume.</td></tr><tr><td>Outlook</td><td>Your business mail is on Microsoft 365 or Outlook.</td></tr><tr><td>Pepipost</td><td>Transactional email provider.</td></tr><tr><td>Amazon SES</td><td>You already have AWS set up.</td></tr><tr><td>Elastic Email</td><td>Transactional email provider.</td></tr><tr><td>Mailgun</td><td>Transactional email provider.</td></tr><tr><td>Zoho</td><td>Your business mail is on Zoho.</td></tr></tbody></table>

{% hint style="success" %}
If you have no preference, pick whichever provider already hosts your business mail. Sending from a domain you actually own is what improves deliverability.
{% endhint %}

{% hint style="info" %}
If you have read elsewhere that the app handles only Google and Outlook, that is out of date. Every provider in the list above is selectable from the **SMTP** dropdown in the app today.
{% endhint %}

## Set it up

{% stepper %}
{% step %}

### Collect the details from your provider

Every provider publishes the connection details for sending mail through it — typically a server address, a port, a username and a password, plus the address you want quote emails to come from. Find them in your provider's own documentation and have them to hand before you start.

Gather them first, so you are not hunting for a missing detail halfway through.

Using Google? [Google, field by field](#google-field-by-field) below gives the host and port to type, says which field each value goes in, and walks through creating the app password you will need.
{% endstep %}

{% step %}

### Open the SMTP section

In the app, go to **Advanced settings** > **Email notifications** and find **SMTP**.
{% endstep %}

{% step %}

### Choose your provider

Pick your provider from the dropdown, replacing **Use the app's default email**.

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fgit-blob-7fa27b8e9f74a791f989abbd732ab9a304a86c98%2FScreenshot%202026-09-29%20at%2016-53-44.png?alt=media" alt="The Email notifications tab of Advanced settings showing the SMTP fields the app asks for"><figcaption><p>Your own SMTP server is optional — leave it blank and the app sends for you.</p></figcaption></figure>
{% endstep %}

{% step %}

### Enter the connection details

Enter the information for your own SMTP in the fields, exactly as your provider gives it — copy and paste rather than retype, because a single wrong character stops everything.

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fgit-blob-51609ba988f8c179cf73f6f6bec460c4ca34ced3%2FScreenshot%202026-10-01%20at%2000-09-36.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Save

Click **Save** to update the changes, before you go on to test.
{% endstep %}

{% step %}

### Send a test

The SMTP section has its own **Send a test email** control. Use it first — it checks the connection without involving your storefront at all. The app allows **up to 5 test emails a day**, so treat them as a check rather than a way to preview wording.

Then submit a test quote request from your storefront and confirm the email arrives from your own address, not the app's.

Check both emails while you are there: the one that reaches you, and the confirmation that reaches the customer. This single setting sends both.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Most providers will not accept your ordinary mailbox password from a third-party app. Google in particular requires two-step verification to be switched on and an app-specific password generated from your Google account security settings — [Google, field by field](#google-field-by-field) below walks through it. Never enter the password you use to sign in to your email account.
{% endhint %}

## Google, field by field

Google is the provider most merchants pick, so here is the whole thing end to end. Google will not accept your ordinary Gmail password from another app, so the account work comes first.

{% stepper %}
{% step %}

### Log into your Google account

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fgit-blob-d7c8064a8c298bf13163f2ac33f9fdd7ba3d6d02%2Fscreenshot-google-sign-in.png?alt=media" alt="Google&#x27;s sign-in page with the email field filled and an arrow pointing to Next"><figcaption><p>Start signed in to the account that will send your mail.</p></figcaption></figure>

Sign in at [myaccount.google.com](https://myaccount.google.com/).
{% endstep %}

{% step %}

### Turn on 2-Step Verification

So that your Google account stays protected while it is used for SMTP, enable the 2-step verification Google offers. Google's own guide: [Enabling 2-Step Verification](https://support.google.com/accounts/answer/185839).

If you have already enabled 2-step verification, jump to the next step.
{% endstep %}

{% step %}

### Generate an App password

Open [Google App passwords](https://myaccount.google.com/apppasswords).

Select **Other/Custom name** from **Select App**, give it a name such as "DO – Production Server", and then click **Generate**.

Note down the application password. You need it in the next step.

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fgit-blob-07edcd9e92be4bfade02c89c78aef49468b48863%2Fscreenshot-google-app-passwords.png?alt=media" alt="Google&#x27;s App passwords screen with Other (Custom name) chosen in the Select app dropdown"><figcaption><p>Pick <strong>Other (Custom name)</strong> so the password is labelled for this app.</p></figcaption></figure>

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fgit-blob-9d59eaa1eac517ddfac31c4e2f228d0c64956c08%2Fscreenshot-google-app-password-generate.png?alt=media" alt="The App passwords screen with a name typed and an arrow on the Generate button"><figcaption><p>Name it, then <strong>Generate</strong>.</p></figcaption></figure>

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fgit-blob-c662900e0089baa7f085e13eea9f6b3f4c75789c%2Fscreenshot-google-app-password-result.png?alt=media" alt="Google&#x27;s generated app password panel, with the sixteen-character password highlighted"><figcaption><p>This sixteen-character string — not your Gmail password — is what the app needs.</p></figcaption></figure>
{% endstep %}

{% step %}

### Fill in the SMTP section in the app

With **Google** chosen in the **SMTP** dropdown, the Google configuration takes the following:

<table><thead><tr><th width="70">#</th><th width="250">What the field is for</th><th>What to enter</th></tr></thead><tbody><tr><td>1</td><td>SMTP email</td><td>Your SMTP email.</td></tr><tr><td>2</td><td>Host and port</td><td><code>smtp.gmail.com</code> as your host, and port <code>465</code>.</td></tr><tr><td>3</td><td>Username</td><td>Your Gmail login username — <code>your.username@gmail.com</code>.</td></tr><tr><td>4</td><td>Password</td><td>Your <strong>App password</strong>, the one you generated above.</td></tr><tr><td>5</td><td><strong>Send mail as a different email</strong></td><td>Optional. Use it when the address you want quote emails to come from is not the mailbox you authenticated with — a <code>sales@</code> address, for example.</td></tr></tbody></table>
{% endstep %}
{% endstepper %}

{% hint style="danger" %}
The **App password** in field 4 is the app password you generated in the step above. It is **not** your Gmail account password. Google's explanation of what an app password is: [What is an App Password](https://support.google.com/mail/answer/185833).
{% endhint %}

## Why bother

<table><thead><tr><th width="270">Benefit</th><th>What it means</th></tr></thead><tbody><tr><td>Better deliverability</td><td>Mail from your own authenticated domain is filtered as spam less often.</td></tr><tr><td>Customers can reply</td><td>Replies reach you directly instead of a no-reply address.</td></tr><tr><td>Looks like you</td><td>Your quote arrives from your business, not from a shared app sender.</td></tr></tbody></table>

## If the test fails

* **Check the password** — most providers need an app-specific password, not your account password. On Google, that also means 2-Step Verification has to be on before an app password can exist at all.
* **Check the sending address** is one your provider is allowed to send as.
* **Re-check every connection detail** against your provider's own documentation; a single wrong character stops everything. On Google that is `smtp.gmail.com` and port `465`.
* **Check you saved** — the dropdown and the fields only take effect once you click **Save**.
* **Switch back to Use the app's default email** while you sort it out, so quote notifications keep flowing in the meantime.
* **Check the quote arrived anyway** in **Quote list**. A failed send never loses the request itself.

Still stuck? Email <support@samita.io> with the provider you chose and the error the app shows.

## Next steps

* [Emails sent to customers](/sa-request-a-quote/emails/emails-to-customers.md) — customise what your customers receive
* [Change notification recipients](/sa-request-a-quote/emails/change-recipients.md) — choose who gets notified
* [Troubleshooting](/sa-request-a-quote/help/troubleshooting.md) — wider email delivery problems


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.samita.io/sa-request-a-quote/emails/smtp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.