Transactional Email for Websites: SMTP Setup, Authentication, and Deliverability Checklist
Reliable website email starts with the right sending method, authenticated domains, controlled sender addresses, and recurring tests. This guide explains how to configure SMTP or an email API for contact forms, account messages, and orders, then track delivery health over time.
Overview
Transactional email is the operational mail generated by a website or application. Examples include contact-form notifications, account verification messages, password resets, invoices, order confirmations, booking updates, and shipping notices. These messages are different from newsletters because they are triggered by a user action or business event, but they still need a deliberate delivery setup.
A website can be hosted successfully while its email workflow remains unreliable. Common symptoms include a form that appears to submit but never reaches the recipient, password-reset messages that arrive late, order emails sent from an invalid address, or messages that are delivered to spam. The cause may be an incorrect SMTP password, a blocked outbound connection, missing DNS authentication, poor sender alignment, or an application that reports success before the email provider has accepted the message.
For a site builder, WordPress installation, or custom application, the basic workflow is consistent:
- Choose an email delivery provider suited to the message volume and application.
- Verify the domain or sending identity required by that provider.
- Publish the provider’s authentication records in DNS.
- Connect the website through authenticated SMTP or an API.
- Send controlled tests and record the results.
- Monitor bounces, failures, complaints, and authentication status.
Keep email credentials separate from your web hosting login, use a dedicated sending identity where practical, and document every DNS record and application setting. If you are changing hosts or domains, include email in the migration plan rather than treating it as a post-launch detail. The DNS records setup guide can help organize records for the domain, hosting, and email services.
What to track
1. Sending method and connection settings
SMTP is often the simplest choice for a site builder or plugin because it can be configured with a hostname, port, encryption mode, username, and password. An email API may be preferable for a custom application because it uses an authenticated HTTP request and can return structured delivery responses. The choice should match the integration options supported by your platform and the level of delivery detail your team needs.
Record the following values in a protected configuration document:
- Provider name and account or project identifier.
- SMTP hostname and port, or API endpoint.
- Encryption requirement, such as a secure transport setting supported by the provider.
- Credential owner, creation date, and rotation date.
- Approved sender address and reply-to address.
- Application events that trigger messages.
Do not place secrets in page content, theme files, client-side JavaScript, public repositories, or screenshots. Use environment variables or the secret-management feature provided by the hosting platform. After changing credentials, send a test from the live configuration rather than assuming the new value has been applied.
2. Provider fit
Provider selection is less about finding a universal “best” service and more about matching the service to the website’s workflow. Compare providers using these practical criteria:
| Decision area | What to check |
|---|---|
| Integration | Does the site builder, WordPress plugin, framework, or deployment platform support SMTP, an API, or both? |
| Authentication | Can you verify the sending domain and publish SPF, DKIM, and DMARC-related records as required? |
| Visibility | Can you inspect accepted, rejected, bounced, or deferred messages without relying only on the website log? |
| Limits | What sending limits, recipient restrictions, retention settings, and account controls apply to your use case? |
| Operations | Are credential rotation, team access, webhooks, logs, and alerts practical for the people maintaining the site? |
| Privacy | What message data is retained, where is it processed, and which data should never be included in email? |
For a small business website, simplicity and clear logs may matter more than advanced features. For an application with multiple message types, an API, event webhooks, and separate credentials for staging and production may be more useful. Avoid using a personal mailbox password as the website’s delivery credential.
3. Domain authentication and sender identity
Authentication records help receiving systems evaluate whether a provider is authorized to send on behalf of your domain. The exact values come from your email provider, so copy them carefully and avoid inventing record contents.
- SPF: identifies authorized sending services through a DNS policy. Maintain one coherent SPF policy for the domain rather than adding disconnected records.
- DKIM: allows the provider to sign messages using a domain key. Publish the selector and value supplied by the provider.
- DMARC: tells receiving systems how to evaluate alignment and how to report relevant results. Start with a policy appropriate to your monitoring readiness, then strengthen it as you gain confidence.
Use a sender address on a domain you control, such as [email protected], and keep the visitor’s address in the Reply-To field for contact forms. This separates the site’s authenticated identity from user-supplied data and makes replies behave as expected. Avoid accepting arbitrary visitor input as the visible “From” address.
Cadence and checkpoints
Transactional email should be tested when it is launched, whenever it changes, and on a recurring schedule. A monthly check is appropriate for many small websites; higher-risk applications may need more frequent monitoring. Use a simple test matrix and save the date, environment, trigger, result, and message identifier.
| Test | Expected result | Record |
|---|---|---|
| Contact form submission | Visitor receives confirmation if configured, and the business inbox receives the notification. | Submission time, recipient, sender, reply behavior, and spam-folder result. |
| Account registration | Verification message arrives with a working link and an understandable sender name. | Trigger, delivery time, link destination, and expiration behavior. |
| Password reset | Reset message arrives, uses HTTPS, and does not expose sensitive information. | Request time, delivery result, token behavior, and application log. |
| Order or booking event | The customer and internal recipient receive the correct event-specific message. | Order reference, recipient list, template version, and delivery status. |
| Negative test | An invalid or unavailable address produces a visible failure rather than silent success. | Provider response, bounce classification, and application handling. |
Run tests from production and staging separately. Staging should use test recipients or a controlled mailbox so that development messages do not reach real customers. Check both the application log and the provider dashboard: an application can successfully submit a request while the provider later rejects or defers the message.
At least quarterly, review DNS authentication, account access, sending limits, credentials, templates, and recipient data handling. Recheck after a domain change, hosting migration, provider change, plugin update, framework upgrade, or DNS restructuring. For broader launch work, pair this checklist with the website pre-publish checklist.
How to interpret changes
When website email stops arriving, isolate the failure in order. First confirm that the event occurred: inspect the form, application, or order log. Next confirm whether the message request reached the SMTP server or API. Then check the provider response and event log. Finally, inspect the recipient mailbox, spam folder, domain authentication results, and any bounce details.
Common patterns provide useful clues:
- No request in the provider log: investigate the application trigger, plugin configuration, network connection, or stored credentials.
- Authentication or connection failure: recheck the hostname, port, encryption mode, username, secret, and whether the provider requires a distinct SMTP credential.
- Provider accepted but recipient cannot find the message: check spam and filtering, sender alignment, the recipient address, and message identifiers.
- Only one recipient fails: compare the address, domain, mailbox rules, and bounce response rather than changing the entire website configuration.
- Many messages fail after a DNS change: review SPF, DKIM selectors, DMARC alignment, DNS propagation, and whether another service still sends mail for the domain.
- Messages arrive late: look for deferred delivery, provider queue events, application timeouts, or temporary recipient-server responses.
Do not respond to a drop in delivery by repeatedly retrying indefinitely. Configure sensible retry behavior, prevent duplicate order or reset messages, and preserve provider event IDs for investigation. Treat bounces as operational data: correct invalid addresses, suppress repeated permanent failures, and make sure users have a clear way to update their email address.
Privacy is part of deliverability operations. Keep sensitive information out of subject lines and message bodies where it is not needed, limit dashboard access, define log retention, and use links to authenticated pages for account actions. If a provider or platform changes its setup screens or authentication requirements, update your runbook rather than relying on an old screenshot.
When to revisit
Make email review a recurring launch and operations task, not a one-time setup. Revisit this checklist monthly when the website handles important leads, accounts, bookings, or orders. A quarterly review may be sufficient for a low-volume brochure site, provided its forms and notification paths are still tested.
Start an immediate review when:
- A contact form, password reset, order notification, or verification message fails.
- The domain, DNS provider, hosting platform, site builder, plugin, or email provider changes.
- SMTP credentials, API keys, sender addresses, templates, or recipient rules are rotated.
- Bounces, spam placement, delays, or complaint signals increase.
- A new application, subdomain, or sending service is added.
- A mailbox provider or email platform changes its authentication or reporting requirements.
Keep a short change log with the date, person responsible, affected domain, DNS edits, application settings, test results, and rollback plan. Before a major website release, test every critical message from a clean session and verify that links point to the correct production host. If the release involves a hosting move, review the cloud hosting migration checklist and schedule a post-cutover email test.
The practical goal is not to send more email. It is to make important messages predictable, authenticated, observable, and safe. A documented SMTP or API configuration, a small recurring test matrix, and a clear response process will prevent many “website form email not sending” incidents from becoming customer-facing failures.