fix(kits): keep SMTP/IMAP mailbox addresses consistent with mail_domain #435

Problem

The SMTP/IMAP kit accepts a different mail_domain, but its two mailbox addresses remain hard-coded to environment.test. Both mailboxes refer to primary_domain, whose name is the substituted parameter. The published variation therefore produces an inconsistent mail inventory.

This predates PR #433: it exists in the 1.0.0 release and is retained by the proposed 2.0.0 release at head 1a551321c00fa36e0e50674639ad214929a4ef2d.

Reproduction

1. Compose infrastructure.smtp-imap-mail-service with its tests/composition.yaml variation, which sets mail_domain: alternate.test.
2. Parse the composition through the pinned raes==6.0.1.
3. Inspect nodes.<namespace>.mail.runtime.mail_services.

Actual:

• domains[0].domain_id: primary_domain, domains[0].name: alternate.test.
• operator_mailbox.address: operator@environment.test, domain_ref: primary_domain.
• service_mailbox.address: service@environment.test, domain_ref: primary_domain.

Expected:

• operator@alternate.test and service@alternate.test, consistently referring to the selected domain.
• The default composition continues to produce the two @environment.test addresses.

Affected content: kits/infrastructure.smtp-imap-mail-service/1.0.0/module.sdl.yaml and the proposed 2.0.0/module.sdl.yaml, plus their parameter-variation coverage.

Scope and ownership

Correct the kit's mailbox/domain relationship using RAES-owned parameter and realization semantics. Do not introduce pack-specific interpolation or extend SDL semantics here.

PR #433 reports that simply substituting operator@${mail_domain} and service@${mail_domain} reintroduces realization.authority-bound-unavailable under RAES 6.0.1. A fix must preserve bounded planning authority; if the current RAES contract cannot express the dependency, file and link a concrete upstream OpenRAE/rae issue before implementing the kit change.

Published releases remain immutable: ship corrected content in a new kit release.

Acceptance criteria

• Every accepted mail-domain value produces mailbox addresses consistent with the referenced domain.
• Regression coverage checks both the default and alternate-domain compositions, including the actual composed addresses and domain references.
• The correction does not reintroduce realization.authority-bound-unavailable.
• Any necessary upstream contract fix is separately tracked and linked; this repository continues to consume RAES semantics.
• The corrected release passes kit integrity, composition, and release checks.

Related

• PR fix(kits): release four kits with an open compute substrate #433: fix(kits): release four kits with an open compute substrate #433
• Parameter planning: Kit parameters inside runtime collections fail RAES planning #414
• Clarification of backend-independent acceptance: fix(kits): release four kits with an open compute substrate #433 (comment)
• Realize declared mail services lilrae#1238 tracks downstream mail realization, which is separate from this authored-content inconsistency.