On Mon, Jun 05, 2006, David Nicol wrote:
The idea if implemented would ease content-based filtering at the
server as messages to multiple recipients would no longer require
separate complete transactions for each recipient when sending to
servers that implement complex per-recipient acceptance policies.
When a server identifies itself as supporting the DATAFIRST
extension, the SMTP transaction may be re-ordered from MAIL FROM,
RCPT TO, DATA to MAIL FROM, DATA, RCPT TO
with the full range of acceptance/delivery status response codes
available at RCPT TO time rather than at the end of the DATA
command.
Why not support the RCPT status model of LMTP? That way you get the
recipients at the start of the transaction and don't need to transfer
any messsage if there are no valid recipients and you can give a
per-RCPT status after the message has been sent:
RFC 2033:
4.2. The DATA command
...
The change is that after the final ".", the server returns one reply
for each previously successful RCPT command in the mail transaction,
in the order that the RCPT commands were issued. ....
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg