Repository navigation
Provide a restricted sender for automated business email #5529
Description
🤖 Generated by the Agentic Engineer
Summary
Provide the configured dedicated sender for business automation.
Motivation
The business site needs to send password resets, announcements and other automated messages to the maintainer or intended clients. Its sending credential should remain independent of personal mailbox and administrator access.
Proposed Solution
Manage the sender, its restrictions and its recovery declaratively. Keep activation disabled until the native server and deployed delivery checks pass, and define how replies and delivery failures reach the maintainer.
Acceptance Criteria
- Declare the dedicated sender and its disabled and enabled states without changing existing accounts, retained messages or the restricted agent route.
- Use a separate, narrowly permitted service credential in approved custody, with verified independent recovery and idempotent recreation.
- Enforce the sender identity in both the SMTP envelope and message headers; reject missing, ambiguous or incorrect identities in actual native-server tests.
- Preserve authenticated transport and delivery limits, and prevent mailbox or administrator access through the sending credential.
- Define and verify receiving, reply and delivery-failure behavior, including maintainer visibility.
- Verify actual delivery to the approved maintainer destination and document the business-site integration contract.
- Complete current-head validation, substantive review, protected merge, publication and deployed readback before activation is called delivered.
Alternatives Considered
A dedicated service identity keeps automation credentials and their lifecycle separate from human sign-in.
Additional Context
Part of #5030. Company Email identity, encryption and custody are tracked in #5387. The producing application is tracked in devantler-tech/business-site#374. Size: Medium.
Superseded by #5400; retain all delivery work on that original issue.
Activity
coderabbitai commentedon Oct 28, 2026
🔗 Related PRs
#5367 - fix(mail): stage storage and verification before administration [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
devantler commentedon Oct 28, 2026
Duplicate of #5400. The original issue already covers this sender and remains the business-site dependency. Additional acceptance detail has been consolidated there.