Stefano,
> I wouldn't like the SMTP server to read the "code" that an handler returns
> and decide how to behave dependently on the first char of that code.
I agree with that concern, which isn't generally exposed in the my version
of the fast-fail proposal. In the case where I show a general case, it
would be the responsibilty of the customer matcher to properly handle the
reply and behavior back to the SMTP handler. Also, at that point I had
provided both numeric and text replies, so that the custom code could drive
off the numeric reply. If we wanted, I supposed we could even document and
use DSNStatus manifest constants. Once again, that would be part of the
plug-in's responsibility, not the core code.
By the way, did I miss a patch where you changed the bounce mailet? I'm
seeing the DSNStatus inner class still there, as well as the new copy of it
that is in mail/dsn/DSNStatus.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
