Email fixtures are easy to create and surprisingly hard to retire. A CI job allocates an inbox, sends a verification message, and exits. When the job is canceled, times out, or loses its final callback, the inbox can stay around forever. After a few weeks, the test system has a quiet collection of stale addresses, unread messages, and records nobody can confidently attribute to a pipeline run.
The usual response is to add a shorter TTL to every inbox. That helps, but it does not solve ownership. A TTL is a deadline; it is not evidence that the cleanup happened. In AWS CI/CD work, I prefer a small reaper process that treats test email data like any other temporary cloud resource: tag it, observe it, expire it, and report what could not be removed.
The hidden cost of test inboxes
An inbox used by an integration test has more than one resource behind it. There may be a provider-side mailbox, a row in the test database, an AWS secret reference, a Docker job, and an artifact containing the message ID.…