Yep, probably much better if you can do it at the MTA level.

In some cases people will still prefer to do this forwarding with DBMail
because they can leverage its administration frontends and external auth
database. This, too, can be done with Postfix and an external transport
map, but the details are left as an exercise to the sysadmin :-P

On Tue, 2007-03-27 at 10:38 -0500, Bret Baptist wrote:
> Sorry about the other mail, here is the full version...
> 
> On Tuesday 27 March 2007 10:04:03 am Aaron Stone wrote:
> > On Tue, 2007-03-27 at 16:40 +0200, Marc Dirix wrote:
> > > > dbmail-users -x @domain -t [EMAIL PROTECTED]
> > >
> > > Does this not replace the original recipient address with
> > > [EMAIL PROTECTED]
> > > So the internal can not distinct users anymore?
> >
> > Both remain active, and the aliases table looks like this:
> >
> > alias     | deliver_to
> > --------------------------------------------
> > @domain   | 30
> > @domain   | [EMAIL PROTECTED]
> >
> 
> There is another way to handle this without knowing the destination alias on 
> the internal server. Iif you are using postfix on the relay set up a 
> transport for the forward to the internal server.
> 
> So in your postfix main.cf add:
> transport_maps = hash:/etc/postfix/transport
> 
> In /etc/postfix/transport add:
> domain smtp:[xxx.xxx.xxx.xxx] (address of internal server)
> 
> Add the aliases in dbmail for each mailbox like above.  However instead of 
> the 
> second alias that goes to the internal server use @domain with a blank 
> deliver_to.
> 
> 
> I am not entirely sure about the order the trivial-rewrite daemon uses for 
> transport resolution so make sure you test this before you enable it.  We use 
> this same priciple to do relaying for some clients while still being able to 
> have addresses for that client in dbmail.
> 
> 
> Let me know if you have any questions.
> 
> 
> >
> > If there are multiple entries of the same type, they all get followed,
> > which is what we're doing here with multiple '@domain' entries
> > delivering to different destinations.
> >
> > Aaron
> >
> > _______________________________________________
> > DBmail mailing list
> > [email protected]
> > https://mailman.fastxs.nl/mailman/listinfo/dbmail
> 
> 
> 

_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail

Reply via email to