Summary: | mail/postfix: running post-install script modifies custom configuration settings | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Sascha Biberhofer <ports> |
Component: | Individual Port(s) | Assignee: | Juraj Lutter <otis> |
Status: | In Progress --- | ||
Severity: | Affects Only Me | CC: | trashcan |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(otis) |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Sascha Biberhofer
2022-05-06 11:55:45 UTC
I thought it over many times and came to the conclusion that postfix's post-install script does a good job when updating the .cf files. Do you have any particular scenario (not mentioning inet_protocols) in mind? Because, in particular, for inet_protocols, specifying "inet_protocols=any" in main.cf is always a good idea. (In reply to Juraj Lutter from comment #1) I ran into this issue setting inet_protocols=ipv4 after removing inet_protocols=all from my main.cf, *because* it became the default setting: mail> postconf -d inet_protocols inet_protocols = all Resetting this to inet_protocols=ipv4 *without* restarting postfix left my mailserver complaining and even throtteling [1] due to: http://www.postfix.org/postconf.5.html#inet_protocols "Note: you MUST stop and start Postfix after changing this parameter." I do sometimes recompile and reinstall all ports of mine, that is how I found out. I do consider this a serious bug, and I was about to open a new bug report but found this. Regards, Michael [1] Jan 17 20:06:31 mail postfix/master[54448]: warning: /usr/local/libexec/postfix/smtpd: bad command startup -- throttling (In reply to Michael Grimm from comment #2) Forget the throtteling part. If one recompiles and reinstalls a port, one should restart postfix. I forgot, my bad. |