feat(email): role addresses are real — security.txt published, placeholders removed, From default fixed #5554
ccantynzAI Reviewcommented 5d ago
AI Triage
(no summary)
Priority: medium Risk area: mixed
Suggested labels: (no label suggestions) Suggested reviewers: (no reviewer suggestions)
Suggestions only — nothing has been applied. The PR author stays in control.
gluecron[bot]🤖 botAI Reviewcommented 5d ago
AI review unavailable
The platform's AI balance is exhausted, so AI generation is temporarily unavailable. Nothing was lost. You can queue this as a repair for the internal agent from the repository's Health page, or try again once the balance is restored. The PR is otherwise unchanged.
Cross-repo impact
See what breaks downstream if this PR merges.
⮌ Merged
This pull request was merged into main.
c comment · e edit title · m merge · a approve · r request changes · ? shortcuts
The owner created the role mailboxes (security@, support@, notify@, postmaster@, abuse@, dmarc@ — aliased to a monitored inbox). This wires the code side:
security.txtat/.well-known/security.txt+ root fallback — Contact: security@gluecron.com, rolling ~6-month Expires computed at render so it can never quietly go stale. NoPolicy:line (it would have pointed at a nonexistent page); SECURITY.md carries scope and ground rules. The admin-security CC7.1 disclosure check flips green with an accurate description.EMAIL_FROMdefault becomesgluecron <notify@gluecron.com>, replacing the unroutableno-reply@gluecron.localthat real mail servers would reject the moment the Vapron rail is wired. notify@ over no-reply@: replies to a password-reset mail are occasionally humans in trouble.Typecheck clean; seo/legal/email suites 87 pass; design gate green.