Mailinglist Archive: opensuse (4600 mails)

[Enrique Arizón <e_arizon_benito@xxxxxxxxx>]

...
> 
> 	Issue 1 (and most important)  Red Hat Enterprise
Servers Postfix is
> broke.  I installed the Postfix and ran switch mail
> to enable it as
> default.  Then configured /etc/openldap/ldap.conf,
> /etc/ldap.conf and
> /etc/openldap/slapd.conf  I also ran authconfig and
> checked pam.d and
> nsswitch to confirm all enteries had taken.  I
> configured postfix (as I
> had done in SuSE which worked great) and ran postmap
> with an
> ldap:virtualldap. and I got segfault.  Just to make
> sure I was not being
> stupid I went back double checked it all and redid
> the whole process in
> SuSE 8.2 pro (worked there but not in Red Hat)  I
> also installed Webmin
> and even it tells me the ES3.0 postfix does not
> support LDAP.  Being
> tired of it after the third attempt I installed
> Postfix from Red Hat 9.0
> (I saw some people where using it for OpenLDAP) and
> it works great. (all
> without further editing my configuration files)
> 

 What's clear is that paying more for licences doesn't
make you more happy. If Postfix doesn't work it just
doesn't work. You can investigate with strace, ltrace,
... what's going wrong but you will loose too much
time.

 Just based in my own experience, if you are going to
install a mail server or any other critical software
for RedHat/SuSE/Debian  build it from sources. Don't
trust precompiled packages at all. And then write down
the configure options you passed to configure and keep
them  in a secure place. 
 Use something as ./configure
--prefix=/opt/_my_custom_postfix_ver.x.x --... so your
custom build don't mix with the default
RedHat/SuSE/... setup.

 A few weeks ago I had similar problems with the
default squid proxy-cache installed with SuSE 9. It
was precompiled with many unnecesary options and a
memory leak nearly blocked the server. By just
compiling from sources and removing all the unnecesary
option in the  "./configure" step the software runs
now really well. It took no more than half an hour to
study the "./configure --help" options, compiling and
installing as service.

 You can also use static linking to improbe system
independence, but you will need to recompile if some
security hole is  been discovered in dependant
libraries.