hornet icon

hornet

Interact with hornet API

Actions452

Compliance Filter → Compliance Filter Put

AI-generated

Summary

Update (PUT) a compliance filter rule for a given object (user, customer, or partner) in the Hornet Security API.

Inputs

  • object_id (required) — ID of the object whose filter rule is updated. Sent as a query parameter (e.g., ?object_id=123).
  • APP-ID (required) — Application ID issued by Hornet Security, sent as an HTTP header.
  • direction (required) — Direction of mail flow: 1 = INCOMING, 2 = OUTGOING.
  • action (required) — Action to take when the rule matches: 1=REJECT, 2=REDIRECT, 3=REROUTE, 4=BCC, 5=IN_CLEAN, 6=IN_QUAR, 7=IN_VIRUS, 8=OUT_NOTIFY.
  • criterion (required) — Type of criterion used for filtering: 1=ADVANCED, 2=HEADER, 3=BODY.
  • info — Description of the rule.
  • size — Maximum mail size in MB (values beyond the third decimal place are ignored).
  • action_details — IP/hostname or a semicolon‑separated list of email addresses, depending on the selected action.
  • priority — Rule priority; lower numbers have higher priority.
  • active — Boolean flag indicating whether the rule should be applied.
  • sender — Sender address to filter for (required when criterion = ADVANCED).
  • receiver — Recipient address to filter for (required when criterion = ADVANCED).
  • ip — IP address to filter for (required when criterion = ADVANCED).
  • hostname — Hostname to filter for (required when criterion = ADVANCED).
  • subject_contains — Subject text to filter for (required when criterion = ADVANCED).
  • attachment_contains — Attachment name to filter for (required when criterion = ADVANCED).
  • email_header_filter — Email header to filter for (required when criterion = HEADER).
  • email_body_filter — Email body to filter for (required when criterion = BODY).
  • recipients_amount — Maximum number of recipients allowed (required when criterion = ADVANCED).

Output shape

The raw HTTP response from the Hornet Security API, typically containing the updated compliance filter rule or a success status.

The node also supports standard request options such as batching, SSL handling, proxy, and timeout, which can be configured via the node’s request‑options UI.

Links

Discussion