Treat IPv6 as a production path, not a checkbox.
Before publishing AAAA or sending over IPv6:
- verify routing and firewall rules;
- bind SMTP to the intended address;
- configure PTR/reverse DNS;
- confirm forward DNS;
- update SPF where the address is directly authorized;
- test inbound/outbound SMTP;
- verify TLS;
- monitor reputation and failures separately from IPv4.
If IPv6 is broken, remove the advertised path until it is fixed rather than relying on every remote system to fall back cleanly.