History

tegwick f69291659c Some checks are pending CI Smoke / container-smoke (push) Waiting to run Details CI Smoke / host-smoke (push) Waiting to run Details Transactional mail acceptance / mail (push) Successful in 27s Details Build and Publish Container Image / build-and-push (push) Successful in 10s Details Pin reviewed verification candidate and record exact live activation gate Assistant: codex Assistant-Model: gpt-6.1-sol Assistant-Session: 01a11538-05ea-7b63-b3c7-a2df5f38898d		2026-10-07 19:35:39 +02:00
..
clustersecretstore.yaml.template	Reserve verification sends durably across retries and restart	2026-10-07 19:04:48 +02:00
configmap.yaml	Record verified P05 rollout and service recovery acceptance	2026-09-13 22:31:16 +02:00
deployment.yaml	Pin reviewed verification candidate and record exact live activation gate	2026-10-07 19:35:39 +02:00
externalsecret.yaml	fix(security): prevent ESO copying source annotations (CUST-WP-0073)	2026-09-28 15:56:50 +02:00
kustomization.yaml	Complete EMAIL-WP-0004 transactional invitation mail delivery.	2026-08-12 13:32:11 +02:00
namespace.yaml	Complete EMAIL-WP-0004 transactional invitation mail delivery.	2026-08-12 13:32:11 +02:00
networkpolicies.yaml	Complete EMAIL-WP-0004 transactional invitation mail delivery.	2026-08-12 13:32:11 +02:00
openbao-eso-token-apply.sh	Reserve verification sends durably across retries and restart	2026-10-07 19:04:48 +02:00
pvc.yaml	Complete EMAIL-WP-0004 transactional invitation mail delivery.	2026-08-12 13:32:11 +02:00
README.md	Reserve verification sends durably across retries and restart	2026-10-07 19:04:48 +02:00
service.yaml	Complete EMAIL-WP-0004 transactional invitation mail delivery.	2026-08-12 13:32:11 +02:00
serviceaccount.yaml	Complete EMAIL-WP-0004 transactional invitation mail delivery.	2026-08-12 13:32:11 +02:00

README.md

email-connect transactional receiver — railiance01

The receiver permits user-engine invitation and registration-verification calls, using fixed templates and bounded SMTP/STARTTLS. Its persistent SQLite store contains delivery/challenge evidence; SMTP acceptance is not inbox receipt or authorization. Current release review: ../../../docs/verification-retry-review-2026-10-07.md.

Target: railiance01, cluster kube-system UID a553c742-0115-43d4-99a4-a5ca56fe0786. Observe through ~/.kube/config-railiance01; change the cluster through ssh railiance01 and the founder's exact live go. config-hosteurope is the retired cluster and must not be used. Read the-custodian/docs/agent-environment-orientation.md first.

Platform owns OpenBao custody, Kubernetes-auth ClusterSecretStore openbao-email-connect and its scoped ESO ServiceAccount (RPF-WP-0045). ExternalSecret email-connect/email-connect-runtime delivers the existing EMAIL_CONNECT_INGEST_TOKEN, EMAIL_CONNECT_SMTP_USERNAME and EMAIL_CONNECT_SMTP_PASSWORD fields. Never read or print Secret objects/annotations. Route needs through warden route find/show email-connect-transactional.

The static ESO token bootstrap and duplicate store template are retired. Do not recreate external-secrets/openbao-email-connect-eso-token or apply a store copy from this repo. Custody and store mutations require the platform lane.

Stable URL: http://email-connect.email-connect.svc.cluster.local:8080. Default-deny NetworkPolicy permits only user-engine:8080 ingress, DNS and public SMTP:587 egress. No additional caller admission is part of an image correction. ConfigMap owns host, port, sender and portal URL; no provider credentials belong in HTTP requests, Git, chat, State Hub or test fixtures.

After reviewing current live manifests and CPU headroom, perform client diff and server dry-run for the exact digest change. Preserve live resource ownership; apply only that reviewed image change from this owner repo after founder go. Observe Ready/probes and an isolated no-send authenticated rejection before calling the release successful. Do not recreate secrets as a workaround.

Before the verification correction, capture SQLite with its backup API into a private mode-0600 artifact. Keep PVC evidence intact. Do not run rollout undo with sending enabled: an older image ignores verification_attempts and may resend an uncertain operation. Stop the receiver first and reconcile unknown reservations; roll forward with the invariant preserved where possible.

Local regression harness: tests/harness/README.md. It uses synthetic addresses and loopback SMTP/IMAP only; no production mailbox or message send is a test.