SMTP error 553, RFC 822, and Barracuda Spam Firewall

Posted by on Jan 27, 2011 in Uncategorized | 3 Comments

We recently had a strange issue where a script that creates and then emails a file to a user began failing.  It was strange in that the script had been in production for over two years, and there were no changes to the system on which it runs in that time.

In testing, we found that our Barracuda Spam Filter was refusing the mail with an SMTP 553 error code:

553 Requested action not taken: mailbox name not allowed

After some poking around, we found that the Barracuda’s firmware had been recently updated to v5.x, which includes a new option to enforce RFC 822 (ironic as the RFC is from 1982!).  The upshot seemed to be that email addresses (of both senders and recipients) need to be enclosed in angle brackets, or they are considered to be invalid addresses.

So if the email address is

user@example.com

Change to

<user@example.com>

Obviously, for scripting purposes, you’ll need to enclose the address in double quotes, and escape the quotes themselves.  Good times!

  • Allan

    Thanks for posting this. Was trying to figure out why I was getting this error with a new Barracuda and found the answer here :)

    FYI if anyone’s looking at disabling the RFC822 (it’s actually recommended by Barracuda) you can do this from Advanced > Email Protocol > Enforce RFC 821 Compliance

    Cheers,
    Allan

  • Tom K

    Allan,

    Glad the site had the info you needed. Thanks for posting the info on disabling RFC822 compliance.

    Tom

  • Mark Pippin

    I also want to thank you for this post. A customer’s Barracuda suddenly started blocking all external email or nearly all.

    I was nearly at a loss until I found this via Google. I was born 2 yrs after that RFC was released and I have never seen any reference to the requirement of enclosing mail from / rcpt to in .

    In fact, numerous reference websites with instructions for testing smtp from telnet omit the : http://www.yuki-onna.co.uk/email/smtp.html

    Apparently Gmail and many other mail providers omit the . An email from a gmail account getting bounced is why I was looking at the issue to begin with.