sendmail is broken, how do I fix

[Derek Ragona]

At 11:17 AM 1/1/2008, Andrew Falanga wrote:
>Hello,
>
>I'm not sure what I did.  I've been following instructions (really!) and 
>after
>following the instructions from here:
>http://www.puresimplicity.net/~hemi/freebsd/sendmail.html
>
>to setup SSL/TLS authentication for mail relaying, my sendmail installation
>always gives me this very frustrating messages in /var/log/maillog:
>
>Jan  1 11:24:27 whitbap sm-mta[3706]: starting daemon (8.13.8):
>SMTP+queueing at 00:30:00
>Jan  1 11:24:27 whitbap sm-mta[3706]: NOQUEUE: SYSERR(root): 
>opendaemonsocket:
>daemon MTA: cannot bind: Address already in use
>Jan  1 11:24:27 whitbap sm-mta[3706]: daemon MTA: problem creating SMTP socket
>Jan  1 11:24:27 whitbap sm-msp-queue[3710]: starting daemon (8.13.8):
>queueing at 00:30:00
>Jan  1 11:24:27 whitbap sm-mta[3707]: m010sNBM004564:
>to=<jqyuehutmqluz at epilot.com>, delay=17:30:04, xdelay=00:00:00, mailer=esmtp,
>pri=1835114, relay=mail02.interchangeusa.com. [63.251.210.81], dsn=4.0.0,
>stat=Deferred: Connection refused by mail02.interchangeusa.com.
>Jan  1 11:24:32 whitbap sm-mta[3706]: NOQUEUE: SYSERR(root): 
>opendaemonsocket:
>daemon MTA: cannot bind: Address already in use
>Jan  1 11:24:32 whitbap sm-mta[3706]: daemon MTA: problem creating SMTP socket
>Jan  1 11:24:37 whitbap sm-mta[3706]: NOQUEUE: SYSERR(root): 
>opendaemonsocket:
>daemon MTA: cannot bind: Address already in use
>Jan  1 11:24:37 whitbap sm-mta[3706]: daemon MTA: problem creating SMTP socket
>Jan  1 11:24:42 whitbap sm-mta[3706]: NOQUEUE: SYSERR(root): 
>opendaemonsocket:
>daemon MTA: cannot bind: Address already in use
>
>Try as I have, I cannot isolate what is causing this.  When I completely kill
>all sendmail processes (as verified by sockstat  and ps -aux) there is
>*nothing* using port 25.  I do not understand what is going on.
>
>While following the instructions for smtp authentication in:
>http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/smtp-auth.html
>
>I perhaps made one of my blunders.  These instructions say to alter the
>file "freebsd.mc" rather than <hostname>.mc.  It does say that some admin's
>like to use <hostname>.mc, but because I didn't know much about how FreeBSD
>does the install, I saw freebsd.mc and added the three lines listed in bullet
>item 6 on that web page.  Later, I saw that I did have the file <hostname>.mc
>and while researching a resolution to this problem learned that FreeBSD makes
>the <hostname>.mc file when doing a "make all" if memory serves.
>
>Anyway, I then removed those three lines from freebsd.mc and pasted them into
><hostname>.mc.  Regardless, when I had those three lines in freebsd.mc
>everything worked.  I made the changes for SSL/TLS as Josh Tolbert lays out
>in his web site (see above link) and when I restarted sendmail, that's when
>my troubles began.  I don't understand what it is that I did and how it made
>it so that sendmail now thinks something else is using the socket/address.
>
>I'm desperate for a solution.  Thanks for any help.
>
>Andy

While you think there is nothing on that port something is running not 
letting that socket connection.  Try rebooting the system and see if the 
problem is still there.

         -Derek

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.