Re: eQmail or s/qmail
Erwin Hoffmann <[email protected]>
| Newsgroups | gmane.mail.qmail.general |
|---|---|
| Message-ID | <[email protected]> |
Hi Pascal, after Manvendra and Kai promoted their 'products', let my give you my comment: a) As Manvendra said: Try and evaluate all three qmail successors. b) Over the last decades, qmail developed like a garden without gardener. c) There are tasty fruits and basic fruits which need to be planted. Three of those I tried to grow up, thus you can harvest those: IPv6, Auth, and TLS (within s/qmail). d) You seem to have other tastes. I don't know about 'assp', nor about SRS (not yet; SPF is on my list). Thus, I have no expertise to provide add-ons for any of those (however, this could change). However, currently I don't see any 'convergency' to join all the activities together into a common platform. Two give you two examples: - exim (Phil Hazel) seems to be used like a brick yard (on Debian). - Postfix (Wietse Venema) is a strong focused project (everywhere). At first, because we - as developers - like to protect our work; we are all 'egomanes'. Second, because we simply have too different views on the 'real qmail world'. What I try to do, is to provide a solid code base (and the right ideas). Documented, functional, in the spirit of DJB. I do this partially for my students to teach them how to do things (right). Minimalistic, no 'stdio', no MySQL, no SASL; OpenSSL is hard to avoid. Very few dependencies. Working on current systems. This is my 'philosophy' - which might not coincident with your expectations. I'am glad, that my enhancements made their way to 'other products' as well. Again: Your choice. Anyone's choice. Free software. Free to 'mod' it. I would be happy, if qmail.org (Russ Nelson) would reflect those thoughts. Best regards. --eh. > Am 21.04.2016 um 11:00 schrieb Pascal Nobus <[email protected]>: > > Since the previous century we are running several mailservers on qmail, > serving around 6000 domains with about 4000 mailboxes. > > All systems are based on the original Qmail-1.03, with the standard > patches, and all run on a single UID, based on Paul Greggs howto: > https://pgregg.com/projects/qmail/singleuid/ > > Spamfiltering is done in front of Qmail, with assp. So no hookups needed > for this. (assp listens to port 25, qmail to port 125) > > Ezmlm is also in use. > > > Because of the several patches the last years (some have TLS, other > IPv6, some both, some none of these), we want to make a new fresh start > with compiling qmail on our servers. > Our systems are mixed-OS's, most run on Slackware, some of them on > CentOS, so I want to compile the things myself. > > > Which package should we follow? > eQmail, s/qmail, or are there others? > > Any tips are welcome. > > Best regards, > Pascal Nobus > Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: EE00CF65 Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id: EE00CF65
signature.asc
(application/pgp-signature, 842 B)
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJXG9bGAAoJEIP8+SDuAM9lqT8QALi95Hlc59ZD7zYLfcNy+bh5 v0K7FZdCgAypWD6pcilW9iS5AWPtbMpF1FEuXxEUIGzw650F/alr9kKOj4FOOkor U3XNB5uMasWkN89xqdLNwOk4m5CKoSJtMcpYCMCk7VM23xRaHI5UWTNkAGJeedUC JouDyp19dhD8i4JaWj/PPj7Q+xNeNLn2DztBGTex/nZfq9WIpQfaioDl76J1DCoP BIX45s0goc6FIAwTjEWBrOM+XIQEa4s6+nT047iP4WtK+9LqoK6VahFgPs37G0lE BiJGoBTxYD0UiD0Faw9Ex4/iTv71G9WMy7O8zeQxI2ZdG4ndICvApHWwYwQqodpD p6jxGB66XEYe3yqTGj8NP+4qb3Z14rEZu2/D9LM7aQkDXVUPKsYnIUw3zDo+1diq LM+9pYDLqS1xEVnDGvZZYQ0LAgWiC2c+onKAjOkhaOv/e7OLjTmaFPdwCqYVrvXW OS7ioSgYw7DOHIzAv3s90HKoque8u2UU9h1pMQYI/nzQBjm9MLQTIi5f4JXGHxJL IPQ5LkGo08QCadpNH3dPvZnv5pHvTO5+zZhC0nl066AYTZrpuJt0LpyJ02FAutSk 9zbGlGCnmS9AMvg1+uwq9z40pDzJAK73g4u7zmC2F/vvBQw1GulSYTgDAxqxb1V+ hAHkuBA0Xi6QcSOAu2GX =VDO1 -----END PGP SIGNATURE-----