The five myths
- It makes you anonymous
- It stops every phishing message
- It removes the need for strong authentication
- Every address should be temporary
- More addresses always mean more confusion
What is actually true
Treat public contact as infrastructure designed to absorb exposure. That can reduce correlation, improve context and make one exposed relationship easier to replace. It is a control surface, not an invisibility cloak.
Why the distinction matters
A genuine collaboration sits beside hundreds of automated pitches. The address can tell you which relationship is involved, but it cannot certify the sender or erase information shared elsewhere.
Good tools solve a named problem. Myths ask them to solve every problem.
Use the modest superpower
Reply behaviour can expose an underlying address if the service does not preserve the alias.
- Publish a dedicated route
- State useful contact boundaries
- Check reply identity
- Replace it when abuse wins
Give the next relationship its own route.
Create an MXDuck alias