Bug 802518 - Sendmail DaemonPort change from 25
Summary: Sendmail DaemonPort change from 25
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sendmail
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-12 17:50 UTC by Gerry Hynes
Modified: 2012-03-13 09:05 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-13 09:05:01 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Gerry Hynes 2012-03-12 17:50:37 UTC
Description of problem:
If you change the DaemonPortOptions=Port=25 to DaemonPortOptions=Port=125 the MTA will not start. You can start the MTA at the command line with "/usr/sbin/sendmail -bd -q1h.


Version-Release number of selected component (if applicable):
Version 6.1

How reproducible:
Everytime.


Steps to Reproduce:
1./etc/init.d/sendmail stop
2.change the DaemonPortOptions=Port=125
3./etc/init.d/sendmail start
  
Actual results:
Looks like it starts, but only the client actually starts.
maillog stats that 
Mar 12 09:42:48 mail sendmail[1828]: starting daemon (8.14.4): SMTP+queueing@01:00:00
Mar 12 09:42:48 mail sendmail[1828]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Permission denied
Mar 12 09:42:48 mail sendmail[1828]: daemon MTA: problem creating SMTP socket
Mar 12 09:42:48 mail sendmail[1828]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: server SMTP socket wedged: exiting



Expected results:


Additional info:

If you after this enter at the command line as root 

/usr/sbin/sendmail -bd -q1h

Sendmail works fine on port 125.

Comment 2 Jaroslav Škarvada 2012-03-13 09:05:01 UTC
It looks like SELinux, you need to mark your new port as SMTP, i.e. by:

# yum install policycoreutils-python
# semanage port -a -t smtp_port_t -p tcp 125

or disable SELinux (not recommended), one-shot for running session:
# setenforce 0

According to the above I am closing this as NOTABUG. If the problem persists, feel free to reopen.


Note You need to log in before you can comment on or make changes to this bug.