Jay, I’ve also tried that, perhaps my attempt to make an MX record is inaccurate … I get and OK config at Mxtoolboxdotcom: (no PTR record, no support for TLS, otherwise all green)
We have to have a DNS record that directs our TLD email to our outgoing mail server, that seems to override my attempt to send mail to the server / subdomain, viz: sending test email to nobody@discourse.TLD,domain shows up in the mail receiver logs as:
There’s not much chance on getting it figured out with it using placeholders since neither you nor whoever is helping you can check anything, but I guess here’s an attempt anyway.
The MX record should be
discourse.example.com pointing to discourse.example.com with any priority.
Don’t change anything about the TLD’s email. Just the MX record for the mail receiver, which is the same hostname as Discourse.
This worked fine, log says “delivered” so I’ll go back to the config and see if I can get reply-by-email working now
p.s.
I’m sure somewhere continuing to debug was DNS …
Because I kept sending test messages from my regular email address (a large Uni) and apparently changes to DNS haven’t managed to propagate in to said large email infrastructre.
So I sent a test message from that openinbox account I was going to use for POP3, bingo, delivered fine
god I used to run dns servers, but it was a couple decades ago, and times were simpler.
Anyway, my MX (namecheap) looks exactly as you said, … I’ll stop obfuscating