Fair. To a certain mindset, "self-hosted" is its own advantage -- but to pick a couple of advantages out of thin air:
+ Free: I can run Postal on my own hardware, with no usage limits or costs other than the VPS or AWS costs (which I'm paying anyway)
+ Independent: I'm not relying on a third-party to provide core features. If SendGrid goes down there's nothing I can do about it
+ Private: Maybe I don't want to hand over a list of my user's email addresses to SendGrid.
Self-hosting services means I maintain control over them. It's a tradeoff, and you may value control less than, say, convenience. YMMV.
I feel like you're still begging the question. The proposition is not really "SendGrid vs Self-hosted SendGrid", but "Self-hosted SendGrid vs any IMAP/SMTP server":
> Free: I can run Postal on my own hardware, with no usage limits or costs other than the VPS or AWS costs.
So is postfix.
> Independent: I'm not relying on a third-party to provide core features.
What features? This is the crux of the question. What do you actually need that justifies having to maintain a web application?
> Private: Maybe I don't want to hand over a list of my user's email addresses to SendGrid.
Imagine a retail business that relies on emails to get information on what's next: what are the most popular products, what's a good tag line, which segment of its customers are interested by what, who is most likely to buy. Sendgrid allows you to add A/B testing, scheduling (send a % of emails at a specific hour), track who opened emails when, track who unsubsucribed.
If you are doing simple emails like email confirmation or simple user reminder, these features are totally overkill. But email has still the best ROI for many businesses and thats why they need sendgrid
> Think Sendgrid, Mailgun or Postmark but open source and ready for you to run on your own servers.
Your comment fails to answer the question: "Did this HN user even RTFT(itle)?"