Skip to content
SendPoint / Education
B2B security gateways

Barracuda IP delisting workflow

Distinguish a reputation listing from a recipient organization’s local policy.

SendPoint referenceUpdated 2 min read

Confirm the reported block

Start with the complete SMTP response and connecting IP. A Barracuda customer can apply local controls as well as reputation filtering. Use the removal process only when the evidence identifies an IP reputation listing, not as a generic response to every rejected message.

Repair before requesting removal

  1. Identify who owns the IP. For a shared ESP pool, ask the ESP to investigate and coordinate remediation.
  2. Check for unauthorized sending, exposed credentials, abusive recipients or other confirmed causes relevant to the incident.
  3. Stop the unwanted traffic and document the repair. Preserve the response and incident timeline.
  4. Use the official Barracuda Central removal form with accurate contact information and the real affected IP.

Track the outcome

SendPoint recommendation: retain the request reference and the time it was submitted. Follow the operator’s response and verify the result using subsequent legitimate delivery evidence. Do not promise a fixed removal time or repeatedly submit the same request without new information.

When the IP is not listed

Ask the recipient’s administrator to inspect the message log and identify the exact rule or verdict. Provide the message ID, UTC timestamp and original response. A local block or quarantine requires the customer’s authorized review; a reputation removal form cannot override that policy.

Sources