Compatibility Target
Ruzor targets Pyzor 1.1.2 observable behavior for client and server commands. It preserves the digest algorithm, datagram shape, thread ids, request signing, ACL behavior, local whitelist behavior, and supported backend record formats.
Digest Flow
The Pyzor digest is designed to identify message content while ignoring volatile delivery details. Ruzor follows the upstream approach: discard headers, normalize selected body content, remove long noise tokens, strip email addresses, URLs and HTML-like tags, collapse whitespace, then hash the normalized payload.
ruzor predigest < message.eml
ruzor digest < message.emlUDP Request Shape
Requests and responses use RFC-822-style headers over UDP. Ruzor preserves PV: 2.1, the 8192-byte packet limit, operation headers, digest headers, and account signature headers.
Op: check
Op-Digest: 7421216f915a87e02da034cc483f5c876e1a1338
Thread: 1234
PV: 2.1
User: anonymous
Responses
| Field | Meaning |
|---|---|
Code | Server status code, commonly 200 for OK. |
Diag | Diagnostic text, commonly OK. |
Count | Number of spam reports for the digest. |
WL-Count | Number of whitelist reports for the digest. |
Entered and Updated | Record timestamps for report state. |
WL-Entered and WL-Updated | Record timestamps for whitelist state. |
Not Shipped
Ruzor covers the client and server package surface. It does not ship the Python-only pyzor-migrate helper.