Name the two destinations in your application
Changing the email address on a user record is more than sending a confirmation. Until the new address is accepted, your application has an established destination and a pending one. A tester who watches only the new inbox can miss an incorrectly routed warning or a premature change in the account. Choose receiving access that lets you inspect both sides of the workflow while the relevant events are still observable.
This is a test of your own application, not instructions for changing a 99MAIL provider account. Give the destinations neutral fixture labels such as OLD and NEW. Both should be addresses you are permitted to control for the approved test. Do not use a colleague’s real mailbox or another person’s existing identity to manufacture the scenario; those choices would add privacy and authorization problems unrelated to the feature.
Agree when the product treats the change as complete
OWASP’s email-change guidance recommends reauthentication, notification to the existing address and confirmation of the new one. Turn your product’s chosen design into explicit states: established, change pending, confirmed or cancelled. Some higher-risk designs may also require confirmation at both destinations. Test the behavior your team actually approved rather than assuming every application should use the same sequence.
The acceptance record should say which address receives routine messages in each state. For the hypothetical product here, ordinary notices continue to OLD until NEW is confirmed. A warning goes to OLD when the change is requested, and a confirmation request goes to NEW. No real user information is needed; use a synthetic project and non-sensitive text to make incorrect routing immediately recognizable.
Use a destination table to expose premature switching
Suppose a small owned learning portal lets a synthetic participant move from OLD to NEW. Request the change after the product’s required reauthentication. Before opening the new confirmation link, trigger one harmless lesson reminder. The expected destination is OLD. Record whether OLD received the warning and reminder, and whether NEW received only the pending-change confirmation. A successful confirmation email at NEW does not excuse a missing warning at OLD.
Next complete the approved confirmation route. Trigger another reminder with a different run marker. Now NEW should receive it under this invented specification. Keep the earlier OLD message identifiable by its event. Your four-event record covers the warning, pending confirmation, reminder before confirmation and reminder afterwards. Read destination and product state together for each event; a screenshot of the changed account address alone cannot establish that the notifications followed the right route.
Exercise cancellation and replacement without mixing fixtures
A cancelled change needs its own clear result. Start a fresh pending change, cancel through the application’s supported route and confirm that OLD remains established. Attempting the cancelled confirmation link should have the declared safe result, without switching the address. Use a controlled synthetic user; do not repeatedly send notices to a real recipient who has not agreed to take part.
If the product allows a new pending destination to replace another, add a third controlled address only for that case. Label the first candidate NEW1 and its replacement NEW2. The first link must behave according to the application’s stated replacement rule. This creates a genuine need for another destination; buying three addresses for every simpler test would not. Keep your application event log free of complete confirmation tokens or URLs.
Choose independently observable destinations
For this test, independent destination identity matters more than folders or a tidy combined inbox. Two aliases might be sufficient if your lawful receiving setup distinguishes the actual destination reliably; two apparently different addresses are insufficient if the view hides which one received the message. Never assume a candidate 99MAIL offer supports aliases, recipient detail or a combined view. The listing and exact provider documentation need to establish those capabilities.
Ask whether both destinations can be read, whether the required messages remain available through the transition and whether private evidence can be kept legitimately. Note which of those three answers the listing states outright and which it leaves you to assume. A setup that loses the earlier warning before review is a poor fit for the four-cell method even if the latest confirmation works.
Make the order check narrower than the release test
Compare 99MAIL mailbox listings against the actual two-destination requirement: two independently readable mailboxes, plus a third only for the replacement case. Use them within 99MAIL’s terms and the operating provider’s rules. There is no pre-purchase store chat on rStock. If a listing leaves provider identity, authorized control or receiving visibility unresolved, choose a clearer listing, use an existing suitable mailbox arrangement or defer.
After a purchase, the order’s delivery record lets you check what access was supplied against the description. Any item mismatch belongs in a timely order dispute, following the displayed deadline and current rules. Routing defects in your own portal belong in its development record, with OLD/NEW labels and redacted evidence. 99MAIL and any operator behind it are unrelated to rStock, which is an independent marketplace. Passing this test supports the declared change route; it does not establish every recovery or sign-in behavior.