BATV and Out of Office


I am trying to troubleshoot a problem we are having at a customer site. This particular customer is having issues with receiving OOO (Out of Office) replies from one specific client. This is a big problem for them as it delays a lot of work when then await replies from people who are offsite etc.

After troubleshooting on our customers side we have found that it is the BATV function of the Sonicwall E-mail Security gateway which causes these messages to be dropped. We do not see them as Junk etc, in the Email Security GUI but the admin on the client side has found these error messages in his maillogs:

Mailserver on client side:
552 Unable to process message: msg.1257926399.602572.29394 - error: recipient: xxxxx@xxxxn.nx failed, reason: Giving up on 550 5.7.5 BATV failed to verify

Mailgateway on client side:
error: recipient: xxxxx@xxxxn.nx failed, reason: Giving up on 550 5.7.5 BATV failed to verify

After i turn off the BATV setting in the Sonicwall E-mail Security gateway the OOO messages are delivered from the client. I am unable to figure out where this domain could be blacklisted or something to that extent. And ordinary messages are delivered from the clients domain as normal.

Has anyone experienced this on the Sonicwall E-mail security or could help point me in a direction for troubleshooting this issue?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

This may well be due to the change of behaviour in Exchange 2007.

See my article with reference to RFC and changes to meet the guidelines for these special types of messages (OOF). Basically these messages are sent with no 'Envelope From' field (blank from) and this can cause some devices to reject.

There is nothing you can do on Exchange to alter that setting as far as I know,


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
AskCentricAuthor Commented:
Is it likely that implementation and use of BATV is so scarce that the external client of my customer has not encountered this issue before?

You don't see BATV failures very often no, I can think in the last two years, I've seen one other instance where mail was rejected with this status code.

It is normally smarthost providers that will reject certain types of mail that have no Return-To address sent, in which case you can normally send using DNS to bypass this restriction.

Mail servers should not reject mail that has no Return-To address, as it is a legitimate method for special types of messages such as OOF's.

Jamie McKillopIT ManagerCommented:

What you are seeing is a known issue -

As I thought -"BATV will drop an NDR or Out of Office reply if the mail from address is a NULL value."

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.