Amitai Schleier

Dang it, I keep forgetting that linking a PR to an issue makes the issue close when the PR does. The approach in #211 (incrementally enable specific warnings in `conf-cc`,...

The TODO item immediately following ("eliminate token822, headerbody, hfield") seems very likely related.

One possible way to [implement STARTTLS and AUTH on port 587](https://github.com/notqmail/notqmail/wiki/Designs#port-587-ipv6-and-mandatory-starttls-and-auth) involves importing mess822's `ofmipd`.

#20 and #53 suggest the `Makefile` was not being auto-generated.

My inclination is, we keep shipping the Makefile and gradually require less effort to keep it updated. People building notqmail source needn’t learn anything new, just those of us hacking...

Having notqmail available in system-native package repositories is an explicit [goal](https://notqmail.org/goals-and-non-goals/), "Being easily packaged by OS integrators". It sounds like you're seeing a conflict with our explicit [non-goal](https://notqmail.org/goals-and-non-goals/), "Breaking compatibility...

Given our goal of supporting packaging, I agree that it's necessary for us to support FHS-compatible installations, and that manual pages (and commands, for that matter) should not require users...

IRC discussion with @alanpost clarified that "FHS" carries with it two related but distinct goals. Attempting to summarize: 1. "FHS-aware": By default, we want notqmail to install files to FHS-compatible...

At least for the near term, and possibly much longer, "FHS-strict" builds won't be the default. This is an excellent reminder that when we introduce the FHS-strict build option in...

Expecting to need to do the same with [tlsonlyremote](https://schmonz.com/qmail/tlsonlyremote/) for pkgsrc. Users of our packages almost certainly don't mind (or know, or care ;-) that we do that for them.