Is "virtual_alias_maps" somehow already supposed to be performing this functionality?Įdit zmmta.cf, and change POSTCONF smtpd_reject_unlisted_recipient no to 'yes'. Would this be sufficient or would I need a new ldap search in order to return the list of valid LDAP-stored recipients?
![zimbra desktop mail merge zimbra desktop mail merge](http://image2.win2pdf.com/win2pdf7.jpg)
Local_recipient_maps= ldap:/opt/zimbra/conf/ldap-vam.cf,$alias_maps
![zimbra desktop mail merge zimbra desktop mail merge](https://img.bhs4.com/E3/4/E34235F15A071548EE946990057A3921A36F29D1_large.jpg)
![zimbra desktop mail merge zimbra desktop mail merge](https://emailformatconverter.files.wordpress.com/2021/06/zimbra-to-office-365.png)
Will Zimbra get upset if I add the following to postfix/main.cf? Is there a proper Zimbra way to enable this functionality? This is also how the postfix default main.cf does things, but zimbra doesn't appear to use the local_recipient_maps variable at all. We do this by setting "local_recipient_maps" to our alias files and user lookup. In a similar vein, we currently only accept SMTP connections for valid recipients (this cuts down on a -lot- of spam processing). They should do what you're trying to accomplish without any postfix hacking. See the "Domain Forwarding" and "Domain Masquerading" sections of Managing Domains in the Wiki. Since zmmta.cf doesn't use "canonical_maps", would the correct answer be:Ī) Just add a canonical_maps entry and file to postfix/main.cf like we used to have (and let Zimbra remain unaware of what's going on.)ī) Add a new key to localconfig.xml "postfix_canonical_maps", a new entry to zmmta.cf and a new file such that zimbra creates a main.cf that looks like the one I would have created in step A.Ĭ) Use some internal zimbra method to achieve the same results that I've missed. POSTCONF sender_canonical_maps LOCAL postfix_sender_canonical_maps We currently use a canonical map to force the following has sender_canonical_maps set (to an LDAP query) which appears to be set by It looks like postscript is predominantly configured via zimbra internal variables through ZIMBRA_HOME/conf/zmmta.cf's mta section. Zimbra doesn't care about the contents of that file, so you should be able to modify it manually without any side effects. Specifically, I have a bug-tracking system with an email interface that needs to be hooked up with alias entries like: Can this file be directly edited or is Zimbra controlling it from somewhere else? Does zimbra even look at this file? It looks like Zimbra configures postfix with 'alias_maps = hash:/etc/aliases' by default, so it ends up pointing over to /etc/aliases rather than /opt/zimbra/postfix/conf/aliases, but then that file -could- be manually edited to contain whatever extra fixed aliases I need. ZIMBRA_HOME/postfix/conf/aliases appears to contain the 'main' aliases separate from any account or distribution list aliases I create. Most of these questions will, no doubt, turn out to be fairly simple and straightforward, but if they get answered here maybe they'll help other people in the future.
![zimbra desktop mail merge zimbra desktop mail merge](https://s3.amazonaws.com/fileswwwzimbracom/_res/images/resources/Universite-de-Lille-casestudy-thumbnail.png)
I understand postfix and am comfortable with it's configuration file, but want to make sure I don't break it's close ties to zimbra. I'm working on preparing a Zimbra deployment, and I want to make some modifications to the postfix configuration, but I'm a little confused by the Zimbra-introduced indirection.