From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
Description of problem:
Sep 9th RPM updates:
When installed, these RPM's will cripple sendmail.
Sendmail refuses to accept connections on port 25
A quick diff of the new sendmail.cf file indicates that naming structure
for db files may have changed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Update sendmail with RPMs
2.Try to open port 25
Actual Results: Access Denied
I just got the same problem.
I'm using a separate sendmail.cf
Updating from sendmail-8.11.0-8 to sendmail-8.11.6-1.7.0 on i386 gives the
following errors in the maillog:
Sep 11 10:04:46 mail sendmail: f8BA4kD11088: tcpwrappers (ch5as09-73-244-
Sep 11 10:04:46 mail sendmail: NOQUEUE: ch5as09-73-244-208.cw-visp.com
[22.214.171.124] did not issue
MAIL/EXPN/VRFY/ETRN during connection to Daemon0
Sep 11 10:07:04 mail sendmail: f8BA73D11094: tcpwrappers
(ex3lujmoims01.cec.eu.int, 126.96.36.199) reje
Sep 11 10:07:04 mail sendmail: NOQUEUE: ex3lujmoims01.cec.eu.int
[188.8.131.52] did not issue MAIL/EXP
N/VRFY/ETRN during connection to Daemon0
Sep 11 10:12:57 mail sendmail: f8BACpD11160: tcpwrappers
(corp1.cbn.net.id, 184.108.40.206) rejection
Sep 11 10:13:08 mail sendmail: NOQUEUE: corp1.cbn.net.id [220.127.116.11]
did not issue MAIL/EXPN/VRFY/E
TRN during connection to Daemon0
I'm having the same problem. Sendmail worked fine till the RPM. Now what?????
Does Red Hat provide FREE support for what they break?
ChangeLog mentions this vaguely:
* Fri Mar 2 2001 Nalin Dahyabhai <email@example.com>
- tcp-wrapper support wasn't enabled correctly #21642
* Fri May 19 2000 Florian La Roche <Florian.LaRoche@redhat.com>
- enable tcp_wrapper support
This should have been clearly documented in the update notice...
I can't get the /etc/hosts.allow fix to work. I even put in an "ALL : ALL" temporarily as a test, and still the connection was refused
by sendmail. Any other ideas?
Come on Red Hat. Where's the fix? You really botched this one, taking out all of our mail servers like this.
This was sent to me via Red Hat so I copied and pasted the fix. Hope that isn't
Ok, most of us have probably seen this, and if you haven't you can have it
to look forward too. Customers will upgrade sendmail because of the errata
and alot of folks will now have a broken sendmail.
Here is what is going on:
IF they have never changed their /etc/sendmail.cf file and do the upgrade,
that file will be updated to the "stock" sendmail.cf. This stock version
DOES NOT allow any incomming connections. This is just like we have delt
with since Red Hat Linux 7.1 was released. So even if they have Red Hat
6.1 and upgrade, they now have the same issues to deal with that 7.1 had.
So how do you fix it.....
find this line in /etc/mail/sendmail.mc
and put dnl in front of it.
dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')
save the file and issue this command:
m4 /etc/mail/sendmail.mc > /etc/sendmail.cf
service sendmail restart
If incomming mail still does not work, then you need to check one other
place. This new version of sendmail has tcpwrappers compiled in. So even
though someone using tcp wrappers before never had a problem with
sendmail, if they upgrade and havent accounted for it, it will break
sendmail and it will not work.
what do you do......
If there is anything in it, that does not start with "#", especially if it
has a line in it like this:
Sendmail will not work. They will have to add an entry to /etc/hosts.allow
to permit outside connections to sendmail. I haven't tested this but this
This should fix any problems you run across, that are caused from the
One thing I had to do that is different to restart sendmail is:
There is a updated rpm available via ftp/Red Hat Network that should fix
the problem that the default configuration only enabled network access
for localhost instead of for all network devices.
Florian La Roche