Traffic a MailerQ node generates that is not mail verified

Every one of these is defensible and none is obvious from the outside, which is exactly why they belong in a catalogue a customer can read. Usage statistics go to the vendor periodically; the documentation says paid licences may switch them off, and this build accepts heartbeat-enabled rather than the documented heartbeat. Crash reports are produced locally and sent onward, with separate switches for each half — so "keep diagnostics, send nothing" is expressible. Resource fetching is the one with security weight: for messages built from JSON, the node requests whatever URLs the message references. The shipped blacklist covers loopback and one private range and misses 10/8 and 172.16/12 entirely, which on a node inside a customer's network leaves their internal services reachable from a template. None of this is hidden; all of it is undocumented in the places a customer would look.