• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 513
  • Last Modified:

Qmail Installation from qmailrocks.org

I am trying to get qmail installed on a RHE3 server. I had some issues initially and installed GCC and the installation started but cannot get past the third step.

Any ideas ??

Here is the installation section and the results :

Ok, so enough talk. Let's apply these mega-patches and get this patching business out of the way...

/downloads/qmailrocks/scripts/util/qmail_big_patches.script   (click here to view this script)

Now we build Qmail...

cd /usr/src/qmail/qmail-1.03

make man && make setup check

./config-fast your_fqdn_hostname (ex




[root@local qmail-1.03]# make man && make setup check
make: Nothing to be done for `man'.
./load qmail-lspawn spawn.o prot.o slurpclose.o coe.o \
sig.a wait.a case.a cdb.a fd.a open.a stralloc.a alloc.a \
substdio.a error.a str.a fs.a auto_qmail.o auto_uids.o \
auto_spawn.o
spawn.o(.text+0xc0): In function `okwrite':
: undefined reference to `errno'
spawn.o(.text+0x530): In function `getcmd':
: undefined reference to `errno'
collect2: ld returned 1 exit status
make: *** [qmail-lspawn] Error 1
0
nashsupport
Asked:
nashsupport
  • 2
  • 2
1 Solution
 
jlevieCommented:
I'd guess that either something didn't go right in the patching or something in the configure failed.

Why would you want to install qmail on RHEL? It is furnished with a supported version of Sendmail (the "Gold Standard" of MTA's) and Postfix. By switching to Qmail you've lost part the usual reason to use RHEL (supportability) and will now have a non-RedHat package that has to be separately maintained.
0
 
nashsupportAuthor Commented:
Interesting, did not know that and was informed to try and go this way due to security issues with sendmail.

what is your feeling on security issues ??
0
 
jlevieCommented:
It's been a long time since there was an exploit against Sendmail in the wild. Yes, from time to time things have been found that could be a problem, but the security fix has always been available before an exploit starts to circulate. And, since the early days of Sendmail, it has been redesigned to limit the impact an "as yet not found vulnerabilty" might have. Because Sendmail is so widely used there are a lot of folks reviewing the code for even the most obscure vulnerabilities and reporting then in a responsible manner, which leads to any such vulnerability being quickly fixed.

RedHat is very proactive in making security updates to RHEL, which means that keeping your system up to date virtually eliminates any risk of a vulnerability due to a flaw in the code for some application. Once one starts adding third party code to the server that advantage is gone and it becomes up to you to monitor all of the various security alert channels for flaws in things that you've added (and then having to fix them). Personally I've got better things to do and prefer, where ever possible, to use the RHEL packages.
0
 
nashsupportAuthor Commented:
thanks for your comments, you are very helpful and have used numerous posts for fixes.

take care
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now