Unfortunately, the Redhat Enterprise 4 mail server at my new job had up2date configured to autoupdate, with old package storage and rollbacks disabled and no other backup*. It installed exim, sendmail, a kernel update and several dozen various updates and dependencies
I've since restored all of qmail's functionality, save email sent to ezmlm mailing lists. This does not work on the pre update kernel or the newer one Whenever a message is sent to a list the mailer-daemon returns the following error to the sender
<list@do.ma.in>:
Incorrectly built binary which accesses errno or h_errno directly. Needs to be fixed.
ezmlm-reject: fatal: List address must be in To: or Cc: (#5.7.0)
Now I checked the up2date logs and I didn't see glibc listed. All the same we have 2.3.4 release 2.25 installed. wondering what the best course of action would be. We can't afford any more serious downtime, so the most straightforward option is the most desirable, as I can work on an alternate solution while it's working. I suspect it is ezmlm that is generating the execution error, as qmail works in all other respects.
would using rpm with --oldpackage to install an older version of glibc take care of this error? any patches for the current executables exist or are they solely for patching source?
any links to documentation regarding comprehensive lists of qmail/ezmlm files to back up before attempting a rebuild would be appreciated as would links to recommended patches.
* the rh/qmail/ezmlm server was set up by a consulting company that was fired for incompetence. i've been trying to make sense of it for the past 3 weeks or so.
Edit/Delete Message
I've since restored all of qmail's functionality, save email sent to ezmlm mailing lists. This does not work on the pre update kernel or the newer one Whenever a message is sent to a list the mailer-daemon returns the following error to the sender
<list@do.ma.in>:
Incorrectly built binary which accesses errno or h_errno directly. Needs to be fixed.
ezmlm-reject: fatal: List address must be in To: or Cc: (#5.7.0)
Now I checked the up2date logs and I didn't see glibc listed. All the same we have 2.3.4 release 2.25 installed. wondering what the best course of action would be. We can't afford any more serious downtime, so the most straightforward option is the most desirable, as I can work on an alternate solution while it's working. I suspect it is ezmlm that is generating the execution error, as qmail works in all other respects.
would using rpm with --oldpackage to install an older version of glibc take care of this error? any patches for the current executables exist or are they solely for patching source?
any links to documentation regarding comprehensive lists of qmail/ezmlm files to back up before attempting a rebuild would be appreciated as would links to recommended patches.
* the rh/qmail/ezmlm server was set up by a consulting company that was fired for incompetence. i've been trying to make sense of it for the past 3 weeks or so.
Edit/Delete Message