Version 0.71.2

The server that runs NMTS no longer answers on the home network it is hosted on — only through the public path.

NMTS reaches you through one path — Cloudflare, then a tunnel into the machine — but next to it the machine also answered on its own local network, on a port meant for our deploy checks, and that second door skipped Cloudflare entirely, so behind it the caller could choose what address the server believed they were coming from: the value the request limit, the lockout after wrong account codes, the limit on messages to the postbox, and the free-trial limit per line added a day earlier all hang on. We measured it rather than assumed it: 140 requests under one made-up address earned the refusal, and changing one character of it was served immediately. The port is now bound so that only the machine itself can reach it, the deploy checks go in the same way, and a test reads every container definition in this repository and fails if any port is opened wider. The door was never open to the internet — and that never made it harmless.