LWN: Comments on "Announcing notqmail" https://lwn.net/Articles/796794/ This is a special feed containing comments posted to the individual LWN article titled "Announcing notqmail". en-us Fri, 03 Oct 2025 13:06:35 +0000 Fri, 03 Oct 2025 13:06:35 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net switch to postfix instead https://lwn.net/Articles/797745/ https://lwn.net/Articles/797745/ HelloWorld <div class="FormattedComment"> IOW, they don't really have an answer. <br> </div> Thu, 29 Aug 2019 12:04:02 +0000 Announcing notqmail https://lwn.net/Articles/797339/ https://lwn.net/Articles/797339/ schmonz The aforementioned <tt>qmail-remote</tt> refactoring is <a rel="nofollow" href="https://github.com/notqmail/notqmail/wiki/Roadmap#19">slated for 1.9</a>. When that ships, notqmail will support IPv6 for outbound connections by simply replacing ucspi-tcp with ucspi-tcp6 (which already gets you IPv6, today, for submission and incoming). And the same architectural improvement will put us very close to supporting STARTTLS for outbound connections. Tue, 27 Aug 2019 01:25:03 +0000 Announcing notqmail https://lwn.net/Articles/797145/ https://lwn.net/Articles/797145/ vadim <div class="FormattedComment"> How is not handling IPv6 a feature?<br> <p> </div> Sat, 24 Aug 2019 10:54:21 +0000 Announcing notqmail https://lwn.net/Articles/796901/ https://lwn.net/Articles/796901/ schmonz <div class="FormattedComment"> I don't think any of the initial batch of notqmail developers are vpopmail users (so no, we haven't pinged Inter7). Would be great to have your involvement.<br> <p> That's a whole lotta patches, and probably not all of them are mergeable as-is. Guessing some are more specific to your needs and some are useful to pretty much everyone who runs qmail? I'd suggest we start by picking one that's small, widely applicable, and on-theme for our next release (1.08). Hop on Freenode #qmail sometime, if you would, so we can figure out what makes sense as your first PR.<br> </div> Wed, 21 Aug 2019 23:38:12 +0000 Announcing notqmail https://lwn.net/Articles/796898/ https://lwn.net/Articles/796898/ jccleaver <div class="FormattedComment"> Do you have a preferred mechanism for submitting things? Because of the nature of qmail installs it may be difficult and/or require a lot of explanation for various patchsets. I've had RPM's for qmail and and vpopmail for about a decade now, but a quick count shows 87 patches in there. Is there a better way than git pull requests for some of this?<br> <p> Speaking of vpopmail, have you communicated at all with the Inter7 folks on this project?<br> </div> Wed, 21 Aug 2019 22:36:48 +0000 Announcing notqmail https://lwn.net/Articles/796895/ https://lwn.net/Articles/796895/ schmonz <div class="FormattedComment"> Re: s/qmail, I've sometimes borrowed (and then usually refactored) some of his code, and have frequently collaborated with him on improving ucspi-tcp6, ucspi-ssl, etc. I'm still hoping he'll consider participating in notqmail development.<br> </div> Wed, 21 Aug 2019 22:24:42 +0000 Announcing notqmail https://lwn.net/Articles/796892/ https://lwn.net/Articles/796892/ schmonz Making qmail easier to install and run has been a longtime interest of mine. Before notqmail, I focused my efforts on cross-platform packaging in pkgsrc (here's a <a rel="nofollow" href="https://youtu.be/Vq6vu9T3vow">3-minute installation demo on CentOS 7</a>). Now that we're developing notqmail, "Meeting all common needs with OS-provided packages" is <a rel="nofollow" href="https://github.com/notqmail/notqmail/wiki#what-are-the-projects-goals">an explicit project goal</a>, and we've taken some important first steps toward this in <a rel="nofollow" href="https://notqmail.org/1.07">1.07</a>. Wed, 21 Aug 2019 22:24:38 +0000 Announcing notqmail https://lwn.net/Articles/796891/ https://lwn.net/Articles/796891/ schmonz IPv6 for incoming SMTP (port 25, <code>qmail-smtpd</code>) and submission (port 587, <code>ofmipd</code>) is extremely easily had: just replace ucspi-tcp's <code>tcpserver</code> with <a rel="nofollow" href="https://www.fehcom.de/ipnet/ucspi-tcp6.html">ucspi-tcp6</a>'s. For outbound SMTP, one possible option for notqmail is to refactor <code>qmail-remote</code> to use <code>tcpclient</code> for network communication. Then it could trivially be swapped out for ucspi-tcp6's <code>tcpclient</code>. We're glad to hear appreciation for what we're trying to do. Thank you! Wed, 21 Aug 2019 22:24:27 +0000 switch to postfix instead https://lwn.net/Articles/796890/ https://lwn.net/Articles/796890/ schmonz Postfix is very good. We also really like qmail. (From <a rel="nofollow" href="https://github.com/notqmail/notqmail/wiki#why-not-postfix">the notqmail wiki</a>) Wed, 21 Aug 2019 22:24:11 +0000 Exim is the king https://lwn.net/Articles/796873/ https://lwn.net/Articles/796873/ LightDot <div class="FormattedComment"> Looking at the research methodology, out of a total number of 1,775,165 queried mail servers, 838,307 provided SMTP banners that identified them and only those were taken into account.<br> <p> Understandable, but a default banner setting might significantly affect the position of a specific server in the final result of this research.<br> <p> Cpanel might also be an additional reason for Exim's statistical success, combined with the default SMTP banner setting.<br> <p> Plesk on the other hand, supports using Postfix or Qmail. Plesk's Qmail default is not to identify itself, while Postfix's default is the opposite.<br> </div> Wed, 21 Aug 2019 19:47:02 +0000 Announcing notqmail https://lwn.net/Articles/796874/ https://lwn.net/Articles/796874/ jccleaver <div class="FormattedComment"> At this point, not accepting IPv6 traffic is probably a feature rather than a bug.<br> <p> Qmail still has its uses, and it's still (by necessity) far more customizable than virtually any other compiled mail system. I'm glad a new community has formed around continued development and stabilization -- netqmail was a needed effort, but it had a design goal of only including critical or necessary patches, and so couldn't really move the code base or community ecosystem forwards.<br> <p> There's a lot of old qmail/vpopmail code out there that people have written, and a place for the best of it to bubble up into a release will be nice.<br> </div> Wed, 21 Aug 2019 19:35:51 +0000 Exim is the king https://lwn.net/Articles/796844/ https://lwn.net/Articles/796844/ claude.bing <div class="FormattedComment"> <font class="QuotedText">&gt; Exim 4 is currently the default MTA on Debian GNU/Linux systems.</font><br> <p> <a href="https://en.wikipedia.org/wiki/Exim">https://en.wikipedia.org/wiki/Exim</a><br> <p> That would probably give it a boost.<br> </div> Wed, 21 Aug 2019 13:58:46 +0000 Exim is the king https://lwn.net/Articles/796837/ https://lwn.net/Articles/796837/ xose s/Postfix/Exim<br><p> <a rel="nofollow" href="http://www.securityspace.com/s_survey/data/man.201907/mxsurvey.html">Mail (MX) Server Survey August 1st, 2019</a> Wed, 21 Aug 2019 13:45:41 +0000 Announcing notqmail https://lwn.net/Articles/796815/ https://lwn.net/Articles/796815/ LightDot For those interested in qmail, take a look at <a rel="nofollow" href="https://www.fehcom.de/sqmail">s/qmail</a> too.<br> <br> Anyway, Postfix has indeed taken the popularity throne. These days it seems that besides valid criticism, bashing qmail has also become a popular pastime. But on the other hand, qmail seems to be quite resilient to both.<br><br> There are quite a few qmail servers out there and a lot of them are more modern that some commenters here seem to realize.<br><br> It is unfortunate that using qmail is not easier under various distros, perhaps this is something that is worth working on. Wed, 21 Aug 2019 11:49:47 +0000 switch to postfix instead https://lwn.net/Articles/796814/ https://lwn.net/Articles/796814/ ale2018 <blockquote> &gt;Postfix is as secure as qmail [...] I have used both </blockquote> <p>I thought the easiest switch from Qmail was <a href="http://www.courier-mta.org/#features">Courier-MTA</a>, due to its ability to import<code>.qmail</code> files. Wed, 21 Aug 2019 09:52:06 +0000 Announcing notqmail https://lwn.net/Articles/796811/ https://lwn.net/Articles/796811/ Gladrim <div class="FormattedComment"> Seriously? Why? It's 2019. It doesn't even support the modern Internet:<br> <p> <a href="https://github.com/notqmail/notqmail/blob/08a0b794f3c12c7cbfa8e6217028d32cf841c3ba/TODO#L22">https://github.com/notqmail/notqmail/blob/08a0b794f3c12c7...</a><br> </div> Wed, 21 Aug 2019 09:10:12 +0000 switch to postfix instead https://lwn.net/Articles/796809/ https://lwn.net/Articles/796809/ higuita <div class="FormattedComment"> I don't understand why people still trust qmail after all this years... i can understand existent setups, but new setups?!<br> Postfix is as secure as qmail, have lot more features out of the box, do not need patches with unknown security record, it's compatible with sendmail (usage and milters), it's very flexible and scales well ( can be used either as a small local mail service to a huge ISP setup) and have good config.<br> <p> I have used both and while qmail was amazing in 1999/2000, in 2019, it's way too limited and require more work to build a working setup than a simple "apt-get install postfix".<br> <p> Yes, i know it still works after all this years, but also postfix setups from 2000 still work fine today and sendmail setups from 1994 also still work fine... that doesn't mean they should be working still!<br> </div> Wed, 21 Aug 2019 09:03:13 +0000 Announcing notqmail https://lwn.net/Articles/796800/ https://lwn.net/Articles/796800/ rsidd <div class="FormattedComment"> It's remarkable that qmail still has users over 20 years since the last update from its author, and over 10 years since the last "community" update (netqmail). I used it for a long time, before switching to postfix, but these days I use postfix only as an outgoing MTA on my desktop (relays mail from mutt to the local smtp server). <br> </div> Wed, 21 Aug 2019 05:51:57 +0000