Skip to main content

Support & downloads  >  

Bindsock or "Port already in use" errors with port 25 due to the sendmail task
 Technote (FAQ)
 
 
Question
After installing a new Domino server on Solaris, starting SMTP results in bindsock errors, or "port already in use."

Attempting to kill the sendmail process with "kill -9" command on the Solaris 10 server fails to bring down the daemon to free port 25.

How should sendmail be shut down on a Solaris server to allow Domino to take over port 25?

 
Answer
On the Solaris 10 platform, a different command format is used to start and shutdown the services.

# svcadm disable sendmail is Solaris 10 Method to disable sendmail.


 
 
 

Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.
This material provides me with the information I need.




This material is clear and easy to understand.




Did the information help you to achieve your goal?
What updates, improvements, or related information would you like to see in this document?
Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.
Input the verification number to submit feedback:
Document information
 Product categories:
 Software
 Messaging Applications
 Advanced Messaging
 Lotus Domino
 Lotus Domino Server
 Operating system(s):
  Solaris
 Software version:
  7.0, 8.0
 Reference #:
  1290238
 IBM Group:
 Software Group
 Modified date:
 2009-02-09

Translate My Page
 
 

Rate this page

Help us improve this page. Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.