> For the complete documentation index, see [llms.txt](https://help.checkoutchamp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.checkoutchamp.com/crm/plugins/smtp-maintenance/maropost-smtp-profile.md).

# Maropost SMTP Profile

This guide will show you how to configure your SMTP profile to support using an API key with Maropost.

1. Navigate to Admin → Plugins → SMTP Maintenance

* Click the *Add Mail Server* \[+] button or the edit button associated with your Maropost SMTP Profile
* Set the form fields like as:

**Host Name:** smtp.maropost.com

​**Username**: apikey (Not your actual API key- type in “apikey”)

**Password**: Your API key from Maropost

**From Email**: the address associated with this SMTP Profile

**Port number:** 587

**Use SSL:** unchecked

**Use Relay:** checked

**Custom Headers (\* indicates required):**

&#x20;  **\* X-ApiKey:** Your API key from Maropost

&#x20;  **\* X-AccountID:** Your Maropost Account ID

&#x20;  \* **X-CampaignName**: The unique lookup key for the transactional campaign

&#x20;  \* **X-CampaignID**: The Transactional Campaign ID that you have created within Maropost for Marketing. *This x-header is required ONLY if your Maropost Marketing Cloud Account ID is between 1 and 999.*

&#x20;  \* SMTPAutoTLS:false             This custom header must be included with *false* for Maropost SMTP to work properly.

<figure><img src="/files/g84IPUwuMhWxPajXJ87F" alt=""><figcaption><p>Checkout Champ - Maropost SMTP</p></figcaption></figure>

Optional SMTP Headers and more SMTP information can be found [here](https://galaxy.maropost.com/s/article/Sending-Transactional-Campaigns-via-SMTP).


---

# 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://help.checkoutchamp.com/crm/plugins/smtp-maintenance/maropost-smtp-profile.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.
