turboSMTP vs Mailgun: Compare EU Email Delivery Options

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

Verified on 27 October 2026 against Mailgun’s API overview, SMTP guide, and HTTP sending guide. 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.

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 and review processing terms for your requirements. Check turboSMTP 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.

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"
  }'

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 for DNS, suppressions, and webhook changes.

Frequently asked questions

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.

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 when you need separate credentials and account boundaries.

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.

Comparisons

Migration Guides

turboSMTP vs Mailgun: Compare EU Email Delivery Options

At a glance

Regional setup and plans

JSON and form data

Switching from Mailgun

Frequently asked questions

​At a glance

​Regional setup and plans

​JSON and form data

​Switching from Mailgun

​Frequently asked questions

At a glance

Regional setup and plans

JSON and form data

Switching from Mailgun

Frequently asked questions