Re: eQmail or s/qmail

I want to thank you for your response overall.

> First I tried to install eQmail, however I bumped into ipv6 and
> SSL-support for tcp-server, and insteadoff patching it myself, I
> downloaded it from fehcom.
ucspi-* is a separate package and not part of eQmail :-(

> P.S.
> Why not bundle your works eQmail s/Qmail and Indimail in one project?
> If you bundle your strength you could be the leader in MTA, replace the
> awfull (my personal opinion) exim/postfix.
Hmm, that's a strange point. Always IMHO:

Overall it will be hard to reanimate (net)qmail to growth in public 
attention again. There is a (hard) core of users, but most of the main 
distributions didn't provide/assist (net)qmail as a package anymore. Why 
ever, there were a lot of mistakes made in the past. I question if this 
can be corrected. At the moment I would say (net)qmail is dying slowly 
but continuously.

I couldn't say a lot about s/qmail or indimail. eQmail is one of 
multiple private forks using popular patches and some individual 
changes. Just published more successful. On the other side this shows 
that there is still an interest. Back, differences in short:

- s/qmail is academic, not what I want as administrator
- indimail is leading in up-to-date functionalities and its history
- eQmail is minimalistic, less (should be) is more (its like I wanted to 
se netqmail-1.07)
- other derivatives of (net)qmail with lesser attention differs minimal

Getting the work of Erwin, Manvendra and me together is not enough. The 
community have to contribute too. Starting with feedback, wishes and 
expectations. Former and new contributors. Than it will make sense to 
think about a coordinated project.

Just some high level thoughts. Keep in mind: IMHO!

-- 
----
Sent with eQmail-1.10-dev