I've somehow got myself into a situation where the mta trusted relay network setting is 'stuck'. Changes I make in the admin interface seemed to be saved OK, and can be viewed using zmprov gacf, but never take effect in the postfix configuration. I can even manually change main.cf to reflect what the setting should be, but it is still overwritten when zimbra restarts with the 'old' setting.
I ran zmslapcat and found the config entry in the LDAP database seems to also contain the 'old' value even though zmprov gacf returns the correct 'new' entry.
Any pointers would be appreciated.
MTA config is 'stuck'
MTA config is 'stuck'
Do a
zmlocalconfig | grep relay
What ever value comes back, you can change it with
zmlocalconfig -e (relay command)=(Relay value)
zmlocalconfig | grep relay
What ever value comes back, you can change it with
zmlocalconfig -e (relay command)=(Relay value)
MTA config is 'stuck'
If you do a execute "postfix reload" is should pull all the new parameters, and it's non-intrusive.
MTA config is 'stuck'
Thanks for the advice, but neither of those things has helped.
zmlocalconfig | grep relay returns no lines and postfix reload ran without error but left the main.cf unchanged.
Should I try changing the entry in LDAP using an LDAP editor?
zmlocalconfig | grep relay returns no lines and postfix reload ran without error but left the main.cf unchanged.
Should I try changing the entry in LDAP using an LDAP editor?
MTA config is 'stuck'
Sorry-
Try to grep the main.cf file.
What returns?
Try to grep the main.cf file.
What returns?
MTA config is 'stuck'
[quote user="jholder"]Sorry-
Try to grep the main.cf file.
What returns?[/QUOTE]
looking for the value in main.cf shows the old value that doesn't agree with what is listed in zmprov gacf
Try to grep the main.cf file.
What returns?[/QUOTE]
looking for the value in main.cf shows the old value that doesn't agree with what is listed in zmprov gacf