writes:
> I'd really like to get back to the main thing, which is how the
> client smtp can get to decide the form of the VERP, rather than
The client can get to decide right now. There's nothing to stop the client
from doing that.
> As a matter of principle, if the server smtp dictates the VERP
> form and screws up, the sender loses through no fault of his own
> (doesn't get bounce).
The server can also screw up the return address the client gives it, so,
what exactly are you trying to argue?
> The only hop that matters is the one to the target mx. Hops before
Why?
There's nothing particularly special about that particular hop that is not
present at any other time.
> and after are unimportant:
> Before the Hop, the message is in the senders domain, and if the
Not necessarily.
> admin has his wits about him, he will not let the recip list be
> exploded before the Hop. He wants to keep that option open.
> After the Hop, the message is in the recips domain, where it will
> need to be exploded anyway for individual recips.
Not necessarily. Ever seen headers on mail that's delivered to AOL? At
least one or two hops, before it's delivered to mailboxes.
> : > Main problem here is error handling, that your boolean-flag approach
> : > doesn't have.
>
> : Specifically what in regards to error handling are you referring to?
>
> It's a consequence of having multiple copies. The last 250 ok after
> DATA is meant to confirm ALL recips before, but what if I run out of
> disk halfway through.
This is not a new problem, and has been solved a long time ago.
> I have to reject all, and recovery is messy.
> But if the message preceded the recip list, then the 250 is for the
What are you talking about?
--
Sam
