RFC 1985:SMTP Service Extension ...
RFC-Ref

start


Click on the red underlined text to get to the source

... valid attempt to address the problem of having to start the processing for the mail queue on a remote machine. However, the TURN command presents a large security ...
... ("receiver-SMTP") start the processing of its mail queues for messages that are waiting at the server for the client ...


... ETRN, with a single parameter that specifies the name of the client(s) to start processing for; (4) no additional SMTP ...


... currently exist with the TURN command. The security loophole is avoided by asking the server to start a new connection aimed at the specified client ...
... SMTP implementations. In addition, as this command will take a single parameter, the name of the remote host(s) to start the queues for, the server can decide whether it wishes to respect the request ...


... connection, the client may request that the server start to process parts of its messaging queue. This processing is performed using the existing ...


... by the client host when it wishes to start the SMTP queue processing of a given server host ...
... node, multiple ETRN commands may be needed to start the processing for the node as it may be listed at the remote site under multiple names. This can also be addressed using the ...
... Otherwise, the server host should force its retry queues to start sending messages to that remote site, using another SMTP connection ...


... A "minimal" client may use this extension with its host name to start the queues on the server host ...
... cases where mail for 'x.y' is sent to 's.x.y'. A minimal server may use this extensions to start the processing of the queues for all remote sites. In this case, the 458 error response ...
... queues for all remote sites. In this case, the 458 error response will not be seen, and it should always return the 250 response as it will always try and start the processing for any request. ...



Google
Web
RFC-Ref