Before you share the address
Pause at the point where name+shop@example.com makes filtering easy but plainly reveals name@example.com. Ask whether the relationship is temporary, whether recovery matters and what would happen if the address became public.
The checklist
- Test provider support
- Use tags for sorting
- Use aliases for privacy
- Avoid tags for critical recovery
Write down the purpose beside the credential. A label is small operational memory: it prevents a random-looking address becoming another mystery.
After the first message arrives
Confirm that the route works, that replies behave as expected and that important mail is not being forwarded somewhere unsafe. If the relationship grows, extend the lifetime before it becomes urgent.
Review without over-managing
Use plus tags for convenient sorting and real aliases for stronger separation. Review on change—not every day. Support varies across forms and mail systems.
Give the next relationship its own route.
Create an MXDuck alias