Mail and Notification Settings

Mail ownership

SophMate workflows can create support drafts, watcher alerts, contact confirmations, and operational notifications that depend on reliable mail handling. Use a monitored mailbox and a transactional mailer for production communication rather than relying on default PHP mail behavior.

Notification routing

Decide which alerts go to site administrators, store owners, developers, agency operators, or support leads. Watcher and workflow notifications should include enough context to act without exposing secrets. The watchers and alerts docs explain alert ownership, and diagnostics and support explains what evidence should be safe to share.

Production verification

Before inviting users, send test messages for contact flows, watcher alerts, and support handoffs. The production readiness tutorial should be updated with the mailbox, delivery provider, and escalation owner.

Quick reference

• Use this page when changing provider, budget, role, mail, queue, cron, source, cache, or WooCommerce context settings.
• Do not store secrets, credentials, purchase codes, or private customer data in documentation notes or screenshots.
• Key decision: whether critical SophMate notifications reach monitored recipients and can be traced through the mail provider.

Scope limits

• Do not treat one delivered test message as proof that operational mail is reliable.
• This page does not replace provider, host, mail, billing, security, or legal policy review where those owners are responsible.
• Use it to frame configuration decisions, not to store secrets or justify broad access.

Owner and cadence

• Primary owner: site administrator with provider, billing, and security responsibility.
• Review cadence: after provider, mailbox, role, budget, security, WooCommerce, or integration changes.
• Escalate when a setting grants high-risk access, changes provider spend, weakens privacy posture, or redirects alerts away from monitored owners.

Access and data boundary

• Notification evidence should use monitored mailboxes, sender-domain status, bounce logs, and test timestamps without sharing mailbox credentials.
• Restrict provider keys, billing, budgets, roles, mail routing, queues, cron, cache, and integration settings to accountable administrators.
• Document setting intent and validation results without storing API keys, mailbox passwords, purchase codes, raw logs, or private customer records.

Production checklist

• Use a transactional mailer, monitored sender, reply-to address, and delivery logs for production notifications.
• Test contact confirmations, watcher alerts, support handoffs, and operator notifications before launch.
• Document who owns provider credentials, budget limits, role access, notification routing, and ongoing review.
• Keep configuration changes behind administrator access and review them after plugin updates, staff changes, or incidents.

Acceptance checks

• Critical notifications reach a monitored mailbox and can be traced through the mail provider.
• Failed mail delivery has an owner and does not silently hide workflow or support issues.
• A second administrator can explain why each high-risk setting is enabled and who may change it.
• No production credential, support mailbox, or notification path depends on an unmanaged personal account.

Failure modes to test

• Test bounced messages, spam placement, unmonitored inboxes, broken reply-to paths, sender authentication failure, and missing delivery logs.
• Test invalid credentials, exhausted budget, unmonitored mailbox, wrong role mapping, queue delay, cron failure, and cache-dependent behavior.
• Confirm configuration failures are visible to an owner without exposing provider keys, mailbox credentials, or raw logs.

Evidence to capture

• Capture sender domain, SPF/DKIM/DMARC status, monitored recipient, bounce path, test timestamp, and mail-provider evidence.
• Record changed setting, previous value category, new value category, owner, approval reason, and review date without storing secrets.
• Capture provider, budget, role, mailbox, queue, cron, cache, and WooCommerce evidence relevant to the setting being changed.

Decision record

• Decision field to include: monitored recipient, sender-domain status, delivery proof, bounce path, reply-to owner, and notification escalation route.
• Record the configuration decision, setting owner, previous setting category, new setting category, validation result, approval reason, and next review date.
• Include whether the change affects provider spend, privacy, mail delivery, queue or cron behavior, WooCommerce context, or user permissions.

Stop or rollback path

Pause notification-dependent workflows when delivery cannot be proven. Resume after the monitored inbox, sender authentication, bounce handling, and test evidence are confirmed.

Monitoring window

• Monitor the next operating cycle for unexpected spend, blocked work, missed notifications, queue delays, or changed provider behavior.
• Compare the setting change against audit records, diagnostics, and user reports before making another related change.

Expansion criteria

• Widen the setting change only after audit records, user reports, diagnostics, and cost or delivery signals match expectations.
• The owner can explain how to reverse or narrow the change without searching through unrelated settings.

Common mistakes

• Sending operational alerts to an inbox no one monitors during weekends, launches, or incidents.
• Using personal provider keys, personal mailboxes, or broad administrator access because it is faster during setup.
• Changing budgets, roles, notifications, or integrations without recording the owner and review reason.

Common questions

Is one successful email test enough?

No. Check sender authentication, monitored recipients, bounce handling, reply routing, provider logs, and the critical alert paths that depend on mail.

Who should own this decision?

The site administrator should own the decision, with provider, billing, security, mail, or hosting owners involved when their systems are affected.

What should stop the rollout?

Stop when a setting changes spend, access, privacy, mail, queue, cron, cache, provider behavior, or WooCommerce behavior without validation evidence.

Related operations

• Use Incident Response Runbook when missed alerts affect production.
• Pair configuration work with Roles and Permissions.
• Review Approval Controls before enabling write-capable modules.
• Use Cost Allocation and Client Billing Review before client or team billing reviews.
• Use Security and Key Rotation before changing provider credentials.
• Use Cache Queue and Performance before scaling workflows or alerts.
• Use Scheduled Task and Cron Reliability before relying on recurring work.
• Use Provider Models and Fallbacks before changing production model behavior.