On Wed, Jul 12, 2006 at 09:27:34AM +0100, Philip Hazel wrote:
> On Wed, 12 Jul 2006, Angel Marin wrote:
> > Hosting providers might want to avoid users mangling with smtp codes on
> > their servers. If you allow your users setting aliases, then you'd now
> > be allowing them to change your servers' return codes.
> You mean when the host's admins control the Exim configuration, but
> other people are allowed to manage the alias files? Yes, I see that
> point. I'll see how easy it is to add an option to the router.
Is it worth treating this in a similar vein to the allow_fail, and
allow_defer settings of the redirect router. I mean, obviously you
have to have these allows to allow those settings to work correctly,
and you should probably default to allowing status codes, but it may
well be a good idea to be able to restrict back to the defaults within
the router.
Also, I'd be inclined to suggest that 421 and 221 are special, mentioned
elsewhere in the thread, and that for 421 in particular (I don't think you
should be allowed to specify 221), this causes the subsequent connection
close that a remote end should expect on seeing a 421. (I appreciate that
you've already committed some code, and if I have some time this week, I'll
be happy to produce the patch to do this).
Sorry to create more work over this.
Cheers
MBM
--
Matthew Byng-Maddick <mbm@???> http://colondot.net/
(Please use this address to reply)
