InnoviaMail
  • 👋Welcome to A InnoviaMail
  • Broadcast
    • 🧑‍🏫What you can do with broadcasts
    • ➕Create a Broadcast
    • ⚙️Broadcast Settings
    • ⌨️Choosing your email composer
    • 🗣️Augment your subject line with a preheader
    • 📬Adding your recipients
    • ⏲️Schedule your Broadcast
    • 🔂Resend to non-openers automation
    • 📈Broadcast Reporting
    • 👯Duplicate a broadcast
    • 🏷️Tag contacts who Open your broadcast
    • 💫Resume an incomplete broadcast
    • ⬇️Export Broadcast Openers & Unsubscribes
    • 🛑Cancelar uma transmissão
    • 🔗Cancelar um gatilho de funil de transmissão
    • 🔧Revise tagging and funnel triggers for sent broadcasts
  • USING THE DRAG & DROP EMAIL COMPOSER
    • ⌨️The Basics
    • ⚒️Component Section Toolbar
    • 🏛️Designing your email - Using Columns
    • 🦶Footer
    • 🐦Social Media Component
  • TRANSACTIONAL
    • 📮Transactional SMTP Relay
    • 📭Transactional SMTP Relay requirements for Cloudflare
    • 📁Transactional templates
    • 🏷️Transactional tags
    • 🧀Use SWAKS for testing and troubleshooting
  • CONTACT LIST MANAGEMENT
    • ➕Create a contact list
    • ♻️Resubscribe after an unsubscribe
    • 👓List X-Ray
    • 🏷️Contact Tags Manager
    • ⬇️Export your contact list
    • 🚫Uploading a suppression list
    • ⚠️Large suppression files
    • ⛔Exclusion Lists
    • 🇪🇺GDPR Delete & Export
  • SEGMENTING
    • 🧑‍🏫What you can do with segments
    • ➕Create a segment
    • 🧱Designing your segment
    • 🏷️Tag contacts in a segment
    • ⬇️Export a Segment's Contacts
    • 🆎A/B test using segments
  • INTEGRATIONS
    • 🟢Pabbly Connect
    • 🔴Zapier
    • 🪝Event webhooks
    • 🅰️API
    • 🔲Integrating Pixabay into your email campaigns
    • 📰WordPress
  • Funnels
    • 🧑‍🏫What you can do with funnels
    • ➕Create a funnel
    • 🟧Choosing your funnel type
    • 🆔From Name & From Email - editing
    • ⚡Activating your funnel
    • 🔗Trigger an email funnel from a broadcast
    • 🏷️Tag contacts who open your funnel messages
    • ⌨️Choosing your email composer
    • 🗣️Augment your subject line with a preheader
    • 🤖Design your automated email sequence
    • 🚫Contact Suppression and Exclusion
    • 🖇️Adding a funnel to an opt-in subscriber form
  • SUBSCRIBER OPT-IN FORMS
    • 🧑‍🏫What you can do with forms
    • ➕Create an opt-in form
    • 2️⃣Sending to double opt-in contacts
    • 📋Choosing your form type: floating bars, lightboxes,inline naked embedded, slide outs
    • 🔙Exit intent and display rules
    • 📋Adding email and name input boxes to your form
    • ✏️Setting the size of your form
    • 📱Configuring how your form displays on mobile devices
    • 📲Configuring your mobile width
    • ✖️Add a close window X to your form
    • ⛔Adding a "No" button that closes your form
    • 🏷️Tag subscribers who opt-in to your form
    • 🙅‍♀️Adding "no thanks" text which closes your form
    • 🔣View your form conversion rate
    • 🔗Connect an existing form to your account
    • 💠Adding your form to your website
    • 🤖Add opt-in subscribers to an automated email sequence
Powered by GitBook
On this page
  1. TRANSACTIONAL

Transactional SMTP Relay

PreviousSocial Media ComponentNextTransactional SMTP Relay requirements for Cloudflare

Last updated 1 year ago

In the email marketing platform, go to Integrate -> API & SMTP -> SMTP Relay

If you're using Cloudflare for HTTPS, extra steps to enable SMTP Relay are required.

Attachments are currently not supported for transactional mail

Image attachments will be removed automatically, you need to include images by using regular HTML the usual way.

Configure your sending application to use your ESP hostname or IP address and ports 587, 2525, or 8025.

To make a secure encrypted connection, use the TLS extension after connecting via regular SMTP. SSL method is not supported.

If a multipart message consists of text and HTML parts, only HTML will be used.

Text parts are unsupported.

Use your API Key for your username and password.

The following standard headers are valid in a transactional message.

  • From: The from name and from email address, aka the 'Friendly From' or 'From Name'.

  • To: Specify the recipient's name but not their email address.

  • Subject: The message subject line.

  • Reply-To: Include an optional Reply-To address.

The following platform-specific headers are valid in a transactional message.

  • X-Transactional-Tag: If left blank, the message will be tracked as “untagged” on the transactional dashboard.

  • X-Transactional-Route: Specifies a postal route to use. This is required if the customer account has more than one postal route available, otherwise, the message will fail.

  • X-Transactional-Template: Include a template ID if you want to send this message using a pre-created transactional template.

  • X-Auth-APIKey: Bypass the SMTP AUTH username and password method and authenticate via header instead.

  • X-Transactional-Variables: Specifies a JSON string to use as an input dictionary for the Jinja2 templating system.

All other headers are automatically discarded and ignored.

You can actually use whatever you want for the Transactional SMTP Relay username. We recommend using the API Key for the username and password for simplicity of explanation, but the username is actually ignored and discarded and can be anything.

📮