3 ms·
> My MUA would not be rejected by the destination host if the recipient uses the same host as me. Your MUA would be rejected if it acted as an MTA and connecte
by sedachv 10y ago
> My MUA would not be rejected by the destination host if the recipient uses the same host as me.
Your MUA would be rejected if it acted as an MTA and connected on port 25 without authenticating. "Using the same host as me" is the case because the mail server knows that it is "your host" because your MUA is connecting to your email server's MSA using SMTP AUTH on port 587 or 465.
- extra88 10y agoWell now you're moving goalposts, qualifying connections by port and authentication. I'm sure what you write is true of most ISPs and major email service providers but there are still SMTP servers in the world that don't require all MUAs to make authenticated connections; there's at least one at my university.
- loup-vaillant 10y agoThey don't require authentication because they only accept relay requests from within the university network. Otherwise they'd be an open relay, and those tend to relay spam as soon as spammer spot them, then they get blacklisted by most spam filters. In any case, this doesn't affect my main point: by using those, you still don't send your email yourself. In my book, "sending your own email" means you operate your own mail server, without using any third party relay (not Gmail's, not your ISP's). I'm personally halfway there: I have root access to a virtual machine on the cloud (gandi.net), and configured it to relay my email for me. Next step would be to have physical control, but I kinda abandoned that idea when I learned that residential IPs are blacklisted (Hotmail even made it an explicit policy, it won't even appear in the recipient's spam folder).
- extra88 10y ago> In my book, "sending your own email" means you operate your own mail server Virtually no one else reads that book. To everyone else, the user operating the MUA is sending their own email.
- sedachv 10y agoIf you use Gmail via webmail at https://mail.google.com https://mail.google.com or have a MUA like smtpmail.el in Emacs connect to smtp.gmail.com, Gmail is still sending your mail.
- cwyers 10y agoThis is like saying that unless you own your own post office, you're not sending your mail, the US Postal Service is. Nobody talks like that.
- loup-vaillant 10y agoWe trust the postal office to act as a reliable dumb pipe. Most email services are far from that: they filter inbound email in a way you have little control of. They spy inbound and outbound mail, and use that information to send you ads. Also, they control your right to send and receive email: if your account is terminated for some reason (they reserve the right to, blah, blah), you cannot move to a new provider, or redirect inbound mail or nothing: they own your email address. Still think your send your own email? Fool.
- cwyers 10y agoI mean, if you want to make the point that e-mail is not secure, you can say "e-mail is not secure." That's a statement that actually makes sense. Your false pedantry isn't convincing anyone to agree with you, it just makes you sound like a crackpot.
- loup-vaillant 10y agoOh, it's much worse than "email is insecure". It's more like "somebody else controls your email, and they don't have your best interest in mind". What did you think Alphabet was, a charity? Besides, there's more to it than (in)security. For instance, what happens to your various accounts tied to your email if your account gets terminated? You will not be able to redirect your incoming emails, and notifying your friends will be difficult if you relied on the web interface's address book. Also, it's a hole ecosystem: if you use a big webmail, then you allow your provider to spy on everyone you exchange emails with. If you have the means to avoid those, it is your responsibility to do so. Surely you don't like inflicting this kind of spying on your friends, do you? So far, the only reliable way to have proper control over our own email is to control our own domain name, and operate our own mail server. Or at least use small, trustworthy providers. In other words, "send our own email". It's intellectual property/monopoly all over again. One will chose the terms that suits one's side of the debate. I side for privacy, security, and reliability; and argue that webmail providers do not provide any of them. This thread is the first time my "sending one's own email" wording hasn't been an unmitigated success.