Laravel SMTP with Airmail

SMTP settings

Use smtp.airmailai.tech, port 587, STARTTLS required, and the username/password created in your workspace SMTP settings. These are not your dashboard login or REST API key. Keep certificate verification enabled. Do not choose implicit TLS on port 587. SMTP is submission only: it is not an IMAP/POP mailbox. Set a verified From address and monitored Reply-To. Preserve Message-ID and identical MIME content when retrying an uncertain SMTP transaction.

Host: smtp.airmailai.tech
Port: 587
Encryption: STARTTLS (required)
Username: your Airmail SMTP username
Password: your one-time SMTP password

• SMTP documentation

Laravel configuration

For Laravel 12's Symfony-based mailer, configure the smtp entry in config/mail.php as below. require_tls is supported by recent Symfony Mailer versions; verify it against your installed version. Older Laravel 8 applications use the encryption=tls setting instead of scheme/require_tls. Never disable certificate checks. Restart your normal queue workers when deploying a mail configuration change.

// config/mail.php, inside mailers
'airmail' => [
    'transport' => 'smtp', 'scheme' => 'smtp',
    'host' => 'smtp.airmailai.tech', 'port' => 587,
    'username' => env('AIRMAIL_SMTP_USERNAME'),
    'password' => env('AIRMAIL_SMTP_PASSWORD'),
    'require_tls' => true, 'timeout' => 30,
],

• Laravel mail configuration
• Symfony TLS requirements

Send using the named mailer

Use Mail::mailer('airmail')->to($recipient)->send(new YourExistingMailable()) in your application service. Set a From address on your verified domain. For tests, use Mail::fake() rather than a real recipient. A framework queued job and Airmail durable queue are different stages: keep a stable RFC Message-ID and identical content across an uncertain SMTP retry.

Before your first production message

Start with the free Developer beta. Verify your account, create a workspace and add a domain you control: example.com and mail.example.com are both supported. Publish the records shown in Domains. Merge an existing SPF policy rather than adding another; preserve a valid existing DMARC policy. Create an API key after verification, use the dashboard for one owner-controlled validation, and request production approval. SMTP credentials become available after activation. No repository or SSH access is needed.

• DNS and onboarding
• Start free

Know the boundaries

Airmail is a controlled public beta. Production sending requires manual approval. Paid plans remain request-access for general signups; payment never grants sending approval. Monthly allowance, daily safety quota and provider pacing are different limits. Sending is transactional by default; partnership/campaign access needs separate approval and is not a purchased-list service. Dedicated reputation isolation is not currently included. There is no inbox-placement guarantee or published OTP delivery SLA.

• Current pricing and limits
• Acceptable use

Start with one verified domain

All integration guides / Ask about your use case