I can provide these at the moment…logs from my server. The domain in the message must be .org as it’s getting flagged.
I do recall last week that either domain (.org or .cloud) seemed to be resolving to the address when I checked manually from ultratools online. However, my server (which uses cloudflare) was not able to resolve the .org version. I ultimately concluded that the handshake was not include the hostname, as discourse was sending both version on and off over a day’s period. I considered whitelisting the ip address but decided against it.
Based on this, as I don’t know who the heck this is. The address is a residence:
Jun 10 10:22:49 mx postfix/postscreen: PASS OLD [188.8.131.52]:40265
Jun 10 10:22:57 mx postfix/smtpd: warning: hostname mx-out-01a.sjc3.discourse.org does not resolve to address 184.108.40.206: Temporary failure in name resolution
Jun 10 10:22:57 mx postfix/smtpd: connect from unknown[220.127.116.11]
Jun 10 10:22:58 mx postfix/smtpd: Anonymous TLS connection established from unknown[18.104.22.168]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
Jun 10 10:22:58 mx postfix/smtpd: NOQUEUE: reject: RCPT from unknown[22.214.171.124]: 450 4.7.25 Client host rejected: cannot find your hostname, [126.96.36.199]; firstname.lastname@example.org to= proto=ESMTP helo=<mx-out-01a.sjc3.discourse.cloud>
Jun 10 10:22:58 mx postfix/smtpd: disconnect from unknown[188.8.131.52] ehlo=2 starttls=1 mail=1 rcpt=0/1 data=0/1 rset=1 quit=1 commands=6/8
These error logs began when I stopped receiving digests.
If I can assist further, please let me know. I am hesitant to let the message through.