A consumer connecting by the binding's address meets a certificate for mail.novox.be and refuses it — found live by the forwarder's cutover proof, one send before production would have. The TLS name is mailu's own fact (HOSTNAMES), so the binding carries it; consumers say ${bound:smtp:name} and verification holds. de-spiegel can adopt the same key in its own time.
A consumer connecting by the binding's address meets a certificate for `mail.novox.be` and refuses it — found live by the forwarder's cutover proof, one send before production would have. The TLS name is mailu's own fact (`HOSTNAMES`), so the binding carries it; consumers say `${bound:smtp:name}` and verification holds. de-spiegel can adopt the same key in its own time.
A consumer connecting by the binding's address meets a certificate for
mail.novox.be and refuses it — found live by the forwarder's cutover
proof, one send before production would have. The TLS name is mailu's
own fact (HOSTNAMES), so the binding carries it; consumers say
${bound:smtp:name} and verification holds.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A consumer connecting by the binding's address meets a certificate for
mail.novox.beand refuses it — found live by the forwarder's cutover proof, one send before production would have. The TLS name is mailu's own fact (HOSTNAMES), so the binding carries it; consumers say${bound:smtp:name}and verification holds. de-spiegel can adopt the same key in its own time.A consumer connecting by the binding's address meets a certificate for mail.novox.be and refuses it — found live by the forwarder's cutover proof, one send before production would have. The TLS name is mailu's own fact (HOSTNAMES), so the binding carries it; consumers say ${bound:smtp:name} and verification holds.