Own Your Email Identity: Why a Domain Makes Your Address Portable
An address on a domain you control keeps working when you change mailbox providers. An address on someone else's domain does not.
read >An address on a domain you control keeps working when you change mailbox providers. An address on someone else's domain does not.
read >Address hygiene when registering for services: plus addressing, aliases and unique passwords, so one leak does not expose everything you use.
read >Greylisting temporarily rejects unknown senders and accepts them on retry. It stops much bulk spam with little overhead, at the cost of a delay for first.
read >Logs help operators run mail reliably, but they also record who talked to whom and when. Here is which operational logs a mail service needs and why keeping.
read >Standard PGP and S/MIME encrypt the body but leave the subject visible to every server on the path. Protected headers move the subject inside the encrypted.
read >A lost PGP private key cannot be recovered by a provider. Plan ahead with a revocation certificate, an encrypted backup and a restore procedure you have.
read >Practical habits for people who handle sensitive information by email, covering what to leave out, how to address and share, and how to clean up after yourself.
read >How business email compromise works, why authenticated mail still gets through, and the controls that stop payment and data fraud.
read >Autocrypt exchanges OpenPGP keys in ordinary email headers to enable opportunistic encryption, and what that convenience costs in trust.
read >Email keeps copies of a password in many places it cannot be recalled from. Here is where a sent password ends up, why transport encryption does not solve it.
read >Receiving servers judge a sending IP by its reverse DNS, its forward confirmation and its history. Here is how to check each one.
read >A catch-all mailbox accepts mail for any name on a domain. It removes friction and adds spam, backscatter and filtering work.
read >