I don't understand your assertions... It is our nightmare .. We caused it?
If your donor receipt messages are sent with an envelope of [EMAIL PROTECTED] which is NOT a valid recipient to your MX, then the MX you send to that do SAV will refuse yr msgs. That's what I thought you could be describing.
We accept bounce messages. That account is not inactive.. It actually receives email but we ask emails to be sent to Support. If someone replies to the email it goes to support. It is not bounced.
ok, then the problem you are having is not one of sender_address_validation.
I do want to point out to you, and anybody else, that when these "apps" and "robots" and listservers send-only but refuse bounces, then they will be rejected by any MX doing sender address validation. And that problem is very easy to fix on your end, since it would be your end causing the problem
All I ask is if several hundred people's confirmation comes to our accounting for confirmation of the confirmation email before it gets delivered to the donor ... Would that not be a nightmare?
yes, if your donors are doing challenge/response defense on their mailboxes, then you will have a nightmare.
It is like a listserv where every member of the list asks a confirmation every time someone posts to it.
yep, obviously not workable.
To get around the challenge/response problem, you would have to have some kind of program alias that received the inbound mail for the donor sender address and tried to decide if it should respond to a challenge, but detecting that it is a challenge and not real msgs will probably be unreliable.
The type of sender address verification that IMGate does doesn't actually send a msg, it just contacts the MX of the sender.domain and does a
RCPT TO:<[EMAIL PROTECTED]>
... to see if the MX would accept the msg. SAV is essentially like SMTP VRFY but using SMTP RCTP TO:
btw, I don't think these challenge/response techniques are advisable, esp not at the server level, but they might work at the desktop level.
To alleviate your problem, another tactic you can try is to keep resending the receipts. The rejecting challenge/response mechanism should also be reporting the rejects to your dononrs, who would see your repeated rejects and whitelist you. That IS their responsibility, not yours. All you can do is keep re-sending in an attempt to get their attention.
Len
_____________________________________________________________________ http://MenAndMice.com/DNS-training: Denver; New York; Seattle IMGate.MEIway.com: anti-spam gateway, effective on 1000's of sites, free
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
