I really like qmail-toaster and qmail in general (using it for 4 years
now!), but it's extensibility is not the best.

It's what happens when you can't distribute modified source. If DJB
would open up his license, it'd probably be easier.

You must patch to get a new feature all the time.

True. We try to keep it current.

Moreover if you want to make a change on chkuser you should play with race
conditions!!! :-P (search wiki for chkuser :-P)

That's not a race condition, as much as a way for users who don't know
rpm to make chkuser changes.

You could just as easily create a patch for chkuser settings and apply
those, as I have a few times in the past. Writing documentation on rpm
doesn't make sense for a mail project, so unless you're willing to do
your own research, then we have put this simple work around for all to
do.

I think implementing qmail-spp (http://qmail-spp.sourceforge.net/) and
deploying the (SMTP) patches with plugins should be a good idea.

It's a bit complicated to do, and it's slower since the whole thing is
written in perl. We prefer C based stuff for speed.

Feel free to write instructions for integrating qmail-spp. I'd add a
link from my page or the main page if there is interest.

That let sysadmins choose their own patches :-)

Currently all of the patches we have are able to be disabled by configuration.

There's something like that for qmail-send ? (e.g. for implementing DKIM
signing and the like)

???

---------------------------------------------------------------------
    QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to