:-)
Well, yes. I can define a more precise LDAP filter in
`/etc/postfix/ldap-aliases.cf'. However: a way for disabling local
delivery and forcing remote one even if the address is present in
virtual_alias_maps would be a better (perfect) solution for me...
Best regards,
Marek
On 09/30/2014 11:04 AM, Marek Kozlowski wrote:
> :-)
>
> The scenario:
>
> For some reasons there are two mail servers: `myshost.mydomain' and
> `mydomain'. `myhost.mydomain' uses LDAP servers (pam_ldap, nss_ldap) as
> an authentication source. Users' email addresses are stored as an LDAP
> attributes which are accessed via:
>
> virtual_alias_maps = ldap:/etc/postfix/ldap-aliases.cf
>
> "For future development" ("migration in progress") some users have this
> attribute set to:
>
> [email protected]
>
> while others:
>
> name.surname@mydomain
>
> `mydestination' on `myhost.mydomain' is set to:
>
> mydestination = $myhostname, $myhostname.$mydomain,
> localhost, localhost.$mydomain,
>
> So it DOES NOT contain `$mydomain' itself.
>
> Expected results:
>
> 1. `[email protected]' sends an email to
> `[email protected]' - the mail is delivered locally to the
> mailbox of `jonesj' on the `myhost.mydomain' server. It works OK.
>
> 2. `[email protected]' sends an email to `john.doe@mydomain' -
> the mail is delivered to the other mail server. It doesn't work: the
> mail is delivered locally to the mailbox of `doej' on the
> `myhost.mydomain' server.
>
> I'm trying to guess what I'm doing wrong. How should I force remote
> delivery in such case?
>
> Best regards,
> Marek
>
