- Zimbra Collaboration 8.6 Patch 9 now available (includes fix for CVE-2017-8802). Read the announcement.
- Zimbra Collaboration 8.8.7 + Zimbra Connector for Outlook 8.8.7 are available.. Read the announcement.
- Are you a Zimbra Developer? You can find some interesting stuff in our Official GitHub: https://github.com/Zimbra and check the Community Projects too: https://github.com/Zimbra-Community/
Discuss your pilot or production implementation with other Zimbra admins or our engineers.
- Outstanding Member
- Posts: 909
- Joined: Mon Apr 18, 2016 8:18 pm
- Location: Earth
- ZCS/ZD Version: ZCS FLOSS - 8.7.11 Mutli servers
I was talking about SIEVE Filter.
- Outstanding Member
- Posts: 336
- Joined: Fri Sep 12, 2014 11:18 pm
- Location: Victoria, BC
- ZCS/ZD Version: Release 8.7.11_GA_1854.RHEL6_64.P7
shanmarsh28 wrote:The link you provide is a very exact description - looks like a general postfix issue rather than something specific to Zimbra but I don't know how you could integrate that solution. I know main.cf exits as I came across it but I'm a bit nervous about editing in case I break something that I am unable to fix.
Excellent... Couldn't this be handled by postfix_sender_canonical_maps? You can check https://wiki.zimbra.com/wiki/Postconf_keys to see the "zimbra way". If that is the case, perhaps this https://forums.zimbra.org/viewtopic.php?t=63234 has the information you need.
Ref: from postfix manual: http://www.postfix.org/postconf.5.html#sender_canonical_maps
Code: Select all
Optional address mapping lookup tables for envelope and header sender addresses. The table format and lookups are documented in canonical(5).
Example: you want to rewrite the SENDER address "firstname.lastname@example.org" to "email@example.com", while still being able to send mail to the RECIPIENT address "firstname.lastname@example.org".
Note: $sender_canonical_maps is processed before $canonical_maps.
PS... Answering your other question about updating main.cf when there is no zimbra way. The issue is upgrades... you would need to put back your changes if there isn't support via the "zimbra way". They have some ldap variables that are retained between releases that the zmconfigd program uses to write its postfix output but you don't always have everything you need so sometimes one has to move in that direction for advanced solutions. As far as break something, you just put back the file or comment out your changes and restart the mta.
Who is online
Users browsing this forum: Google [Bot] and 18 guests