At 08:19 03-12-2008, Jose-Marcio Martins da Cruz wrote:
You can get the same functionality with a 251 reply code where the MTA
accepts the message and forwards it to the new address. It's a
redirection in the sense that the MTA is doing an address rewrite and
relaying or delivering the message to the new mailbox.
That's what I want to avoid : "accept and forward", mainly the "accept" part.
There is no need for a new reply code if the text after the reply code
is structured. You still have to determine how to relay the new address
back to the MUA as SMTP does hop by hop delivery. HTTP, on the other
hand, requires a direct connection between the server and the user
agent. Even if there is a proxy in the middle, the user agent still has
access to the HTTP reply code.
The idea is why, in this case, SMTP can't work the same way as HTTP ? The goal is, if wanted, be
able to not work in "store and forward" mode or ("hop by hop", as you say).
Asrg mailing list