While BATV is a good technique, we've seen that there can be some limitations with it when combining it with an SPF policy. What else do we have to consider with BATV?
So, to summarize, make sure you make a list of possible things that can break before implementing BATV. Unintended consequences can be a major headache if customers start to complain and you have to re-roll out a feature.
PingBack from http://wordnew.acne-reveiw.info/?p=14386
C/R systems (and other auto-responders) are IMO not strictly incompatible with BATV, but could end up with sending a challenge for each mail where BATV uses a different envelope sender address. I don't mind to get *rare* challenges for mails really sent by me (SPF PASS).
In theory auto-responders could be modified to look at the "PRA" (SenderID) to disambiguate senders, while using the envelope sender address as destination for their auto-responses. But unfortunately that's one of those "worldwide upgrade" theories :-(