How to Add and Verify a Sending Domain

A sending domain allows MailerLogic to send emails on your behalf using your own identity. Verifying your domain ensures that inbox providers trust your emails and recognize MailerLogic as an authorized sender.

Domain verification is required before you can start sending emails.

Why Domain Verification Matters

Email providers rely on authentication signals to decide whether an email should reach the inbox. By verifying your domain, you confirm that MailerLogic is permitted to send emails using that domain.

This helps:

• Improve inbox placement

• Protect your sender reputation

• Prevent spoofing and phishing attempts

Adding a Domain

You can add a domain directly from the MailerLogic dashboard or through the API. Once added, MailerLogic automatically generates the DNS records needed for verification.

Most customers use a dedicated subdomain such as:
mail.yourdomain.com

DNS Records and Verification

MailerLogic provides DNS records like SPF and DKIM that must be added to your DNS provider. These records authenticate your emails and enable tracking features.

After adding the records, you can verify the domain from the dashboard. DNS changes may take up to 48 hours to propagate.

Common Issues

If your domain does not verify, double-check that all DNS records are added exactly as provided. Typos or missing records are the most common causes of verification failures.

Best Practices

Use a dedicated sending subdomain

Avoid sharing domains across multiple email providers

Monitor domain health regularly

SMTP in MailerLogic

​Sending Emails Using SMTP

MailerLogic supports SMTP-based email sending for applications that rely on traditional email delivery methods. SMTP is especially useful for legacy systems, CMS platforms, and tools that do not support REST APIs.

SMTP Credentials

SMTP credentials are generated from your MailerLogic account and include the hostname, port, username, and password. These credentials authenticate your application when sending emails.

For security reasons, credentials can be rotated at any time.

SMTP Configuration

To send emails using SMTP, configure your application with the following settings:

• SMTP Host: smtp.mailerlogic.net

• Port: 587 (recommended) or 2525 without encryption.

• Encryption: STARTTLS (for port 587)

• Authentication: Required

Security and Authentication

MailerLogic enforces encrypted connections and authenticated access for all SMTP traffic. This protects your account and prevents unauthorized usage.

If authentication fails, generating new credentials usually resolves the issue.

Common Issues

SMTP errors are often caused by incorrect credentials, missing TLS configuration, or an unverified domain. Always confirm your domain status before troubleshooting further.

Best Practices

• Rotate SMTP credentials periodically

• Never expose credentials publicly

• Monitor sending activity from the dashboard

Webhooks in MailerLogic

Receiving Real-Time Email Events

Webhooks allow MailerLogic to notify your application instantly when email events occur. Instead of checking delivery status manually, your system receives updates automatically as events happen.

Supported Events

MailerLogic can send webhook notifications for key email events, including:

• Delivered

• Opened

• Clicked

• Bounced

• Complained

• Unsubscribed

• Failed

How Webhooks Work

When a webhook is configured, MailerLogic sends an HTTP request to your endpoint whenever a selected event occurs. Your server should acknowledge the request with a success response to confirm receipt.

Setting Up Webhooks

To set up a webhook, provide a secure HTTPS endpoint and choose the events you want to receive. Webhooks can be enabled or disabled at any time from your account.

For reliable delivery, your endpoint should respond quickly and handle duplicate events safely.

Security Considerations

Always use HTTPS endpoints and validate incoming webhook requests. Limiting access to trusted IPs adds an extra layer of protection.

Common Issues

If events are not received, verify that the webhook is active and the endpoint is publicly accessible. Slow or failing responses may cause delivery retries.

Adding and verifying a sending domain is a one-time setup that plays a critical role in email deliverability. Once your DNS records are correctly configured and verified, MailerLogic can securely send emails on your behalf using your own domain identity.

A verified domain helps improve inbox placement, protects your sender reputation, and ensures reliable email delivery. If verification is delayed, allow time for DNS propagation and recheck your records. For advanced configurations or automation, refer to the MailerLogic Developer API documentation.