As zimbra user:
Get maximal_queue_lifetime:
[zimbra@zimbra ~]$ postconf | grep maximal_queue_lifetime
maximal_queue_lifetime = 5d
Change the configs and get new config:
[zimbra@zimbra ~]$ postconf -e maximal_queue_lifetime=1d
[zimbra@zimbra ~]$ zmlocalconfig -e postfix_maximal_queue_lifetime=1d
[zimbra@zimbra ~]$ postconf | grep maximal_queue_lifetime
maximal_queue_lifetime = 1d
[zimbra@zimbra ~]$ zmlocalconfig | grep postfix_maximal_queue_lifetime
postfix_maximal_queue_lifetime = 1d
Reload postifx:
[zimbra@zimbra ~]$ postfix reload
/postfix-script: refreshing the Postfix mail system
Get maximal_queue_lifetime parameter again (reseted to default 5d after postifx reload):
[zimbra@zimbra ~]$ postconf | grep maximal_queue_lifetime
maximal_queue_lifetime = 5d
In zmlocalconfig parameter is OK:
[zimbra@zimbra ~]$ zmlocalconfig | grep postfix_maximal_queue_lifetime
postfix_maximal_queue_lifetime = 1d
Cannot change postfix maximal_queue_lifetime in 8.7.5
-
- Posts: 3
- Joined: Sat Mar 25, 2017 7:45 pm
- DualBoot
- Elite member
- Posts: 1326
- Joined: Mon Apr 18, 2016 8:18 pm
- Location: France - Earth
- ZCS/ZD Version: ZCS FLOSS - 8.8.15 Mutli servers
- Contact:
Re: Cannot change postfix maximal_queue_lifetime in 8.7.5
Hi,
maybe you do not look at the right place ?
Did you try this
And restart Zimbra MTA.
Regards,
maybe you do not look at the right place ?
Did you try this
Code: Select all
zmprov ms $(zmhostname) zimbraMtaMaximalQueueLifetime 1d
Regards,
Re: Cannot change postfix maximal_queue_lifetime in 8.7.5
Hi DualBoot,
I'm on 8.6 and get this error:
In fact, I cannot find the zimbraMtaMaximalQueueLifetime parameter in zmprov gs or zmprov GetAllConfig results...
Any suggestions?
Thanks!
I'm on 8.6 and get this error:
Code: Select all
zmprov ms [my server] zimbraMtaMaximalQueueLifetime 1d
ERROR: account.INVALID_ATTR_NAME (invalid attr name: invalid attr name - unable to modify attributes: zimbraMtaMaximalQueueLifetime: attribute type undefined)
Any suggestions?
Thanks!
- DualBoot
- Elite member
- Posts: 1326
- Joined: Mon Apr 18, 2016 8:18 pm
- Location: France - Earth
- ZCS/ZD Version: ZCS FLOSS - 8.8.15 Mutli servers
- Contact:
Re: Cannot change postfix maximal_queue_lifetime in 8.7.5
Hello,
if you are on Ubuntu search for the Zimbra main.cf file.
If you get 2 files quiet identical at one point : the end with a second extension .in , open it and search for the Zimbra variable which replace the value
into the main.cf file.
Regards,
if you are on Ubuntu search for the Zimbra main.cf file.
If you get 2 files quiet identical at one point : the end with a second extension .in , open it and search for the Zimbra variable which replace the value
into the main.cf file.
Regards,
Re: Cannot change postfix maximal_queue_lifetime in 8.7.5
Thanks DualBoot, I’ve done some further research and I think I may solved the problem:
It appears that the postfix value maximal_queue_lifetime was not mapped to LDAP nor zmlocalconfig values in previous Zimbra versions. So if the server was upgraded to 8.5+ version from a previous release there will be no mapping too, even on 8.6 or 8.7 the command zmlocalconfig -e postfix_maximal_queue_lifetime=... will be saved but will have no effects on postfix.
To make it work you have to manually add the mapping value from zmconfigd.cf file has described here.
After saving, let’s restart MTA (zmmtactl restart) and now postfix conf file should have the maximal_queue_lifetime set in it. No zmprov commands are used, since LDAP is not involved.
I still cannot understand why these two strictly-related parameters (maximal_queue_lifetime and bounce_queue_lifetime) hava been managed in such different ways!
Thanks again for pointing me in the right direction (or correct me if I made some mistakes)
It appears that the postfix value maximal_queue_lifetime was not mapped to LDAP nor zmlocalconfig values in previous Zimbra versions. So if the server was upgraded to 8.5+ version from a previous release there will be no mapping too, even on 8.6 or 8.7 the command zmlocalconfig -e postfix_maximal_queue_lifetime=... will be saved but will have no effects on postfix.
To make it work you have to manually add the mapping value from zmconfigd.cf file has described here.
After saving, let’s restart MTA (zmmtactl restart) and now postfix conf file should have the maximal_queue_lifetime set in it. No zmprov commands are used, since LDAP is not involved.
I still cannot understand why these two strictly-related parameters (maximal_queue_lifetime and bounce_queue_lifetime) hava been managed in such different ways!
Thanks again for pointing me in the right direction (or correct me if I made some mistakes)