>Another related question. Does SAV pay any attention to the ReplyTo: >field when seeing if the sender will accept email?
SAV uses the envelope sender to see if its MX will accept it as a recipient > I'm having a lot of >list failures. SAV is great except for this and the fault is probably >the way people set up list servers, not SAV. all the isp-* and other lists work fine with SAV, but announcement lists, www servers with mail cgi's, .mil, airlines, reservations, e-commerce sites, have to be whitelisted. They all "should" accept bounces (which is another way of saying what SAV tests) but they don't, so white list them. >It may be just trying to >send to the From: address instead of the Reply-To: if there is one >there. Either way, a lot of valid list email is getting caught by SAV. whitelist >I assume "Reply-To: [EMAIL PROTECTED]" is why this list passes right >through SAV. IMGate list is correctly set up, and it's envelope sender is a valid recipient. >How is everyone handling this? It looks like manually white listing >might be the best answer. only answer To keep an eye on SAV rejects, in my "advanced" config, I made a script that prints out two fields from the SAV reject lines, sorted by ip of MTA: sendingMTA [EMAIL PROTECTED] and emails that every hour. It's pretty easy to see what's junk and what's not. I've also made another script that harvests the [EMAIL PROTECTED] of SAV undeliverable rejects (the sender.domain's MX said the account does not exist) to a .map file from_senders_undel.map: [EMAIL PROTECTED] 554 ACL from_senders_undel Not sure whether that is worth it, I'm still evaluating. Len
