> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/using-peakcommerce/system-communications/using-your-own-smtp-email-provider.md).

# Using Your Own Email Provider

PeakCommerce's built-in email sender exists so you can verify templates and flows during setup — it is **intended for testing only**. For production you should connect your own email provider. Doing so means transactional mail comes from **your** domain and sender identity, and you get full visibility into delivery: bounces, opens, suppressions, and reputation all live in tooling you control rather than a shared default sender.

## What this changes

Connecting a provider routes **all** outbound PeakCommerce email — order confirmations, payment receipts, and notification-template emails — through that one account. It does not change template content or which events fire; it only changes the sending path. You configure **one** provider, and it handles every outgoing message.

## Supported providers

* Amazon SES
* Mandrill
* SendGrid
* SparkPost
* Other SMTP (for example Gmail or Yahoo)

## How to configure

The exact steps depend on the provider, but the shape is the same: enable the integration for your tenant and supply the credential it needs.

* **SendGrid** — enable the SendGrid integration and provide your **SendGrid API key** in your integration settings. Once it's activated and the key is in place, all outgoing email routes through SendGrid. (See the SendGrid integration page in the Integrations area for the full walkthrough.)
* **SMTP-based providers** — provide host, port, and SMTP credentials, plus the **From** address you want mail to come from.

After connecting, send a test notification and confirm it arrives from your domain before relying on the provider for live customer mail.

## Allowlisting

So PeakCommerce can send through your provider, you may need to open the right ports and allow inbound connections from PeakCommerce's sending IP addresses. Your implementation specialist can provide the current IP list.

## Gotchas

* **Both activation and a valid credential are required** — email won't route through your provider until the integration is enabled *and* the API key or SMTP credentials are in place.
* **Keep credentials current.** A revoked or rotated SendGrid key, or expired SMTP credentials, silently stops delivery until you update them — failures stay visible, so check delivery after any credential change.
* **Authenticate your domain** (SPF/DKIM) in your provider so mail from PeakCommerce isn't flagged as spam.
* Switching providers re-points *all* outbound mail at once; there's no per-message provider split.

Need help choosing or wiring up a provider? Set it up with your PeakCommerce implementation team.

## Related

* [Notification Templates](/product/using-peakcommerce/system-communications/email-templates.md) — control what the emails say.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/using-peakcommerce/system-communications/using-your-own-smtp-email-provider.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.