Basic terms

Can anyone explain what these services actually do? I tried to make a list, correct me if I’m wrong?

MX = MR …eceive (who receives email for the domain)
SPF = MS …end (who sends email for the domain)
DKIM = MK …ey (email public key for the domain)
DMARC = MFA (fail action)

Also, how do these entities relate with each other in case you want to use more email services on your domain (or even subdomains - example.com, blog.example.com )? For example Office, Sendpulse and your own mail server. How will the entries look like?

I wouldn’t call any of those a “service”, exactly. Email is a service. Maybe that’s just me, though.

MX is a type of record in the DNS database. It points to an organization’s “mail exchanger”, which is the server that receives email.

The other three are protocols that help your mail server decide what to do with incoming mail, mostly to deal with spam.

You might want to read the relevant RFCs or the Wikipedia pages for SPF, DKIM, and DMARC.

I’ve read everything about it there is on the internet. Nothing says about how to set it up for more than one mail server for one domain, or one mail server for more domains, or a combo of those two.

I agree on the ‘service’, just couldn’t think of a better term at the moment.

I also see no difference between MX and SPF records. One is a list of servers that receive mail, and other is a list of servers that send mail. Why the syntax is different one can only guess…

One doesn’t need to guess, one can read the relevant documentation. In the case of Internet standards, those are the Request For Comments (RFC) documents. Internet email is defined by the Simple Mail Transfer Protocol documentation, the most recent of which is RFC 5321:

https://tools.ietf.org/html/rfc5321

SPF is this one:

https://tools.ietf.org/html/rfc7208

If they are too technical for you (they are usually way too technical for me) then there’s always Wikipedia.

Setting up multiple mail servers for one domain is a matter of having multiple MX records for your domain, and giving each MX record a priority. If the highest priority server is down, senders will try to use the next highest priority MX record, and so on.

Setting up one server for multiple domains is again a matter of having multiple MX records, one per domain, and each pointing to the same server. That server will need to be configured to handle the incoming mail appropriately, of course, which has nothing to do with DNS records.

One difference between MX and SPF records is that MX records are required for internet email, and SPF records are optional. They serve two very different purposes: one is to discover where to SEND outgoing mail, and the other is to discover if it’s safe to RECEIVE incoming mail from a server that’s trying to send it to you. They are different mainly because MX is much older than SPF, and spam had not yet been invented when the MX protocol was designed, so they didn’t think there was a reason to add any kind of authentication to MX. They were having enough trouble just getting it to work at all!

Hope this helps,

Doug W.

Sorry, but it doesn’t. This is pretty much crap paper. Like something schoolchildren wrote.

Thanks for trying to help, though. It’s not your fault these people are so unorganized.