How websites, hosting, domains and AI discoverability actually work - in plain language, with primary sources cited. Written to answer the question, not to bury it.
IMAP keeps every device in sync with the server; POP3 downloads and detaches. Here is how to set up a phone and a laptop on the same business mailbox, which ports to use, and how to fix the classic 'it works on my laptop but not my phone' failure.
A personal note to a customer and a marketing campaign are different things in Canadian law, and the line is drawn by the content of the message rather than the size of the send. Here is where CASL section 6 bites, when implied consent covers you, and the point at which a mailing list tool stops being optional.
Web hosting and email hosting are different services resolved by different DNS records on the same domain. Here is why a hosting plan that says it includes email often does not, what to check, and why keeping the two separable is the safer arrangement.
The order matters more than the products. Domain in the business's name, MX record, one mailbox per sender, role addresses as aliases, then authentication. Here is the sequence, what each step actually does, and the Canadian obligations that attach the moment you send your first message.
Spam control is layered, and the cheapest layers come first: refuse mail to addresses that do not exist, publish the three authentication records so your own domain cannot be forged, filter on the server rather than in one app, and stop answering machines. Here is the order that works.
Most small businesses need one paid mailbox per person who sends email, and nothing else. Here is how to count properly, when a role address genuinely needs its own mailbox, and what over-buying really costs.
Text is negligible; attachments are everything, and encoding adds roughly 33 per cent on top. Here is how to estimate what your business needs from your own habits, and why the Income Tax Act sets a six-year floor you cannot delete your way out of.
Two businesses can absolutely live in one mail account, and most owner-operators should run them that way. What cannot be merged is the identity: separate domains, separate authentication, separate books, and a clear answer to which business a given message belongs to.
Forwarding works for one person who never replies as the address. A shared mailbox is what you need the moment a second person joins the queue, or the reply has to come from info@. Here is the test, and the authentication cost of getting it wrong.
A catch-all accepts mail addressed to anything@yourdomain, including the millions of addresses a spammer invents. Here is what that does to your spam load, why the rejection you gave up was doing real work, and the narrow cases where a catch-all is still the right call.
An expired domain stops your email before it stops your website, and the messages sent during the gap are usually lost for good. Here is the actual timeline under ICANN policy, what senders see, and how to recover.
Canadian law prescribes exactly what a commercial electronic message must carry, and it is shorter than most signatures already are. Here is the required list, what may be moved behind a link, the sixty-day validity rule, and the claims you should keep out of the block entirely.
Most people stay with an email host they dislike because they are afraid of losing mail in the move. The fear is reasonable and the fix is boring: lower your TTL first, copy over IMAP while both sides are live, switch MX, and keep the old mailbox running for a couple of weeks.
Nobody thinks of their inbox as a database. PIPEDA does not care what you call it - if customer personal information is in there, the safeguards, breach-record and access-request rules apply to it.
Owners either keep every email forever or delete casually, and both are wrong. Email is not a category in Canadian law - it is a container. What is inside decides how long you must keep it, and whether you should.
Provider redundancy protects the provider from hardware failure. It does not usually protect you from a deleted folder, a compromised account, or a lapsed bill. And the record-keeping duty in Canadian law sits with you, not your host.
A staff departure is the moment small businesses quietly lose customer history and create privacy exposure at the same time. Here is the order of operations - revoke, convert, redirect, decide - and the honest judgement call about reading a departed person mail.
Most new businesses buy a paid mailbox for every address they want to exist. You almost certainly need two or three real mailboxes and a dozen aliases. Here is the difference, and why info@ and sales@ should own your customer conversations instead of a personal address.
Owners hear "we use encryption" and assume mail is private end to end. It usually is not. A plain walkthrough of the three layers, why server-to-server TLS is opportunistic by default, and the small number of cases where that is not good enough.
Three records, three different jobs. A plain-English walkthrough of what each one authenticates, why DMARC alignment is the piece that matters, and the policy order that keeps you from blocking your own mail.
Nobody publishes the exact scoring rules that decide your inbox placement. But most spam-foldering traces back to a handful of things you can check yourself in an afternoon, and the standards say exactly what they should look like.
The professionalism argument is the weakest one. The real differences are legal identification, mail authentication, staff control and the fact that a domain is an asset you own rather than one you borrow.
Send a note straight to the team. We read every one and fix bugs fast.
🏆 Find a real bug? We pay a bounty — credit toward Maple products or services for any valid bug.