Barracuda Email Gateway Defense setup

Barracuda Email Gateway Defense: SPF fails for outbound mail

The envelope sender's SPF record may not authorize the Barracuda region that sent the message.

Problem description

The visible symptom is:

Authentication-Results: spf=fail smtp.mailfrom=example.com

Check the sending domain

Fix the SPF failure

  1. Confirm the message actually left through Barracuda Email Gateway Defense.
  2. Read smtp.mailfrom or Return-Path in the failed message. SPF is checked for that domain.
  3. In Barracuda, copy the SPF include for your account’s region.
  4. Add it inside the existing v=spf1 TXT policy before the final all mechanism.
  5. Keep one SPF policy at that DNS name. Do not replace other senders that are still active.
  6. Send a new message and confirm spf=pass for the expected envelope domain.

Common causes

The include is missing, belongs to another Barracuda region, was added after -all, or was published at the visible From domain instead of the envelope sender domain.

What the check proves

MailFixIt can find duplicate policies, invalid syntax, missing includes, and public DNS failures. A pass still requires the message to use the Barracuda route you authorized.

Frequently asked questions

Which Barracuda SPF include should I publish?

Use the include listed for your Email Gateway Defense region and account. Barracuda uses different outbound ranges by region.

Should I copy a DNS value from another company?

No. Use the value shown for your own tenant, region, and mail route. Preserve every other service that still sends or receives mail.

Related email diagnostics

Primary sources: Barracuda: Configure outbound mail scanning and SPF.