> One thing to remember though is that a message could be recieved from > MUA(Client) or fowarded from an MTA(Server). The 'Did you send > this' cannot > be sent to clients.
The rule for *not* asking DYST is "is there already a recieved: header in the message" this would imply it had been relayed by an MTA However.. imagine the situation where we have one SMTP listener dumping all of its reciepts into storage, and another spooling agent processing the storage and sending it on, the sending agent may not be listening on port 25 to recieve the DYST request... Perhaps we should draft an RFC after all and call it DYST for sending MTA's whereby we can disregard the fact that a sending MTA may not also be listening because we can say "implementing transport agents SHOULD listen on port 25 for the DYST command irrespective of whether or not they recieve SMTP email on this port" which would also cover the bases for one-way outbound gateways from private networks or other protocols. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
