OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: Re: Virtual won't deliver local
From: Bruno L. F. Cabral (brunoopenline.com.br)
Date: Tue Mar 21 2000 - 08:31:58 CST

Hi there

seems you're facing the same question than me, on the thread
"expanding virtual_maps"

> The two ways I tried to solve this are:
>
> 1. Make example.com a local domain:

> 2. Make example.com a virtual domain:

> Version 1. has the disadvantage that Postfix does not know if there
> userexample.com is valid before trying to deliver it. Thus, in case

you can use local_recipient_maps to avoid this problem using (1)

> Version 2, OTOH, is really a hack which requires a very special
> virtual map. Since the virtual maps will be driven by an LDAP
> database which will be used by several clients, we cannot put this
> kind of special hack into to DB, but rather have to patch the Postfix
> LDAP client, which is not a pleasant option either.
>
> I originally hoped I could do put like
>
> userexample.com userexample.com
>
> into the virtual map, meaning that this address will move to the next
> setp and handled locally, but this is not possible.
>
> Is there a "nice" solution to my problem?

it was suggested on my thread using a transport map to solve the problem.
by testing, seems that I'll loose the virtual rewrite stuff if I use the
transport map, what would be avoided I stick with mydestination

my temporary solution is a mix

use local_recipient_maps to tell postfix which users are local or not
(I included the virtual_maps and maildrop's userdb.dat file), then
use virtual_maps to do rewriting, If needed, but don't include the

virtual.domain whatever

line. that way you'll avoid the non-listed users being reject as 'unknown'

finally, list the virtual domains on mydestination, and fallback_transport
as cyrus (maildrop on my case). this setup is working here on my testing
machine without problems until now

what I didn't clear undestand is if transport_map can be used (perhaps
with virtual.domain local: instead of virtual.domain maildrop:) instead
of mydestination to mantain the virtual_maps rewrite. perhaps someone
can clarify me on this

(the big problem on using mydestination is that your alias_map becomes
global, which I feel not confortably with. transport_map seems a clever
solution)

that my $0.02

!3runo

> Robert