Lurox 1.0 is live β€” visual page building for Magento 2. Read the guide
SMTP User Guide

SMTP User Guide

Reliable transactional email β€” presets, test-send verification, per-store senders and delivery logs.

Why your store needs SMTP

Order confirmations, password resets, shipping updates β€” your store's most important emails are transactional, and they need a real mail server to be delivered reliably. Left on Magento's default mail handling, those messages often fail or land in spam. The SMTP module routes all outbound mail through a proper SMTP service of your choice, with provider presets, a test-send button, per-store sender identities and full delivery logging.

Configuration

Stores → Configuration → Cabbage Patch Studios → SMTP.

SettingWhat it doesDefault
Enable SMTPReplaces Magento's default mail transport.No
Provider PresetAuto-fills host, port, protocol and auth for a common provider (or choose Custom).Custom
SMTP Host / PortYour mail server and port (25, 465 or 587).β€” / 587
EncryptionNone, SSL (465), TLS or STARTTLS (587).TLS
Auth MethodNone, LOGIN, PLAIN, CRAM-MD5 (OAuth 2.0 on Pro).LOGIN
Username / PasswordYour SMTP credentials. The password is encrypted at rest.β€”
Return-Path / From OverrideBounce address; force a specific From on all mail.β€”
Enable Logging / RetentionLog sent mail; auto-delete after N days.Yes / 30
Test ConnectionA button that runs a full SMTP handshake and reports success and response time.β€”
Developer "preview mode" There's a preview mode that logs mail without actually sending it β€” useful on a staging site, but make sure it is off in production or no email will go out.
The SMTP admin configuration screen.
The configuration screen β€” server, encryption, authentication, sender and logging settings, with the Pro features listed below. (Host and credentials are redacted in this screenshot.)

Provider presets

Pick a preset and the connection fields fill themselves in β€” you only add your username and password.

ProviderHostPortEncryption
SendGridsmtp.sendgrid.net587TLS
Mailgunsmtp.mailgun.org587TLS
Postmarksmtp.postmarkapp.com587TLS
Amazon SES (Sydney)email-smtp.ap-southeast-2.amazonaws.com587TLS
Brevosmtp-relay.brevo.com587TLS
Mailjetin-v3.mailjet.com587TLS
Gmail / Google Workspacesmtp.gmail.com587TLS
Microsoft 365smtp.office365.com587STARTTLS
Self-hosted / Customyour server587STARTTLS

Other presets include Zoho, SparkPost, Elastic Email, SMTP2GO and Outlook.com β€” eighteen in total.

Setting it up

  1. Get SMTP credentials from your provider (often an API key used as the password).
  2. In SMTP, set Enable SMTP to Yes and choose your Provider Preset.
  3. Enter your Username and Password.
  4. Click Test Connection β€” you should get a success message with a response time.
  5. Click Save Config, then trigger a real email (e.g. a password reset) and check it arrives.
  6. Confirm it's logged under Marketing → SMTP → Email Logs with status success.

Per-store senders & the admin fallback

Configure SMTP at Default Config to cover every store and your admin/system emails (password resets, low-stock alerts). Per-website overrides then tailor customer emails for a specific brand, and per-store-view overrides are available on Pro.

Admin email won't silently break Admin and system emails resolve at the Default Config scope. If you've only set SMTP at website or store scope, the module borrows your lowest enabled storefront profile so mail still goes out β€” and shows an admin notice prompting you to set a dedicated Default-scope sender. The clean fix is simply to configure SMTP at Default Config.

FAQ

Port 587 or 465? Use 587 (TLS/STARTTLS) for new setups β€” it's the modern standard. 465 (SSL) is older but still works. Avoid 25 for external providers; ISPs often block it.

"Authentication failed" on the test? Double-check the username/password (no stray spaces), the auth method, and that your provider allows SMTP. Gmail and Microsoft 365 require an app password (or OAuth on Pro), not your normal account password.

My mail still goes to spam. SMTP delivers; inbox placement depends on your domain's email authentication. Set up SPF, DKIM and DMARC in your DNS (your provider supplies the records). The module logs delivery results, but authentication is configured at the domain level.

Logs filling up? Set Log Retention to a sensible window (e.g. 30 or 90 days); a daily cleanup removes older entries.

Changelog

This guide is itself a Lurox page. Every revision is a published version in Lurox's built-in content history, so we can roll any guide back to an earlier version at any time. The public changelog below tracks what changed and when.

Version 1.1

30 June 2026

  • Added an annotated screenshot of the configuration screen.
Version 1.0

30 June 2026

  • Initial publication: configuration, provider presets, setup walkthrough, per-store senders and the admin-scope fallback, plus deliverability FAQ.

Explore the rest of the library

Browse every Cabbage Patch Studios user guide in one place.

All User Guides