Stop delivery to a target — or to everything verifiedimportantWritten by the Hub

A pause is an intervention that stops delivery while leaving the mail intact: messages wait in the sending queue and resume when the pause is lifted or expires. That makes it the right tool for "stop sending to this domain until we understand what is happening", which is a thing an operator wants at two in the morning and a control module should therefore expose properly. The fields the engine actually accepts are domain, tag, cluster and expire — and only those. The field is domain, though the column behind it is target: a body built from the schema is accepted and ignored, which is how our first attempt paused the entire cluster while naming a single domain. Measured again on 2026-09-19 while building the control module, one name at a time: domain and tag come back in the response, while to, target, remoteip, from and localip are all swallowed without a word and leave a cluster-wide pause behind. There is therefore no way to pause one sending address over REST — the console offers such a field, but the public API does not honour it. cluster: false scopes the pause to the node that received the call and stamps its server id; cluster: true, which is the default, applies it everywhere. expire is a Unix timestamp, and zero means forever. Removal matches on the fields, not on the id: {"domain": …, "cluster": false} removes the pause created with exactly those values. A DELETE that matches nothing still answers 200.