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

# turboSMTP vs Mailgun: Compare EU Email Delivery Options

> Compare turboSMTP and Mailgun on regional endpoints, API request formats, message size, and SMTP settings before migrating.

turboSMTP and Mailgun offer SMTP relay and an HTTP email API with Global or US and EU endpoints. Compare region setup, credentials, request formats, and message limits before choosing an integration.

## At a glance

| Setting | turboSMTP | Mailgun |
| - | - | - |
| **Global / US SMTP host** | `pro.turbo-smtp.com` | `smtp.mailgun.org` |
| **EU SMTP host** | `pro.eu.turbo-smtp.com` | `smtp.eu.mailgun.org` |
| **SMTP credentials** | Consumer Key and Consumer Secret | Per-domain SMTP username and password |
| **SMTP ports** | 587 / 2525 with STARTTLS; 465 / 25025 with implicit TLS; 25 also available | 25 / 587 / 2525 with STARTTLS; 465 with implicit TLS |
| **Send API** | `POST /api/v2/mail/send` | `POST /v3/{domain}/messages` |
| **EU API host** | `api.eu.turbo-smtp.com` | `api.eu.mailgun.net` |
| **Request format** | JSON | `multipart/form-data` |
| **API authentication** | `consumerKey` and `consumerSecret` headers | HTTP Basic auth, username `api` and password API key |
| **Published message limit** | Send API: less than 24 MB including attachments | 25 MB per message |

> [!NOTE]
>
> Verified on 27 October 2026 against Mailgun's [API overview](https://documentation.mailgun.com/docs/mailgun/api-reference/api-overview), [SMTP guide](https://documentation.mailgun.com/docs/mailgun/user-manual/sending-messages/send-smtp), and [HTTP sending guide](https://documentation.mailgun.com/docs/mailgun/user-manual/sending-messages/send-http). Confirm current limits and plan terms before migrating.

The turboSMTP limit applies to the whole email, not raw attachment files. Base64 encoding adds roughly one third to binary data, before MIME headers and boundaries. Leave room for those and for the body. See [Attachments](/docs/sending/attachments.md).

## Regional setup and plans

Mailgun selects the API region according to where the sending domain was created. Its API overview distinguishes region-bound message data from globally replicated account information. For turboSMTP, choose the [Global or EU sending endpoint](/docs/api-reference/base-urls.md) and review processing terms for your requirements.

Check [turboSMTP pricing](https://serversmtp.com/pricing/) for feature availability. Free and Basic have a 30-day webhook demo, and individual events can be disabled for an account. Support channels also depend on your plan.

## JSON and form data

Mailgun takes form fields and includes the sending domain in the URL. turboSMTP accepts a JSON body with `content` for text and `html_content` for HTML.

```bash turboSMTP theme={"system"}
curl -X POST https://api.eu.turbo-smtp.com/api/v2/mail/send \
  -H "consumerKey: YOUR_CONSUMER_KEY" \
  -H "consumerSecret: YOUR_CONSUMER_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "you@yourdomain.com",
    "to": "recipient@example.com",
    "subject": "Hello there!",
    "content": "Testing turboSMTP"
  }'
```

```bash Mailgun theme={"system"}
curl --user 'api:YOUR_API_KEY' \
  https://api.eu.mailgun.net/v3/YOUR_DOMAIN_NAME/messages \
  -F from='you@YOUR_DOMAIN_NAME' \
  -F to=recipient@example.com \
  -F subject='Hello there!' \
  -F text='Testing Mailgun'
```

## Switching from Mailgun

SMTP users update host and credentials while checking TLS. API users convert form data to JSON. Follow the [Mailgun migration guide](/docs/migrate/from-mailgun.md) for DNS, suppressions, and webhook changes.

## Frequently asked questions

> [accordion] Which hosts should I use for EU sending?
>
> turboSMTP uses `api.eu.turbo-smtp.com` and `pro.eu.turbo-smtp.com`. Mailgun uses `api.eu.mailgun.net` and `smtp.eu.mailgun.org` for EU-region domains.

> [accordion] Does turboSMTP require per-domain SMTP credentials?
>
> No. A Consumer Key with SMTP Sending permission can send for the account's configured sender domains. Use [subaccounts](/docs/account/subaccounts.md) when you need separate credentials and account boundaries.

> [accordion] Are Mailgun webhooks compatible with turboSMTP?
>
> Adapt the handler to turboSMTP's event payloads and endpoint protection. turboSMTP requests are unsigned, and event availability depends on your account. See [webhooks](/docs/analytics/webhooks.md).


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