3 ms·
There are tools to make use of HTTP in all sorts of ways. Curl, Wget, Restful APIs, Sinatra, Grape, etc. Fast, flexible, lightweight. Email - not so much. W
by andyl 12y ago
There are tools to make use of HTTP in all sorts of ways. Curl, Wget, Restful APIs, Sinatra, Grape, etc. Fast, flexible, lightweight.
Email - not so much. Want a local email server? There's Postfix - yuckkk. The overhead of spam - yuckk. The lack of tooling, the lack of configurability, the DNS complexity. The fact that it requires a SAAS to do shared inboxes. Yuck.
Email could be so much better.
- ah- 12y agoCheck out OpenSMTPd, that makes setting up an email server so much easier. It's still far from what it could be, but pure bliss compared to Postfix.
- aaronem 12y agoWhat's wrong with Postfix? Sure, configuring it takes a little work, but it's not hard, especially not by comparison with Sendmail, which was the standard everywhere when I began my career.
- _delirium 12y agoI didn't even find configuring Postfix to take much work, and I'd never configured a mailserver until a few months ago. Debian's config script autogenerated a basic configuration for me, after prompting with a few questions: receive email for my domain to my unix account, and relay mail only from local or AUTH'd clients. This is the entirety of the manual config I added on top of what Debian produced: # use maildir instead of mbox home_mailbox = Maildir/ # reject obvious spam smtpd_client_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unknown_client_hostname, reject_rbl_client zen.spamhaus.org It has a very nice manual too, but I have not had to use most of it, because it just works out of the box.