Custom e-mail sender

This article explains how to set up a custom email sender in the AirLST Suite, verify your domain, and use the sender in your email templates.

PREREQUISITES

• Professional or Enterprise license
• Access to the DNS management of your sender domain (if necessary, through your IT department or hosting provider)
• A valid email address you want to use as the sender

STEP 1: CREATE A NEW SENDER

1. Navigate to any event in the AirLST Suite and open Messages → Email Senders.
2. Click Add New Sender. An input field will appear where you can enter the desired email address.
3. Confirm by clicking Create.

STEP 2: VERIFY THE EMAIL ADDRESS

After creating the sender, a confirmation email will automatically be sent to the specified address.
Click the link in this email to confirm the address.

After successful confirmation, a green checkmark will appear next to the email address in the sender overview.

STEP 3: ADD DNS RECORDS

Click on the verified email address in the sender overview to open the detail view. There you will find a table with the required DNS records for your sender domain.

All entries marked as (mandatory) must be added to the sender domain by your IT department or hosting provider. Entries marked as (required for secure and reliable email delivery) are necessary to ensure secure and reliable email delivery.

ACTION FOR SELECTION MENU

Via the "Action for Selection" menu, you can perform the following actions:

• Resend confirmation email
  If the original link has expired.
• Manually verify domain
  To trigger the DNS check immediately, without waiting for the 60-minute cycle.
• Delete sender
  Removes the sender from your account.

DNS RECORDS OVERVIEW

The following DNS records are required for sending emails via a custom sender domain.
AirLST uses Amazon Web Services (AWS SES) for email delivery.

SPF (Sender Policy Framework)

An SPF record (TXT record) specifies which mail servers are allowed to send emails on behalf of your domain. To send via AirLST, the SPF record must contain the value include:amazonses.com.

Note: If an SPF record already exists for your domain, add include:amazonses.com to it — do not create a second SPF record, as this can cause delivery issues.

DKIM (DomainKeys Identified Mail)

DKIM protects the integrity of your emails by digitally signing each message. For AWS SES, the DKIM keys are stored as CNAME records. The specific values can be found in your sender's detail view.

DMARC (Domain-based Message Authentication)

A DMARC record (TXT record) defines how recipient servers should handle emails that fail SPF or DKIM checks. A typical entry looks like: _dmarc.your-domain.com with the value v=DMARC1; p=quarantine; pct=100.

MX Record (Mail Exchange)

The MX record specifies which mail server is responsible for receiving emails for your domain. It is not strictly required for sending, but improves the trust of recipient servers in your sender domain. If no MX record is set, an AWS server will automatically handle incoming replies.

For more information on SPF, DKIM, and DMARC, see the article: SPF, DKIM and DMARC: Email Security with AirLST via AWS.

FREQUENTLY ASKED QUESTIONS

I clicked "Create" but did not receive a confirmation email.

Check the spam folder of the specified email address. If the email cannot be found, you can resend the confirmation email via the "Action for Selection" menu.

The DNS records are set, but the domain still shows no green checkmark.

DNS changes can take up to 48 hours to propagate globally. Our system checks every 60 minutes. You can also trigger the check manually via the "Action for Selection" menu.

Can I use the same sender for multiple events?

Yes! A verified email sender is automatically available for all events in your account.

What happens if I do not set the SPF record?

Without SPF and DKIM records, the sender domain cannot be verified and the email sender will not be available for sending. Both entries are mandatory.

Do I also need to set up a custom domain for the landing page?

No, the email sender and landing page domain are independent of each other. If you also want to use a custom domain for your landing pages, please refer to the article: Custom Domain for the Landing Page.