It looks like it would be a 1-line patch to new-inject and ofmipd in DJB's mess822. Just drop the header in the very same way that they already drop "Bcc:".
Erwin Hoffmann could probably be persuaded to add it to s/qmail.
"Note that the original Qmail site is gone" says the #Dovecot doco.
A quick check confirms that http://cr.yp.to/qmail.html is still there and has been all along.
It turns out that the Dovecot doco writers didn't know where #qmail originated, and thought that http://qmail.org was its original WWW site. But a quick check reveals that even that is still there, too.
@kevintechie @qurlyjoe @odo2063
It's generally not the direct-to-consumer hosting companies but the B2B and corporate e-mail world where one might find that this isn't the case, and minus and plus are just considered ordinary characters as of old.
There was a FediVerse post, alas that I did not bookmark, about a month ago where someone found yet another WWW site that didn't allow the plus character in its sign-up forms that require mailbox names. Still happens.
@qurlyjoe @kevintechie @odo2063
... that is not strictly true. It depends from how local delivery works and what MTS is in use. Some mail systems do this, others do not.
It was an invention of the 1990s, long after the invention of Internet mail itself. Not everyone copied it; it wasn't a plus sign originally; and some WWW site softwares that don't parse mailbox names correctly even end up mangling or outright rejecting it.
#qmail qmail is a satisfactory MTA if you're willing to do away with some modern comforts like using Milters, and IPv6 and TLS outbound, and a few other things. Being able to have these modern comforts is a high priority of the single developer of Nightmare Mail (that's us).
People using #qmail have been carefully applying patches for _decades_ to get #STARTTLS, #AUTH, and other basics.
This will change.
How should notqmail be shaped so that modern features like these are easy to land? I've collected some thoughts: https://github.com/notqmail/notqmail/wiki/Designs
As we work toward notqmail 1.09 and beyond, we’d like to hear from more folks who’ve…
1. Updated your #qmail or netqmail installs to notqmail. (Yay! Anything tricky?)
2. Tried and failed to update. (What blew up?)
3. Decided not to try yet. (What were some of your reasons?)
notqmail 1.08 is out. Vulnerabilities and other bugs fixed, compiler warnings reduced, dead code pruned, presumed-dead code put on notice, my QMAILREMOTE patch added, and lo and behold, our first few unit tests.
More: https://schmonz.com/2020/05/20/notqmail-108-released/ #qmail #notqmail #smtp
On his Programming Leadership podcast, Marcus Blankenship and I talked about building a collaborative open-source team in a software community with a long history of… not that. https://schmonz.com/talk/20200110-programming-leadership/ #LegacyCode #qmail #notqmail
In March, for the New York City BSD User Group, I expressed a wish to avoid creating yet another #qmail fork.
Tomorrow’s #NYCBUG talk is about my failure — notqmail is alive and well — and our success with it so far.
#qmail #nycbug #legacycode #c #dev #smtp
If you’re still running #qmail, please
1. Update your systems to notqmail 1.07, released earlier this week
2. Let us know easy it was
3. Give us your thoughts about our roadmap
More info: https://schmonz.com/2019/08/20/announcing-notqmail/
Announcing the initial 1.07 release of notqmail, a community-driven fork of #qmail that begins where netqmail left off: https://notqmail.org/1.07
Themes for this release:
- Fix broken builds (FreeBSD, macOS)
- Make packaging easier
I'm proud to be one of several developers bringing this valuable #LegacyCode back to life. Here's my personal blog post telling this first chapter in the story of notqmail: https://schmonz.com/2019/08/20/announcing-notqmail/
#qmail #smtp #pkgsrc #legacycode #legacycoderocks #c #dev
When we’re responsible for production, it can be hard to find room to learn. That’s why I run my own email server. I own all the decisions, take more risks, and have learned lots. And so can you.
NYC, this Thursday: https://schmonz.com/talk/2019-devopsdays/
#pkgsrc #qmail #devopsdays #devops
I've shipped quite a few improvements for #qmail users in the 2018Q4 release of #pkgsrc, the practical cross-platform Unix package manager. In one sentence:
It's probably easy for you to run qmail now.
With more sentences and a demo: https://schmonz.com/2019/01/07/2018q4-qmail-updates-in-pkgsrc/
Do you use #pkgsrc on non-#NetBSD? Do you _not_ run #qmail?
Great! Please update to pkgsrc-current and test two packages for me: https://mail-index.netbsd.org/pkgsrc-users/2018/12/17/msg027809.html
(NetBSD and/or qmail users, happy to hear your results too.)
Today's update to my SMTP AUTH implementation for #qmail now also provides TLS for message submission and incoming deliveries, without patching! More: https://marc.info/?l=qmail&m=154171120706990&w=2
As always, if you use #pkgsrc, just get the latest qmail and qmail-run. :-)
I've shipped my SMTP AUTH implementation for #qmail. It's designed to avoid patch conflicts, add new user-controlled features, and perhaps offer desirable
security properties. More: https://marc.info/?l=qmail&m=154048252009339&w=2
If you use #pkgsrc, just update to the latest qmail and qmail-run. :-)