Top all-time · #20543
Y
Yareev's schmonz.com
Personal blog · schmonz.comprogrammingsystems
Yareev's schmonz.com is a personal blog at schmonz.com about programming and systems. Since 2014, 3 different Hacker News readers have linked it 9 times. It is still writing: the last post was on 2025-11-12, and you can follow it by feed.
9mentions?
3HN people?
2014–2024first – last linked?
What Hacker News says?
Vanilla qmail was never an open relay unless you really intended to configure it as one. It's just that the only relay controls were IP-based. Back in the day, before AUTH was widely supported, I used a really nice "relay-ctrl" add-on from Bruce Guenter for POP-before-SMTP. For mandatory user-facing TLS and AUTH on port 587, and opportunistic server-to-server TLS on port 25, I've written https://schmonz.com/qmail/ac…
Comment linking /qmail/rejectutils
on “Announcing Notqmail”Submitted Announcing Notqmail as a story · 160 points
HN discussionSorry, we think it's rested plenty long enough :-) You've given some excellent examples of how qmail got this way, and what notqmail needs to change to be viable. I have my own running-in-production solutions to most of them -- for instance, https://schmonz.com/qmail/rejectutils for SMTP recipient rejection and https://schmonz.com/qmail/acceptutils for user-facing AUTH and TLS. These may or may not become part of no…
Comment linking /qmail/acceptutils
on “Announcing Notqmail”Submitted pkgsrc on macOS: Still Works as a story · 2 points
HN discussionI recently spent 4.5 years at a big bank developing identity-management tools. They were written in Perl. The first thing I did was screw up in production: http://www.schmonz.com/2014/06/01/tdd-in-context-1-keeping-m... So I started carefully making the code testable, then gradually adding tests and refactoring under them, and gradually adopting and taking advantage of Moose, shipping every month all the while. Ther…
Comment linking /2014/06/01/tdd-in-context-1-keeping-my-job
on “Why Perl Didn't Win”Submitted Cross-Platform Full-Stack Deployment as a story · 2 points
HN discussionWriting Ikiwiki plugins is often very easy, because triggers for most events you'd want to get involved in are available, and because much of Ikiwiki's own functionality is implemented as plugins. Reading and understanding internals, as you point out, can be challenging. Tricky and/or important bits of functionality are often covered by automated tests (and I've test-driven new functionality in: http://www.schmonz.c…
Comment linking /2013/08/22/tdd-by-example-an-ikiwiki-feature/
on “Twenty years of free software, part 1: Ikiwiki”