Configuration guide

Email configuration

Configure SMTP or a transactional email provider for reliable SigmaCart system messages, including order confirmations, password resets, account notifications, and other important store communication.

Open Email Settings

Sign in to the SigmaCart administration panel and open the Email Settings section from Platform Settings.

https://yourstore.com/console/settings?#emailSettings

Use your store domain

Replace yourstore.com with the actual domain where the SigmaCart administration panel is installed.

SigmaCart Platform Settings page showing the Email Settings option in the configuration menu — Open Platform Settings and select Email Settings from the configuration menu. The screenshot currently displays SMS Settings until Email Settings is selected.

Choose an email delivery method

Select a method that matches your store volume, reliability requirements, and hosting environment.

Standard SMTPHosting or mailbox SMTP Suitable for small stores and testing when your hosting provider or business mailbox includes authenticated SMTP access.

Transactional emailDedicated email provider Recommended for production stores that need better deliverability, monitoring, scaling, and reputation management.

DevelopmentMail testing service Use a sandbox inbox during development so test messages never reach real customers accidentally.

Use authenticated delivery

For consistent production delivery, use authenticated SMTP or a supported transactional provider instead of relying on the server’s basic PHP mail function.

SMTP configuration

Obtain the connection details from your email or transactional provider, then enter them in SigmaCart Email Settings.

Select SMTP as the mail driver. Choose SMTP or the equivalent email-provider option available in your SigmaCart version.
Enter the server details. Add the SMTP hostname, port, encryption method, username, and password.
Configure the sender identity. Use a verified From Email address and a recognizable From Name for your store.
Save the settings. Confirm that no field contains leading or trailing spaces.
Send a test email. Verify receipt, sender identity, links, and message formatting before production use.

SMTP configuration fields

Field	Example	Description
Mail driver	SMTP	The delivery transport used by the Laravel backend.
SMTP host	smtp.example.com	The outgoing mail server supplied by your provider.
SMTP port	587	Port 587 is commonly used with STARTTLS. Use the exact port specified by your provider.
Encryption	TLS or SSL	The secure connection method required by the selected SMTP port.
SMTP username	Provided account or API username	The authenticated username supplied by the provider.
SMTP password	App password, SMTP password, or API credential	A secret backend credential. Never expose it in frontend code.
From Email	orders@yourstore.com	The verified sender address shown to recipients.
From Name	Your Store Name	The recognizable sender name displayed in the customer’s inbox.

Protect email credentials

SMTP passwords and provider API credentials must remain in the Laravel backend. Never expose them through NEXT_PUBLIC_* variables, client-side JavaScript, screenshots, source control, or public documentation.

Recommended email events

After configuring delivery, verify every system event used by your store.

OrdersOrder communication Order confirmation, payment updates, processing updates, shipment information, delivery status, and cancellation notices.

AccountsCustomer notifications Welcome messages, email verification, password reset links, account updates, and important security notifications.

OperationsStore administration New-order alerts, contact notifications, exception reports, and other configured operational messages.

Domain authentication and deliverability

Transactional providers commonly require DNS records that prove SigmaCart is authorized to send email for your domain.

Verify the sending domain
Add the provider’s SPF record
Add the provider’s DKIM records
Configure a DMARC policy
Use a domain-based From Email
Monitor bounces and complaints

Follow provider-specific DNS instructions

DNS record names and values differ between providers. Copy them exactly from your provider dashboard and allow time for DNS propagation before retesting verification.

Test email delivery

Send a test email from Email Settings
Check inbox and spam folders
Verify From Name and From Email
Open links and action buttons
Test password-reset delivery
Place a complete test order

Production-ready verification

Do not consider email configuration complete until both account emails and order emails have been received successfully using production-like settings.

Email troubleshooting

Problem	What to check
Connection timed out	Confirm the SMTP host and port, server firewall rules, provider access policy, and whether outbound SMTP is blocked by your host.
Authentication failed	Verify the username and password, use an app password when required, and remove accidental spaces from credentials.
Encryption error	Match the encryption method to the provider’s port. Do not combine an SSL-only port with STARTTLS settings.
Sender rejected	Use a verified From Email address and confirm that the sender domain is authorized by the provider.
Email goes to spam	Verify SPF, DKIM, and DMARC; use consistent sender identity; avoid misleading subjects; and monitor provider reputation reports.
Order email not sent	Confirm the order event is enabled, queue workers are running when queues are used, and Laravel logs contain no mail exceptions.
Password reset not received	Confirm the customer address, reset-email template, application URL, queue processing, and provider delivery logs.

Production checklist

Production provider credentials saved
From address verified
SPF and DKIM authenticated
DMARC policy configured
Order emails tested
Password resets tested
Queue worker verified if enabled
Bounce monitoring enabled

Email configuration complete

Reliable email delivery keeps customers informed and protects important account workflows. Monitor failed messages, bounces, complaints, and provider limits after launch.

Email configuration #