Sahil Tandon:
> M Mollar wrote:
>
> > For my docent activity, I need to setup a transport like this:
> >
> > /(.*.dyn.nisu.org)/ smtp:[$1]:2500
> >
> > My students will setup a postfix server in their computers, but they
> > cannot listen port 25. I update dns dynamically, so the mail directed to
> > somestudent.dyn.nisu.org will be sent to the corresponding computer at
> > port 2500.
> > I understand that this is forbidden in the transport maps by security
> > reasons, but I don't know any other way to solve the problem.
>
> When you update DNS, use a script that updates the transport map and
> populates it with the appropriate hostnames and transport nexthops.
Yes, it hurts that regexps currently can't make safe substitutions.
You could use (requires Postfix 2.6 experimental release):
transport_maps = tcp:host:port
See tcp_table(5) for the description of this trivial protocol.
In theory it is possible to make regexp substitutions safe,
but this requires source code changes so that the application
can specify what characters are allowed in $number substitutions.
Wietse
