How to configure PMG to verify recipient existence using ldap with domain alias?

[Wodel]

Hi,

We recently added a PMG VM to our Zimbra platform.
We want to verify recipient existence using Zimbra LDAP, which we already did, but we have a little problem
Our main domain "newdomain.tld" has an alias "olddomain.tld", if we activate recipient verification on PMG, all emails sent to olddomain.tld are rejected since the verification will fail.

We tried to use this on PMG :

virtual_alias_domains = olddomain.tld
virtual_alias_maps = hash:/etc/postfix/virtualdomains

cat /etc/postfix/virtualdomains
@olddomain.tld @newdomain.tld

But :
1 - It didn't work, PMG still searches for user@olddmain.tld not for user@newdomain.tld, I don't know if changing the rule priority will change this behavior since it has priority of 99 on Mail Filter -> Rules

2 - Adding configuration to /etc/postfix/main.cf does not hold any changes made on the webui of PMG.

Is there a possibility to verify recipient existence on PMG while using an alised domain?

Regards.

 

[Senin]

Hi!

Can you see your alias emails in Configuration/User management/LDAP/Users of ldap if you double-click on primary email?

 

[Wodel]

Hi,

That's the problem, when you create a domain alias on Zimbra, it does not add an alias attribute to all accounts, it just add an entry on LDAP saying that olddomain is an alias of newdomain.

Like this :

# olddomain.tld
dn: dc=olddomain,dc=tld
zimbraDomainAliasTargetId: 2e7a5e95-f4be-428f-bf93-360601a7dd99
zimbraMailCatchAllForwardingAddress: @newdomain.tld     <----------------------
description: domain alias of newdomain.tld
zimbraDomainStatus: active
zimbraDomainType: alias
objectClass: dcObject
objectClass: organization
objectClass: zimbraDomain
objectClass: amavisAccount
zimbraId: 32c8dbc9-34e1-4547-be51-ae3f65602d64
zimbraCreateTimestamp: 20230220133903.051Z
zimbraDomainName: olddomain.tld
zimbraMailStatus: enabled
zimbraMailCatchAllAddress: @olddomain.tld
o: olddomain.tld domain
dc: olddomain

if it was an attribute I would have added it to the search query or create another rule to that attribute.

Regards