How a sending domain works
Every email carries a From address, and the part after the @ is the sending domain. When a message arrives, the mailbox provider looks that domain up, reads the DNS records published on it, and decides whether whoever sent the message was authorised to use the name. It also keeps a running record of how recipients treat mail carrying that domain: opened, ignored, deleted unread, or reported as spam.
Two domains are involved rather than one. The visible From domain is what the reader sees. The return-path domain is what the sending system uses to collect bounces. Authentication is strongest when the two match, which is what people mean by alignment. Most email platforms arrange this for you once you add the DNS records they supply, but those records have to live on the domain you actually intend to send from, and only someone with access to your DNS can add them.
Why the sending domain matters
Reputation attaches to the domain, not to a campaign or a single message. Complaints, dead addresses and repeated bounces damage the domain itself, and that damage follows everything you send afterwards — quotes, invoices, password resets and booking confirmations included. A list that was bought rather than built can quietly take your ordinary business mail down with it, which is why it is worth understanding how sender reputation is built before you commit a domain to one.
It matters to the reader too. A From address on your own domain matches the website they visited and the person they spoke to, so the message reads as coming from a business rather than from a platform they have never heard of.
Common mistakes with sending domains
The frequent one is putting a free mailbox address in the From field — a Gmail or Yahoo address — while sending through a marketing platform. Those providers publish rules telling mailbox providers to reject mail that claims to come from them but was sent from somewhere else, so the campaign gets filtered or refused outright. Send from a domain you control instead.
The other is treating a brand-new domain as ready for volume. A domain with no history is unknown rather than trusted, and a large first send from it looks like exactly what a spammer would do. Buying a fresh look-alike domain for every campaign makes the problem permanent, because no domain ever accumulates a history worth having.
How to act on it
Pick one domain you own and can edit DNS on, publish SPF, DKIM and a DMARC policy on it, then check in your platform that the visible From address aligns with what is authenticated. After that, keep it stable. Changing the domain resets everything you have built and starts the judgement from scratch.
If you send genuinely different kinds of mail — receipts on one side, promotions on the other — separate them with subdomains rather than separate domains, so the parent keeps its standing while each stream is judged on its own behaviour. For a small business in Nepal writing mostly to Gmail addresses, this one decision does more for whether mail arrives than any rewrite of the copy.
