[pfx] Re: Odd error
Hi Thanks for the insight will find something no doubt. Just spotted that Postfix sent me this at the time. I cannot see anything remiss in it with my eyes Transcript of session follows. Out: 220 mx3.uactech.co.uk ESMTP In: EHLO host.verypinktiger.com Out: 250-mx3.uactech.co.uk Out: 250-PIPELINING Out: 250-SIZE 22971520 Out: 250-ETRN Out: 250-STARTTLS Out: 250-ENHANCEDSTATUSCODES Out: 250-8BITMIME Out: 250 CHUNKING In: STARTTLS Out: 220 2.0.0 Ready to start TLS In: EHLO host.verypinktiger.com Out: 250-mx3.uactech.co.uk Out: 250-PIPELINING Out: 250-SIZE 22971520 Out: 250-ETRN Out: 250-ENHANCEDSTATUSCODES Out: 250-8BITMIME Out: 250 CHUNKING In: MAIL FROM: SIZE=14157 Out: 250 2.1.0 Ok In: RCPT TO: Out: 451 4.3.5 Server configuration error In: DATA Out: 554 5.5.1 Error: no valid recipients In: QUIT Out: 221 2.0.0 Bye On 21/11/2023 17:18, Wietse Venema via Postfix-users wrote: Paul Enlund via Postfix-users: Nov 20 15:48:03 kanuka postfix/smtpd[3566272]: warning: unknown smtpd restriction: "OK" On 21/11/2023 15:25, Wietse Venema via Postfix-users wrote: "OK" is valid only as the first word in a table lookup result. Response updated for for completeness: OK is also valid as the first word in a check_policy_service result. OK is not valid when it appears after other text (in a lookup table or check_policy_service result). Paul Enlund via Postfix-users: Well on first scan no lookup tables look out of order aside to 1 which had a little white space after the OK's In a lookup table input file, whitespace *before* OK can produce the above error, because Postfix will append that text to the previous line: the result will that "OK" appears after other text. Now, we could make "OK" more tolerant in newer Postfix releases, but that will not have an effect on stable releases. Wietse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Odd error
Paul Enlund via Postfix-users: > Nov 20 15:48:03 kanuka postfix/smtpd[3566272]: warning: unknown > smtpd restriction: "OK" On 21/11/2023 15:25, Wietse Venema via Postfix-users wrote: > "OK" is valid only as the first word in a table lookup result. Response updated for for completeness: OK is also valid as the first word in a check_policy_service result. OK is not valid when it appears after other text (in a lookup table or check_policy_service result). Paul Enlund via Postfix-users: > Well on first scan no lookup tables look out of order aside to 1 which > had a little white space after the OK's In a lookup table input file, whitespace *before* OK can produce the above error, because Postfix will append that text to the previous line: the result will that "OK" appears after other text. Now, we could make "OK" more tolerant in newer Postfix releases, but that will not have an effect on stable releases. Wietse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Odd error
Paul Enlund via Postfix-users: > Nov 20 15:48:03 kanuka postfix/smtpd[3566272]: warning: unknown > smtpd restriction: "OK" On 21/11/2023 15:25, Wietse Venema via Postfix-users wrote: > "OK" is valid only as the first word in a table lookup result. Paul Enlund via Postfix-users: > Well on first scan no lookup tables look out of order aside to 1 which > had a little white space after the OK's In a lookup table, whitespace *before* OK can produce the above error, because Postfix will append that text to the previous line, and the result will thaht "OK" appears after other text. Wietse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Odd error
Hi Well on first scan no lookup tables look out of order aside to 1 which had a little white space after the OK's Will come back to it for a 2nd scan with a fresh head presently I am wondering if the following is allowed/recommended practice ? my last 2 lines of smtpd_recipient_restrictions are: check_sender_access proxy:mysql:/etc/postfix/mysql/postgrey_sender.cf check_policy_service inet:localhost:6 The check_sender_access allows me to skip the postgrey check for listed sender addresses. This would have been triggered on the configuration error transaction yesterday On 21/11/2023 15:25, Wietse Venema via Postfix-users wrote: Paul Enlund via Postfix-users: Nov 20 15:48:03 kanuka postfix/smtpd[3566272]: warning: unknown smtpd restriction: "OK" Nov 20 15:48:03 kanuka postfix/smtpd[3566272]: NOQUEUE: reject: RCPT from host.verypinktiger.com[89.34.18.125]: 451 4.3.5 Server configuration error; ... I suggest that you start with the output from these commands: postconf -n | grep OK postconf -P | grep OK If that produces no match, examine the lookup tables in this command output: postconf -n | grep 'smtpd.*restrictions =' postconf -P | grep 'smtpd.*restrictions =' "OK" is valid only as the first word in a table lookup result. Wietse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Odd error
Paul Enlund via Postfix-users: > Nov 20 15:48:03 kanuka postfix/smtpd[3566272]: warning: unknown > smtpd restriction: "OK" > Nov 20 15:48:03 kanuka postfix/smtpd[3566272]: NOQUEUE: reject: > RCPT from host.verypinktiger.com[89.34.18.125]: 451 4.3.5 Server > configuration error; ... I suggest that you start with the output from these commands: postconf -n | grep OK postconf -P | grep OK If that produces no match, examine the lookup tables in this command output: postconf -n | grep 'smtpd.*restrictions =' postconf -P | grep 'smtpd.*restrictions =' "OK" is valid only as the first word in a table lookup result. Wietse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: Odd error
On 2023-11-21 at 09:38:35 UTC-0500 (Tue, 21 Nov 2023 14:38:35 +) Paul Enlund via Postfix-users is rumored to have said: Hi I have an odd error in yesterdays mail.log. This is a one off and cannot be replicated Nov 20 15:48:03 kanuka postfix/smtpd[3566272]: connect from host.verypinktiger.c om[89.34.18.125] Nov 20 15:48:03 kanuka postfix/smtpd[3566272]: Anonymous TLS connection establis hed from host.verypinktiger.com[89.34.18.125]: TLSv1.2 with cipher ECDHE-RSA-AES 256-GCM-SHA384 (256/256 bits) Nov 20 15:48:03 kanuka postfix/smtpd[3566272]: warning: unknown smtpd restrictio n: "OK" Nov 20 15:48:03 kanuka postfix/smtpd[3566272]: NOQUEUE: reject: RCPT from host.v erypinktiger.com[89.34.18.125]: 451 4.3.5 Server configuration error; from=ir...@tigerspecs.co.uk> to= proto=ESMTP helo= ger.com> Nov 20 15:48:03 kanuka postfix/smtpd[3566272]: disconnect from host.verypinktige r.com[89.34.18.125] ehlo=2 starttls=1 mail=1 rcpt=0/1 data=0/1 quit=1 commands=5/7 Where/what to start looking for something that caused this. 'OK' Somewhere in your smtpd_*_restrictions lists there's an error. Most likely a typo in an access map of some sort. Impossible for anyone here to even guess which one without the debugging info suggested here: http://www.postfix.org/DEBUG_README.html#mail -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
