An address is the beginning of a mail system.
In [email protected], the part before @ identifies a mailbox or another recipient arrangement, and example.com supplies the domain identity. A domain registration alone does not create a mail service. You also need a system that can receive, store and send messages for that domain.
For a small studio, [email protected] can identify a person and [email protected] can identify a team responsibility. Decide who should read each address, who can send from it, and what should happen when someone leaves. A clear address is useful because it connects to a clear operating decision.
Follow a message from sender to inbox.
Mail software submits a message to a sending server. To deliver it to another domain, the sending system looks up that domain’s MX records and contacts a receiving mail server. The receiver applies its checks and may accept the message for the intended mailbox.
Reading the message is another part of the journey. A mail app commonly accesses stored messages using IMAP, or the user reads them in webmail. SMTP moves mail between sending and receiving systems. DNS helps find the destination; it does not store the mailbox.
Reference: Cloudflare: mail serversReceiving mail and proving identity are different jobs.
An MX record names a receiving mail server and includes a preference value. Lower values are preferred when choosing between destinations. The target is a hostname for the mail system; it is not the email address of the person receiving the message.
SPF describes authorized sending sources for a domain used in the mail envelope. DKIM adds a cryptographic signature that receivers can verify using a published key. DMARC checks alignment with the visible From domain and publishes policy and reporting instructions. A passing aligned SPF or DKIM result can satisfy DMARC.
Reference: Cloudflare: MX recordsReference: Cloudflare: SPF, DKIM and DMARC| Record / mechanism | Question it helps answer | Does not do |
|---|---|---|
| MX | Where should incoming mail go? | Create a mailbox |
| SPF | Is this sending source authorized? | Encrypt the message |
| DKIM | Can this domain’s signature be verified? | Guarantee the sender is trustworthy |
| DMARC | Does authentication align with From? | Guarantee placement in the inbox |
A mailbox, an alias and a group are not interchangeable.
A mailbox stores messages for an account. An alias generally delivers mail to an existing destination rather than creating its own independent store. A group can distribute mail to several members. Sending behavior and access options depend on the mail system’s configuration.
For the studio, a personal mailbox might belong to the founder, while contact@ routes to a shared team destination. Avoid sharing a personal password simply to let several people answer customers. Choose a shared-access arrangement with individual accountability where the mail service supports it.
Email needs ongoing care.
Publish the records that match every legitimate sender, including business applications that send mail on your behalf. Review authentication results and DMARC reports, then adjust policy carefully. Incorrect settings can interfere with legitimate messages as well as unwanted ones.
Good authentication is one part of delivery. Receiver policy, reputation, message content and recipient behavior also influence handling. A private mail server additionally needs maintenance, storage management, backups and monitoring. Treat “message accepted by the server” and “message visible in the recipient’s inbox” as different observations.
Reference: Cloudflare: SPF, DKIM and DMARCCommon questions.
Can email work without a website?
Yes. A domain can have working email even if it does not serve a public website. The mail service and DNS records still need to be configured.
Does SPF, DKIM and DMARC guarantee inbox delivery?
No. Authentication supports identity checks. Receiving systems make their own acceptance and spam-filtering decisions.
Is contact@ automatically a separate mailbox?
No. It can be a mailbox, alias or group depending on the configuration you choose.
Connect the concept to your work.
DOCKOCK brings your domain, mailbox configuration and mail infrastructure into one workspace, alongside the applications that share your business identity.
Explore business email in DOCKOCKKeep learning from the source.
Further reading from the teams and documentation behind these technologies.
Cloudflare: mail serversCloudflare: MX recordsCloudflare: SPF, DKIM and DMARC