On 05-18-2021 3:10 pm, Noel Jones wrote:
Yes, postfix will attempt to lookup a hostname and use all the IPs
associated with it. This can cause a problem on startup if postfix
starts before the name resolution is available.
The solution i use to this problem on a RHEL systemd server is using the
On 05-18-2021 3:04 pm, Noel Jones wrote:
Yes, you can use macros in main.cf and reference them in the master.cf
# main.cf
submission_recipient_restrictions =
permit_sasl_authenticated
reject
# master.cf
127.0.0.1:submission inet n - n - - smtpd
-o smtpd_recipient_resrictions={ $submission_
On 5/17/2021 6:27 PM, Benny Pedersen wrote:
On 2021-05-18 00:29, Noel Jones wrote:
127.0.0.1:submission inet n - n - - smtpd
[::1]:submission inet n - n - - smtpd
localhost:submission inet n - n - - smtpd
imho postfix will accept this aswell, not tested
Yes, postfix will attempt to lookup
On 2021-05-18 00:29, Noel Jones wrote:
127.0.0.1:submission inet n - n - - smtpd
[::1]:submission inet n - n - - smtpd
localhost:submission inet n - n - - smtpd
imho postfix will accept this aswell, not tested
On 5/17/2021 5:20 PM, post...@ptld.com wrote:
New problem, i can not specify two IP's in the master.cf for
submission to bind to.
This works:
127.0.0.1:submission inet n - n - - smtpd
This works:
[::1]:submission inet n - n - - smtpd
This does not work:
127.0.0.1,[::1]:submission inet n - n
New problem, i can not specify two IP's in the master.cf for submission
to bind to.
This works:
127.0.0.1:submission inet n - n - - smtpd
This works:
[::1]:submission inet n - n - - smtpd
This does not work:
127.0.0.1,[::1]:submission inet n - n - - smtpd
127.0.0.1 [::1]:submission inet n - n
