At 10:54 AM +0200 4/7/03, Claus Färber wrote:
> And when the message turns out to be addressed to an alias or forward
which points outside that MX'es domain?
There's no reason why it could not work in this situation: You hold off
the "OK" until you know that the message has been delivered, delivery
has failed /or/ a timeout has been elasped.
1. The whole point of having dumb SMTP front ends is for performance.
If they have to sit there and wait until the back-end is done
processing the email, you've kind of lost that benefit.
2. This assumes secondary MXs always know all of the legal email
addresses. (I assume you aren't suggesting that a secondary MX wait
to respond until the primary is back up again.) We've had this
discussion before. Lot's of secondary MXs do not know what addresses
are legal.
3. It's a major architectural change. It sounds very easy to say
"don't return bounces", but clearly it requires rewriting major
pieces of code in every MTA out there.
--
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