Skip to content

Prepare version-aware Email configuration and readback #5795

Description

@devantler

🤖 Generated by the Agentic Engineer

Objective

Make the existing Email setup recipe explicitly compatible with the tested legacy and 1.x runtimes, so the migrated service can be recreated from reviewed configuration.

Details

The native configuration, message-copy and rollback trials are complete. The checked-in compiler still targets the legacy schema. Add an explicit supported runtime selection while preserving the current serving defaults.

Checklist

  • Preserve the legacy recipe and reject unknown runtime selections.
  • Render and verify the 1.x field names, exact mailbox permissions, receiving aliases and client-address policy.
  • Bind the administration bundle and startup checks to the selected runtime.
  • Verify fresh setup, replay and refusal controls against both native versions.
  • Deliver through current-head validation and protected merge.

Dependencies

Part of #5387. Serving-store migration, encryption activation and single sign-on remain separately gated by their recovery and acceptance checks.

Notes

This records existing requested Email work investigated from 2026-11-02. This delivery stages compatibility; it does not switch the serving datastore or enable authentication changes.

Activity

  1. added theissue type on Nov 3, 2026
  2. coderabbitai commented on Nov 3, 2026

    @coderabbitai
    Contributor
    🔗 Related PRs

    #5586 - feat(email): verify live mailbox backup recovery [closed]
    #5533 - feat(email): move active credentials and recovery to infrastructure [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 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:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  3. moved this to 🏃🏻‍♂️ In Progress in 🌊 Project Boardon Nov 3, 2026
  4. self-assigned this
    on Nov 3, 2026
  5. added a commit that references this issue on Nov 3, 2026
  6. devantler commented on Nov 3, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    This records a child delivery within the already-started Email work in #5387. Its first investigation began on 2026-11-02 at approximately 22:17 UTC; the board's First started date preserves that start rather than resetting it to issue creation.

    At signed head 1515752dbc3c76bda8c596cad2639dc795c5c42f, the affected Go package, race checks and vet pass. Both checksum-verified UI bundles staged successfully. Isolated native trials with each matched server/CLI/UI combination completed fresh configuration and two replays, including receiving aliases. Initial native failures exposed a factory-resource URL mismatch and a test-credential validation issue; both were corrected and the trials rerun successfully.

    This proves configuration preparation with synthetic fixtures. Production migration, encrypted serving storage, restored user data, sign-in acceptance and external delivery remain separate acceptance work under #5387. PR #5796 delivers this child only.

  7. moved this from 🏃🏻‍♂️ In Progress to ✅ Done in 🌊 Project Boardon Nov 10, 2026
  8. added a commit that references this issue on Nov 10, 2026
  9. devantler commented on Nov 10, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Verified the published Email bootstrap for the protected merge of #5796 at 09423afd7727c5487071e7c5396ad0812551fc9d. The mail configuration source tree matches the revision exercised in the two native setup and replay trials. Merged-main validation and the bootstrap build and publish run both passed.

    An independent registry read verified the published tag's Cosign signature from the protected main workflow and matched the digest reported by that run: sha256:7b13b9820cf5aa5dbc3991452e131053dc9743b6ea7323d9ee993e4e2a59e489.

    This completes the publication check for the version-aware bootstrap. The serving datastore, production sign-in and recovery acceptance remain tracked in #5387.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Fields

Priority

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions