On 2/6/06, Tony Finch <dot@???> wrote:
> On Mon, 6 Feb 2006, alexis wrote:
> >
> > - Forwards can be only configured to send to local domains
> > My users can set up forwards but the destination of the forwarded
> > email can be only on example.com
>
> That's something you should probably configure in your system for
> configuring forwarding. If your system is just letting users create a
> .forward file then it gets complicated. You can probably hack somthing
> together in the routers, e.g. (based on the default configuration), add
> the following to the userforward router:
>
> address_data = forwarded=yes
>
> and the following to the start of the routers:
>
> check_forward:
> driver = redirect
> domains = ! +forward_ok_domains
> condition = ${extract {forwarded}{$address_data} }
> data = :fail: Address forwards to invalid domain
> allow_fail
actually, i forgot to mention this, im configuring the forwards on a
mysql table. and i have a router like this
mysql_forward:
driver = redirect
data = ${lookup mysql {SELECT forward FROM users WHERE
domain='$domain' AND username='$local_part' AND forward != ''}}
and this query returns the forward address configured by the user.
>
> > - beside smtp authentication, i want to check (i know this is weak)
> > that the sender address is one of my local domains.
> > By now after a successfull smtp authentication, im able to send
> > messages with any FROM
>
> deny
> authenticated = *
> senders = ! +valid_sender_domains
>
> Tony.
> --
> <fanf@???> <dot@???> http://dotat.at/ ${sg{\N${sg{\
> N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\
> \N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}
>
