GetResponse SMTP Settings and Configuration (2026)
SMTP available as a paid enterprise add-on (MAX² plans only)
GetResponse offers native SMTP and REST API for transactional email, but only through the Transactional Emails add-on available on MAX² enterprise plans. There is no self-serve SMTP on Free, Email Marketing, Marketing Automation, or Ecommerce Marketing plans. Pricing is custom (contact sales), sized on your monthly transactional volume.
GetResponse is a Poland-based marketing platform (founded 2000) primarily positioned as an all-in-one for newsletters, marketing automation, landing pages, webinars, and ecommerce. Transactional email is a late-added enterprise capability, gated behind MAX², and marketed almost exclusively to ecommerce operations that want their marketing platform and transactional relay on one bill.
Who can use GetResponse SMTP
| Plan requirement | MAX² enterprise sales-negotiated |
|---|---|
| Free / Email Marketing / Marketing Automation / Ecommerce | No SMTP access, use alternatives below |
| Add-on activation | Via GetResponse Customer Experience Manager or sales |
| Pricing model | Custom, tied to monthly transactional send volume |
| Access to credentials | In-app only (Transactional emails › Settings) |
| Auth flow | Server + port + username displayed in-app, generate scoped SMTP password |
| Delivery methods | SMTP relay OR REST API |
| Overage behavior | Continues sending past monthly cap (billed on next cycle) |
SMTP hostname and port are not publicly documented
Unlike self-serve providers, GetResponse does not publish its SMTP server hostname or port on any public page. Values are shown only inside the account under Transactional emails › Settings after the add-on is enabled. If you are evaluating GetResponse for an integration before signing up, you cannot verify SMTP endpoint compatibility from public docs alone — you must engage sales or your Customer Experience Manager first.
SMTP configuration flow
Enterprise transactional relay
For MAX² ecommerce stacks integrating a CMS with GetResponse-managed transactional email
Setup steps
- Contact GetResponse sales or your Customer Experience Manager to enable the Transactional Emails add-on on your MAX² account. Pricing is negotiated based on your monthly transactional send volume.
- Once enabled, log into GetResponse and open Transactional emails from the main navigation.
- Click Settings in the top toolbar. GetResponse displays your assigned server hostname, port, and username on this screen.
- Click Generate password, give it a descriptive name (for example,
woocommerce-prodormagento-staging), and click Generate. Copy the password immediately — the same one-time-display pattern applies here as elsewhere in the industry. - Configure your ecommerce CMS or application with the SMTP server, port, username, and generated password. GetResponse maintains native tutorials for WooCommerce, Magento, PrestaShop, Shopify, Shoper, and Zapier.
- Set message templates directly in your CMS (not in GetResponse). Per GetResponse’s model, transactional messages are composed by the sending application and relayed through GetResponse — the platform does not host transactional templates the way it hosts marketing templates.
- Test with a small volume send. GetResponse’s transactional pipeline enforces several checks (see message restrictions below) so a test that passes marketing-side sender rules may still be rejected transactional-side.
Message restrictions
GetResponse enforces stricter formatting rules on transactional traffic than most competing relays. Your ecommerce CMS output must satisfy every point below or the message rejects.
- The Transactional Emails plugin must be enabled on your account (Customer Experience Manager confirms this).
- The From name and From email must match a Name/From configured in your GetResponse account — you cannot send from arbitrary addresses.
- Each message has exactly one
To:recipient. Multi-recipient transactional sends require separate messages. - Maximum 7 CC/BCC recipients total per message (across both fields combined).
- One optional Reply-To address per message.
- Sender address and envelope address must match — SPF alignment is enforced strictly.
- Subject line hard limit: 512 characters.
- Messages must have a non-empty subject line.
- Messages to known spam trap addresses are silently dropped (no bounce notification).
Deliverability model
GetResponse Max operates its own IP infrastructure with the reputation-management practices you would expect from an enterprise ESP — multiple sending IPs, rotation, throughput guarantees, and auto-scaling past your monthly cap. Because the add-on ships on top of a marketing-first platform, your transactional sends share account-level reputation signals with any Marketing Automation campaigns you run through the same account. Teams running both simultaneously should discuss dedicated IP options with their Customer Experience Manager.
Common setup gotchas
No self-serve access
Unlike Postmark, Mailgun, SES, or MailerSend, you cannot sign up and get SMTP credentials in minutes. Every GetResponse transactional integration goes through sales, contract negotiation, and MAX² provisioning. If you need SMTP running today, GetResponse is the wrong choice regardless of your marketing use of the platform.
Templates live in your CMS, not GetResponse
GetResponse’s transactional add-on is a pure relay — message templates are composed and stored in your sending application (WooCommerce order confirmations, Magento shipping notifications, custom app code). GetResponse does not provide a transactional template editor. Teams migrating from Mandrill or Postmark templates need to move template logic to their CMS or a templating layer above SMTP.
Marketing and transactional share the same account reputation
Because the transactional add-on runs on your marketing account, a large marketing send that generates complaints can drag transactional deliverability with it. Enterprise customers with meaningful transactional volume typically negotiate a dedicated IP as part of the MAX² contract to isolate reputations.
Custom pricing means no published unit cost
GetResponse’s transactional pricing is negotiated per account — no public rate card exists. You cannot compare it head-to-head with Amazon SES ($0.10 per 1,000) or Postmark ($1.25 per 1,000) until sales gives you a quote. Ask for the effective per-1,000 rate during your first sales call to make the comparison tractable.
SMTP endpoint values are account-specific and undocumented publicly
The SMTP hostname and port are provisioned per account and shown only inside your GetResponse panel. If your infrastructure team needs to whitelist outbound SMTP destinations before signing a contract, GetResponse cannot provide this info without an active MAX² account. Plan the procurement flow accordingly.
If MAX² is out of budget or scope
Most teams considering GetResponse do so for its marketing platform. If SMTP relay is your primary need or you want a standalone transactional provider alongside GetResponse marketing, these are the standard pairings:
- Postmark — transactional-only, simple setup, $1.25 per 1,000, best for boutique volume up to a few million per month.
- Amazon SES — cheapest at scale ($0.10 per 1,000), self-serve, works well if your app is already on AWS.
- MailerSend — generous free tier (500/mo), transactional focus, clean developer experience.
- Brevo — unified marketing + transactional if you also want to move away from GetResponse’s marketing side.
Frequently asked questions
Can I use GetResponse SMTP on the Email Marketing or Marketing Automation plans?
No. The Transactional Emails add-on is available only on MAX² enterprise plans. Standard Free, Email Marketing, Marketing Automation, and Ecommerce Marketing tiers do not offer any SMTP endpoint. If you need SMTP relay and are not on MAX², use a dedicated transactional provider like Postmark, Amazon SES, or MailerSend.
What is the GetResponse SMTP hostname and port?
GetResponse does not publish SMTP hostname or port on public documentation. Both values are assigned per-account and displayed only inside your GetResponse panel under Transactional emails › Settings after the add-on is enabled. To confirm compatibility before signing a MAX² contract, engage GetResponse sales and ask for the values in writing during your procurement review.
How much does the GetResponse Transactional add-on cost?
Custom pricing, negotiated per account based on your projected monthly transactional volume. No published rate card exists. Ask GetResponse sales for the effective cost per 1,000 emails during your quote review, then compare against benchmark self-serve rates like Amazon SES ($0.10 per 1,000) or Postmark ($1.25 per 1,000 transactional) to evaluate value.
Where do I write my transactional email templates?
In your ecommerce CMS or sending application, not in GetResponse. The transactional add-on is a pure relay: GetResponse accepts formatted messages from your sender and delivers them. You compose order confirmations in WooCommerce/Shopify/Magento, password reset emails in your app framework, and so on. GetResponse does not provide a transactional template editor.
Can I send to multiple recipients in a single transactional message?
Only in a limited way. Each transactional message allows exactly one To: recipient plus up to 7 CC/BCC total across both fields. For bulk transactional sends (order confirmations to hundreds of buyers), your CMS must generate separate messages per recipient. This is stricter than most transactional providers — if you rely on batch-send patterns, verify with your integration first.
Does GetResponse offer a dedicated IP for transactional sends?
Yes, negotiated as part of the MAX² contract. Because the add-on shares account-level reputation with any Marketing Automation campaigns you run through GetResponse, teams with meaningful transactional volume should discuss dedicated IP options with their Customer Experience Manager to isolate transactional reputation from marketing reputation.
What ecommerce platforms integrate with GetResponse SMTP out of the box?
GetResponse publishes native integration guides for WooCommerce, Magento (Adobe Commerce), PrestaShop, Shopify, Shoper, and Zapier. Any CMS or application that supports standard SMTP relay with LOGIN authentication will work — the native tutorials just walk through the specific CMS UI. For custom apps, use the SMTP credentials directly or switch to the REST API for finer control over sending metadata.
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.
