>The big problem I have with SAV is when the sender uses a b0rked up >domain (like [EMAIL PROTECTED] and Postfix can't resolve or >SMTP to weblist.example.com)
... so postfix rejects with a 4xx, which is not what I said in my previous msg. @sender.domains that are SAV-rejected with 5xx should be harvested into a restriction class so SAV is applied only to these domains. In your case, the 4xx reject of non-responding MX for weblist.example.com would not be in the harvested list of 5xx domains, so it would not be SAV'ed. >or the valid email is from a sender address that does not exist >(like [EMAIL PROTECTED]). if the MX for example.com says donotreply account does not exist, this is an exception to legit send-only addresses. With SAV in warn mode for a couple weeks, you have to pick these out manually and OK that specific address in a from_senders_SAV_except.map that is call in the restriction class just before the SAV check. Len
