At 12:43 PM -0700 4/8/03, Brad Templeton wrote:
Strictly speaking, a challenge/response tool does not send a "bounce" or
error message. It sends a challenge, which is a new piece of mail, and
does not indicate the earlier message failed. A proper c/r tool is holding
the mail in a spool, to be delivered once the response comes. A "bounce"
means delivery failed, and the user may need to try again, or give up.
Not entirely true. Many mail systems send notices that the message
is still in the process of being delivered, but hasn't yet. But
let's avoid the word "bounce" for a second.
I don't see why a challenge/response system is any different than any
other (non)-delivery notification. It's a notification concerning
the delivery of a message. Sure, it requires some action. But a
vacation notice or a straight bounce also requires some action if you
want to get the message through.
A C/R system MUST NOT challenge mailing list mail, for example, but a MTA
SHOULD send bounces/error reports on mailing list mail.
Why do you say that? We've all had the enjoyment of dealing with a
C/R system that did just that to this list. You clearly don't want
the challenge going to each member of the mailing list. It should go
to the list owner, who can deal with it as they wish (probably by
booting the subscriber--but that's up to them).
--
Kee Hinckley
http://www.messagefire.com/ Junk-Free Email Filtering
http://commons.somewhere.com/buzz/ Writings on Technology and Society
I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg