3 ms·
They (and a few here) are missing the key point. I'll refer everyone to the passage "One Good Thing" in Helme's article, just above the disclosure timeline. The
by CodeWriter23 9y ago
They (and a few here) are missing the key point. I'll refer everyone to the passage "One Good Thing" in Helme's article, just above the disclosure timeline. The product does not create an MX record for the email server, hence it is a write-only system. You can't receive email without an MX record because no sender can locate your MTA. I don't care how secure it may or may not be, it's still useless to me.
- zaroth 9y agoTechnically, MX are not mandatory. As per RFC2821, if no MX is found the A record will be used. In the past I used this fact regularly when obtaining SSL certificates for subdomains that were pointed at my server. Customer "foo.com" would point app.foo.com at my server for me to host my service for them on their subdomain. To obtain an SSL certificate, I would select email validation to admin@app.foo.com and not need an MX record in the customer's DNS system in order to receive the email, it would be delivered purely based on the A record pointing to my server.