3 ms·
> ... by letting you use your own domain. Much like email ... It's getting harder and harder to send email from your domain without being send to spam, bouncin
by gus_massa 4y ago
> ... by letting you use your own domain. Much like email ...
It's getting harder and harder to send email from your domain without being send to spam, bouncing, or the server just discarding your email without notice.
- Godel_unicode 4y agoSending it from your own domain isn’t hard, it’s self-hosting that domain which is hard. If you pay Microsoft or Google using your own domain works well.
- EVa5I7bHFq9mnYK 4y agoI use smtp2go for sending, it's easy to setup your domain with them, and they are free for low volume (1000 emails/month) senders. Emails never get rejected, guess they know their game.
- justinclift 4y agoCo-incidentally, we (sqlitebrowser.org) switched most of our stuff to them over a year ago, and yeah they've been hassle free. Currently using their lowest paid tier US$10/month, as that's 10k emails a month which is far more than we send. At least at this stage. ;) Wish they'd occasionally look over the PR's submitted to their GitHub repo's though. ;) eg: https://github.com/smtp2go-oss/smtp2go-go https://github.com/smtp2go-oss/smtp2go-go
- nicoburns 4y agoIt is, but OpenID didn't have this problem because requests were always initiated by the other party.