What we've
discussed, over and over, is the fact that you can't always know the
final recipient at the time of receipt (even though you may know it's
a valid address). I don't see the need for us to go into it over and
over again.
Did I miss something? Anyway, even if you can't always know, the important
question is how often you can know, what can you do to know more often and
what you do when you really can't tell.
.forward's were one thing. The other is a standard system where the
gateway mail system is outside of the firewall, but additional
delivery is done inside the firewall.
One can do "callforward recipient verification". It's perfectly possible -
it might be *way* expensive. Or the outside mail system can access the same
data as inside systems - one way or another. The problem isn't inherent in
SMTP is it? but in the way admins have traditionally set up multi-tier mail
systems. It's an implementation thang.
But anyway. I'm just don't see that this conversation is generating
anything except heat.
I don't know, it seems pretty good-natured so far - and there are (IMHO)
important implications for reliability in an MTS implementing anti-spam
stuff.
Of course the discussion has veered away from the thread subject a bit.
--
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg