Email verification tests become unreliable when every Kubernetes job shares the same inbox. One job can read another job's message, a retry can consume an old message, and cleanup becomes somebody else's problem. The failure usually appears as a random timeout, but the underlying issue is missing ownership.

I get better results when test mail is treated as an ephemeral infrastructure resource. A CI job leases one mailbox, writes the lease identity into its test context, and releases it when the job finishes. The mailbox is not just an address; it is a resource with an owner, a lifetime, and evidence.

Why a shared test inbox breaks CI isolation

Parallel CI is good at exposing assumptions. If five pods send verification messages to one inbox, each test has to guess which message belongs to it. Subject matching helps, but it does not prove that the message was generated by the current run.…