On Thu, Jun 29, 2006 at 04:55:18PM +0100, Philip Hazel wrote:
> > On Thu, Jun 29, 2006 at 12:10:14AM +0100, David Woodhouse wrote:
> > > 
> > > Cute idea, but I don't like the implementation much -- it would be
> > > better for it to be available in a general fashion from ACLs.
> > 
> > I looked at that first.  However, since (AFAICT) the ACL system works in a
> > accept/reject/defer logic, my understanding was that a fourth command would 
> > had
> > to be added to the underlying code specificaly for this feature.  Is this
> > appreciation correct?
> 
> I am watching this thread, but my first feeling is that it is totally 
> against the overall Exim "approach" to put it where you have. Deciding 
> what local parts mean (alias/mailinglist/local login/etc) happens in 
> routers, and it doesn't seem right to hard wire it into the smtp_in 
> module unconditionally. (Can't remember if you checked the domain, but 
> that needs flexibility too - not all domains are the same.)

What do we check in the domain, just that it belongs to us?

> As to your question above, I'm not sure what you are asking. There are 
> only the three possibilities (accept/reject/defer) that one can give to 
> a RCPT command. What is the fourth that you are thinking of?
> 
> I haven't spent much time looking at this, but if you just want to give 
> a particular 5xx response to a RCPT command when a user sets up a
> .redirect file,

Yes, that's precisely what I want.  Technicaly it's a reject, just with a
particular code (551).

> what is wrong with a router like this? Not tested,
> not even syntactically correct, but I think it should be possible to do
> it:
> 
> redirect_special:
>   driver = redirect
>   check_local_user
>   require_file $home/.redirect
>   condition = ${a hairy condition that reads the file, picks the domain
>     out of the address, and checks it against +local_domains for not 
>     being local}  
>   data = :fail: Not local, try ${readfile{$home/.redirect}}   

Ok, I'll try to do it this way.  Is there any documentation around for the Exim
config file interface?  In particular, does ${readfile} support proper parsing?
(remove # comments, trailing newlines, empty lines, etc)

> OK, it may give the wrong 5xx code - there are wish list items about 
> that kind of problem.

Could you give me a reference to these items?  I'd help with them if I can.

> Final thought: how many users are going to appreciate the difference 
> between .forward and .redirect, or were you thinking that sysadmins 
> would create those files?

I was thinking of users (those who know what .redirect means, of course).  For
sysadmins, we could have the same syntax extension for /etc/aliases that
Sendmail does (see my other mail about this, in this thread).

-- 
Robert Millan

-- 
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details 
at http://www.exim.org/ ##

Reply via email to