+- PINE64 (https://forum.pine64.org)
+-- Forum: General (https://forum.pine64.org/forumdisplay.php?fid=1)
+--- Forum: General (https://forum.pine64.org/forumdisplay.php?fid=74)
+--- Thread: HELO files.pine64.org (email config problem) (/showthread.php?tid=7843)
HELO files.pine64.org (email config problem) - sdgathman - 08-14-2019
The forum emails provide only the classic HELO <fqdn> for authentication. This is fine, and RFC correct, although only a few knowledgeable email admins actually check it (or configure it correctly). Big Email providers like to insist on PTR (which is not RFC correct - that is what HELO is for). There is also a valid IP4 PTR record at 207.136.193.31.in-addr.arpa for files.pine64.org. But there is no IPv6 PTR record:
7.0.2.0.6.3.1.0.3.9.1.0.1.3.0.0.0.0.8.0.0.b.a.f.8.f.a.0.2.0.a.2.ip6.arpa not found: 3(NXDOMAIN)
Sending to Big Email providers that insist on PTR via IPv6 may fail.
The HELO for the forums emails is HELO files.pine64.org, and the DNS for files.pine64.org lists only an A record for 31.193.136.207. This is fine for sending emails to IP4 servers. files.pine64.org has entered the 21st century, and also sends emails via IPv6! Great job! Unfortunately, the IPv6 address is not listed in DNS, so the HELO authentication fails in that case. (The FQDN in HELO must resolve to the connect ip.) Since no other authentication is provided, my email server rejects the emails by default. (I, of course, have overridden this by adding a local SPF record for files.pine64.org.)
To simplest solution is to simply add the missing AAAA record to DNS:
files.pine64.org IN AAAA 2a02:af8:fab0:800:31:193:136:207
It would also be a good idea to add the PTR ("reverse DNS") for the IPv6 address to keep Big Email happy.
In addition, I could not find a button to resend the activation email. My account had to be manually activated by an admin on IRC.