Sendmail (daemon MTA: cannot bind: Address already in use)

[frank_14]

I am sorry I seldom came here in two days.
and thanks for any responses,good or bad.
I am tring now as your suggestions,I will report the result as fast as I can.
and I just check the sendmail.cf,there are
some options:

# SMTP daemon options
O DaemonPortOptions=Name=MTA
O DaemonPortOptions=Port=587, Name=MSA, M=E

# SMTP client options
O ClientPortOptions=Family=inet, Address=0.0.0.0

(I used the newest version)

[frank_14]

I found the files in my server,
/var/adm/sw/save/PHNE_17190/INETSVCS-RUN/sbin/init.d/sendmail
/var/adm/sw/save/PHNE_17190/INETSVCS-RUN/usr/sbin/sendmail

so I noticed smtp was started by inetd.
/sbin/init.d/inetd stop
then sendmail can start up.

I studied a lot from your responses.
thanks again.

[Steven E. Protter]

Notice to sendmailers.

If you are using sendmail.mc for macros and you change your network setup:

And you have the daemon setup to accept mail as follows:

DAEMON_OPTIONS(`Port=smtp,Addr=66.92.171.212, Name=MTA')

Note that if for some reason you change your network setup and the IP address stated above no longer exists on the local server.

The sendmail daemon will start run for a little while and generate the error message that started this call. This applies to HP-UX and Linux sendmail 8.11 and 8.12

The situation will not be intuitive and will be hard to diagnose.

The original owner of this call should have assigned points. If this call comes up in a search the documentation will be more complete.

SEP

[Jeff Schussele]

Hi frank,

Check the /etc/mail/sendmail.cf file for just *where* it's defining it's queue directory.
Default is /var/spool/mqueue - but will be wherever the file defines it.

Look for
O QueueDirectory=

IF that doesn't exist, that would explain the lead error msg.

My 2 cents,
Jeff

[Piotr Kierklo]

I had this error messa, when (for some weird reasons) options in my sendmail.cf file were duplicated (so all of them appeared twice).

Cleaning duplicates and restarting sendmail, helped, no error anymore.