Password Managers and Email: Unique Aliases and Safe Recovery
Use a password manager alongside your mailbox without making it a single point of failure, and give each service its own address.
read >Use a password manager alongside your mailbox without making it a single point of failure, and give each service its own address.
read >How DANE and TLSA records secure SMTP using DNSSEC, what the DNSSEC dependency means in practice, and a candid comparison with MTA-STS.
read >Practical inbox and device habits for travel, covering public Wi-Fi, shared computers, lost devices and phishing aimed at travellers.
read >Practical ways to back up email: mbox exports, one-way IMAP mirroring with mbsync or imapsync, and encrypting the archives you keep.
read >What happens between pressing send and delivery: submission, MX lookup, server-to-server TLS, checks, queues, retries and bounces.
read >Which attachment types deserve suspicion, why archives and macros are risky, and how to open unexpected files with less exposure to malware.
read >Using one address per service to limit correlation, trace breaches to their source, and shut off spam, with the limits of aliases.
read >S/MIME trusts certificate authorities, while OpenPGP trusts keys you verify yourself. Compare the trust models, client support and daily usability.
read >Why long random passphrases beat short complicated passwords, how to generate one with dice, and how to manage app passwords and a vault.
read >Attackers register domains that look like yours or your contacts'. Here is how the common tricks work and how to check for them.
read >Email was designed for store-and-forward delivery between many untrusted relays. Encryption was added later, in layers, and never became the default.
read >