Allow restricted email-client Mail2News addressing

1 files changed, 19 insertions, 2 deletions

diff --git a/deploy/README.md b/deploy/README.md
index 5046bb5..055de1e 100644
--- a/deploy/README.md
+++ b/deploy/README.md
@@ -8,6 +8,22 @@ Apply the fragments from this directory through the normal configuration
 management or deployment process. They are intentionally not complete server
 configuration files.
 
+The legacy `qee4...onion` listener on Victor accepts one narrowly scoped
+email-client recipient form:
+
+```text
+mail2news-YYYYMMDD-group.one=group.two@mail2news.tcpreset.net
+```
+
+`qee-mail2news-access` permits only that dated syntax, with at most three
+validated-looking newsgroups. `qee-mail2news-aliases` rewrites only the SMTP
+envelope recipient to the exact private Mail2News onion address. The visible
+`To` header is preserved so Mail2News can perform authoritative date and
+newsgroup validation. Append the alias fragment to Victor's existing
+`virtual_alias_maps`; do not replace the other maps. This keeps the
+Victor-to-Diego leg on the client-authorized onion route and does not permit
+general SMTP relay.
+
 Deployment order:
 
 1. Generate a Tor v3 client-authorization key pair outside the repository.
@@ -17,8 +33,9 @@ Deployment order:
    M2Usenet host, mode `0600`, readable only by the Tor service account.
 4. Install and compile the Postfix maps, then validate Postfix.
 5. Validate Tor configuration and reload both services.
-6. Test unauthorized connection rejection and recipient restrictions before
-   deploying `send.php`.
+6. Test the dated Mail2News recipient and reject malformed, unrelated,
+   `_nospam`, four-group, and multi-recipient cases. Date freshness remains an
+   authoritative Mail2News check after message acceptance.
 7. Deploy the committed application revision and verify final NNTP
    publication with a controlled article.