2 ms·
Yes but that's the recipient choice. I'm not responsible if they use American cloud providers for their emails, but I am for the ones I send.
by speedgoose 5y ago
Yes but that's the recipient choice. I'm not responsible if they use American cloud providers for their emails, but I am for the ones I send.
- BusyLurker3K 5y agoSure, then you can use whatever SMTP option that is best for you. Some people are fine with using American cloud providers and some are not. If they are technical enough to host their own email server, they are more than likely to understand what choices they are making.
- speedgoose 5y agoMy main point was that sending email using AWS SES is not self hosting. Like hosting a website on S3 + CloudFront is not.
- blitzar 5y agoI believe the correct way to write it is self-hosting.
- BusyLurker3K 5y agoThat is _your_ definition of self-hosting. Do you rely on an entity for your internet connection? At some point, you _will_ need to rely on someone else's infrastructure.
- xanaxagoras 5y agoIf you run your own incoming mail, nobody but you has a copy of your entire mail archive and you are self-hosting that data. It can't be handed over to the government, it can't be sold, it can't be analyzed by gmail, etc. That's where the big win is. If you send e-mail using SES, that's one untrusted hop out in front of an unknown number of untrusted hops that you can't opt into or out of - there's little practical difference. The privacy win come from hosting your own data, not your own smtp server with a carefully curated reputation that you spend hundreds of hours a year working on.