SMTP Integration Requirements

Overview

An SMTP integration lets you send transactional emails through GetResponse. To set up the SMTP connection, you need to get your SMTP credentials from GetResponse. You can use them to configure the mail sending settings in your eCommerce CMS.

These are the requirements for your SMTP Integration:

1 Client Submission (SMTP Authenticated Submission)
2 Direct Send (SMTP relay)

Client Submission (SMTP Authenticated Submission)

Client SMTP submission allows your device or LOB application to send emails using an email address associated with an Office 365 mailbox by authenticating itself using that account.

Before You Begin

This method is required if sending email within and outside of your organization

Email sent by device/system will always use this email address in from the field.^[1]
The from email address provided must have a mailbox and the credentials to be able to authenticate with SMTP Server on port 587.

Note:

^[1] From email field in HyperCloud must be set to this email address or email server will reject the emails.

Direct Send (SMTP relay)

The direct send feature allows you to send emails directly from the server without using an SMTP server. You can directly communicate with the recipient server and deliver the message. An SMTP relay is a protocol that allows you to transmit an email through the internet, from one server to another, for delivery. It was first created in 1982 and continues to be the internet standard that is widely used today.

An SMTP relay is an email relay service that basically works in two steps:

It receives the outgoing mail from the sender (that is, your amazing Groundhog Day’s email campaign).
It delivers it to the recipient’s local post office, another SMTP server.

Before you Begin

This method is suitable only if you’re sending an email within your organization.

Email address does not need a mailbox or credentials and can use port 25 or 465
Email sent by device/system can have a different from email address. ⁽¹⁾