BATV is one of the security options used by email servers. In our case, on-premise MDaemon.
We use on-premise MDaemon with Email Security Cloud. We do not have SMG.
The only post here in the Community about this issue I was able to find was from back in '21. Guy who posted it used both SMG and SESC and found the solution for it, in SMG. So I thought theere may be equivalent option in Email Security Cloud, which I'm not able to find (we just started using SESC at that time).
So, SMG has no relevance to my case.
Thank you
-------------------------------------------
Original Message:
Sent: Sep 08, 2025 09:26 AM
From: Joyce Madero-Buquid
Subject: BATV, Recipient address rejected
First, BATV is not something in use in the Email Security Cloud but Address Registration is.
What exactly is the service that you are using? Based on your previous statement, you have an on-prem solution, SMG. Are you using both SMG and Email Security Cloud? With Email Security Cloud, you can always craft data protection based on your organizational needs.
Original Message:
Sent: Sep 05, 2025 03:22 AM
From: Aleksandar Devecerski
Subject: BATV, Recipient address rejected
Joyce
Openned the technical case and, after some back and forth, no solution (outside disabling Address Registration).
Their recommendation, submit suggestion to Ideas. Ideas doesn't have Email Security.cloud category available for this, but has the warning that ideas submitted in wrong category will be deleted. So I've openned non-technical case to see if this category could be added to Ideas. Or at least get support to relay notification about this to Email Security.cloud team. No luck with either one.
So, that's it.
Regards
Original Message:
Sent: Jul 16, 2025 08:13 AM
From: Joyce Madero-Buquid
Subject: BATV, Recipient address rejected
Hello,
Please open a case to have this further looked at.
Thank You.
Joyce
Original Message:
Sent: Jul 15, 2025 09:45 AM
From: Aleksandar Devecerski
Subject: BATV, Recipient address rejected
Hello everyone
We are in the process of evaluating Email Security.cloud and things are pretty much running as expected, no (major) issues. I was a little surprised with 3 day maintenance period over the weekend, but nothing was affected by it.
One thing though. We are using on-premise MDaemon email server with Backscatter protection feature turned on. Common name for it is BATV (Bounce Address Tag Validation) and the most obvious thing about it is that it adds verification tag to the email address looking something like prvs=12908dd3d3=user@mydomain.com. Recipient server after verification strips the tag and recipient sees usual user@mydomain.com. But in some cases recipient server responds to BATV address directly (auto-responses, mailing lists,...) and SES.cloud's Address Registratio feature rejects it.
Security Scan: Address Registration Service
Action: Blocked
Reason: Invalid recipient <prvs=12908dd3d3=user@mydomain.com> (#5.1.1)
I cannot register addresses like this, because BATV tag varies over time. Also registering prvs*@mydomain.com is not working.
Found thread here on the Forum, from 2021, addressing this very issue SMG 10.6.6 BATV Tags from SMG to SESS, but I cannot apply resolution mentioned in it, cannot find Bounce attack validation setting. Not mentioned in the Help either.
Anyone has idea how to handle this?
Thank you
Regards