On 14/2/2025 11:41 π.μ., Florian Piekert wrote:
... couldreject_unknown_reverse_client_hostnamein the smtpd_recipient_restrictions be responsible, since there are dns resolution issues for the hostname....
Thanks Florian for the reply. Interestingly, dns reverse record query does work on the server: [root@mailgw1 postfix]# dig -x 154.52.2.232 ; <<>> DiG 9.11.36-RedHat-9.11.36-16.el8_10.2 <<>> -x 154.52.2.232 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59302 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;232.2.52.154.in-addr.arpa. IN PTR ;; ANSWER SECTION: 232.2.52.154.in-addr.arpa. 3600 IN PTR smtpfra7.fortimailcloud.com. ;; Query time: 391 msec ;; SERVER: 62.217.126.164#53(62.217.126.164) ;; WHEN: Fri Feb 14 12:16:49 EET 2025 ;; MSG SIZE rcvd: 95 Nevertheless, the warning does gets logged by postfix.Yet I think this is not critical, since it's just a warning. If the session was terminated due to reverse record check, it would be logged like in this case :
Feb 14 04:02:59 mailgw1 postfix/smtpd[3627408]: NOQUEUE: reject: RCPT from unknown[103.35.70.77]: 450 4.7.1 Client host rejected: cannot find your reverse hostname, [103.35.70.77]; from=<xxxx...@client.scholargatherings.com> to=<xxxx...@noa.gr> proto=ESMTP helo=<server77.rdnsdomain1.co.in>
Any other hints are welcome! Thanks, Nick
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
