On Wed, Aug 09, 2023 at 11:35:12AM -0500, shorton wrote: > >Do you have "reject_unauth_pipelining" in any of your smtpd > >restrictions, in either main.cf or master.cf? > > I do: > smtpd_data_restrictions = > reject_unauth_pipelining, > permit
That's the reason why the client is unable to submit its message. > >What is your Postfix version (it may have been patched by the vendor > >without changing the patch level number). > > 3.2.2 running on CENTOS 7. From http://ghettoforge.org/index.php/Postfix3 > postfix3.x86_64 2:3.2.2-4.gf.el7 > @gf-testing > postfix3-pcre.x86_64 2:3.2.2-4.gf.el7 > @gf-testing > > >What is the output of: > > > > $ postconf smtpd_forbid_unauth_pipelining > > postconf: warning: smtpd_forbid_unauth_pipelining: unknown parameter The default enforcement of correct pipelining is new in Postfix 3.9, at some point in the future, you may need to pay attention to this variable. For now your obstacle is the explicit restriction. > How hard is it to authorize pipelining for that host, if that's the issue? Instead of your current data restrictions, try: smtpd_data_restrictions = check_client_access inline:{152.86.61.4=permit}, reject_unauth_pipelining If you prefer a more flexible solution, main.cf: cidr = cidr:${config_directory}/ smtpd_data_restrictions = check_client_access ${cidr}clnt-data-access.cidr clnt-data-access.cidr: # IPv4 clients if 0.0.0.0/0 152.86.61.4 DUNNO # Any additional IPv4 special cases here # ... # Default action 0.0.0.0/0 reject_unauth_destination endif # IPv6 clients if ::/0 # Any special IPv6 cases here # ... # Default action ::/0 reject_unauth_destination endif -- Viktor. _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
