3 ms·
You can easily demonstrate the veracity of your statement by letting us all know what publicly-accessible server we can access to read your email, without using
by nateabele 14y ago
You can easily demonstrate the veracity of your statement by letting us all know what publicly-accessible server we can access to read your email, without using violence and coercion (for which 'government power' is a euphemism) against a service provider to circumvent your 'authentication'.
- sliverstorm 14y agoI think you are making the same mistake as some other people in this chain. We are talking about SMTP, not IMAP. You don't need violence or coercion to sniff unencrypted mail in-flight. To prove to yourself that SMTP is primarily concerned about authenticity over privacy, just try setting up your own mail server. Ensuring your mail is not blocked and/or marked as spam is an involved process of establishing multiple checkpoints re-confirming your identity. DKIM, SPF, domainkeys- each intended to establish that you sent this (unencrypted) message, and not someone pretending to be you.
- superuser2 14y ago>You don't need violence or coercion to sniff unencrypted mail in-flight. Google won't hand you a packet capture from eth0 on smtp.gmail.com because you asked nicely. You would have to coerce an insider (or exploit your way in). The only situation in which your statement applies is if you're abusing a position of trust as a network administrator. While it's true that this is possible, it's also possible for someone to break into your (postal) mailbox. You still have an expectation of privacy.
- sliverstorm 14y agoYou don't need a tap on smtp.gmail.com to listen to a message leaving smtp.gmail.com