>> Why hasn't your rejected idea been worked into qpsmtpd yet? > > Because I came to view qpsmtpd in a different way than many > do (many view it as a service with useful plugins which they > can deploy, use, and enjoy). Instead I view it more as a > framework for rejecting/processing/handling mail that happens > to come with some nice sample code.
I'd lean toward agreeing with this take on things. It's difficult steer changes to the core set of QP plugins because so many people need different things. We've wound up creating a huge fork of all the plugins (and to some extent forked QP libs in support of these plugins), and although we've submitted some of these changes back, many of them wouldn't make sense for all of QP's intended audience. It might be *possible* to fashion things to be flexible enough or with conservative enough defaults that it would work for everyone, but unfortunately once we get things working for ourselves we don't currently have the resources to work much further on things. I idly wonder if it might be worthwhile to offer some sort of repository of whole plugin frameworks that users and/or developers looking for idea could pull in as a whole in order to use them together. For our own situation, we might be able to offer our whole set of plugins (after submitting some library changes needed) and have that be a useful submission to the public, and useful for folks like you looking for ideas for your own development, and useful for enhancing the core QP plugins. -Jared
