I have noticed that incoming Passbolt forum digests are getting hung up on my server. I can’t quite nail it down, but this morning it’s a case of the hostname having no A records.
Last week it was coming through as .cloud and .org. Most of the time I was able to resolve the hostname manually and the issue was the message didn’t include the hostname. I am pretty sure this is coming from Passbolt.
I figured I would pass it on in case no one else had.
@olAaeE6Eu35jfogv9umc can you forward us a digest email you received so that the discourse team can investigate? Thanks,
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 [220.127.116.11]:40265
Jun 10 10:22:57 mx postfix/smtpd: warning: hostname mx-out-01a.sjc3.discourse.org does not resolve to address 18.104.22.168: Temporary failure in name resolution
Jun 10 10:22:57 mx postfix/smtpd: connect from unknown[22.214.171.124]
Jun 10 10:22:58 mx postfix/smtpd: Anonymous TLS connection established from unknown[126.96.36.199]: 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[188.8.131.52]: 450 4.7.25 Client host rejected: cannot find your hostname, [184.108.40.206]; 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[220.127.116.11] 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.
I just received a digest dated June 8 10:44pm. I made no changes on my server.
Coincidence? Or maybe we got something fixed, yeah?
Jun 10 11:02:50 mx postfix/postscreen: CONNECT from [18.104.22.168]:35253 to [10.0.40.3]:25
Jun 10 11:02:50 mx postfix/postscreen: PASS OLD [22.214.171.124]:35253
Jun 10 11:02:50 mx postfix/smtpd: connect from mx-out-01a.sjc3.discourse.cloud[126.96.36.199]
Jun 10 11:02:50 mx postfix/smtpd: Anonymous TLS connection established from mx-out-01a.sjc3.discourse.cloud[188.8.131.52]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
Jun 10 11:02:51 mx postfix/smtpd: 12A1A7E88A: client=mx-out-01a.sjc3.discourse.cloud[184.108.40.206]
Jun 10 11:02:51 mx postfix/smtpd: disconnect from mx-out-01a.sjc3.discourse.cloud[220.127.116.11] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7
Jun 10 11:02:51 mx amavis: (26897-15) Checking: joAqq8EJnyNJ [18.104.22.168] email@example.com -> MYHIDDENEMAILADDRESS
Jun 10 11:02:55 mx amavis: (26897-15) Passed CLEAN
@olAaeE6Eu35jfogv9umc discourse team is looking into the issue, maybe they fixed it.
Yes - we recently changed our naming convention and the RDNS for this entry needed to be fixed, thanks for bringing it to our attention!
Fantastic! I actually posted last week but then deleted, and second guessed it. Thank you for fixing it.
Unknown host error is occurring on incoming mail (the digest, I’m assuming). Here is from the logwatch report from yesterday:
Maybe someone can give a shout to the Discourse folks again.
@garrett I will send them a heads up
@garrett the fine people at discourse say it’s fixed. Can you confirm?
@remy unknown host is occurring now on different subdomain:
@schleifer is asking: Do you have any more information for that? Maybe a timestamp? The published record has
ip4:22.214.171.124/27 which includes that address, so the most likely reason is that they still had the old record cached.
@remy @schleifer That last one was from Dec 5 09:35:04 UTC
MxToolbox is still reporting no DNS for that domain. Currently, both domains have no DNS.
I think possibly it is that the server is not sending the hostname in the message.
reject: RCPT from unknown[126.96.36.199]: 450 4.7.25 Client host rejected: cannot find your hostname, [188.8.131.52];
I got the recent digest so it appears functional without issues. Thanks to those who helped!