Sponsored Content
Operating Systems Solaris sendmail failed after patch update Post 302222657 by incredible on Thursday 7th of August 2008 09:34:54 AM
Old 08-07-2008
I backed out the sendmail patch and it worked fine.
Anyway, thanks for the steps. might be useful in future.Smilie
 

9 More Discussions You Might Find Interesting

1. Cybersecurity

Sendmail 8.12.7 Vulnerability and Patch

(0 Replies)
Discussion started by: Neo
0 Replies

2. Solaris

patch update instructions

Hi All, I need to update my solaris with a particular patch. When reading the instruction on the sun web site, I got this: Installation Requirements: Reboot immediately after installing this patch on an active boot environment to bring the system to a consistent state. An alternative may... (8 Replies)
Discussion started by: itik
8 Replies

3. Solaris

patch update and break mirror

Hi All, How do you know if you need to break the mirror on solaris 8 patch update? Here's the patch example, 117350-54. On the site, it's just a low type update and not a medium or critical. Is breaking a mirror a best practice only or really a requirement to some patch? Thanks, itik (1 Reply)
Discussion started by: itik
1 Replies

4. High Performance Computing

verify patch update

Hi All, If I need to verify my solaris 8 with patch 110910-03 and I query the server below: #showrev -p | grep 'Patch: 110910-' Patch: 110910-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Do I still need to apply the patch if the older 110910-01 patch exist? Please... (5 Replies)
Discussion started by: itik
5 Replies

5. Linux

kernel patch update how to

Hi All, I need to update my redhatas4 kernel with kernel-2.6.9-67.0.20.EL.src.rpm. When I run this # rpm -ivh kernel-2.6.9-67.0.20.EL.src.rpm warning: user brewbuilder does not exist - using root warning: group brewbuilder does not exist - using root warning: user brewbuilder does... (2 Replies)
Discussion started by: itik
2 Replies

6. High Performance Computing

veritas cluster with kernel patch update

hi all, can someone please share their process on how to kernel patch a red hat ent 4 with veritas cluster 5? it's compose of a primary and backup node. the resources are db, disk, nic. it doesn't need to be detail, just give me the steps like: login to the backup node and update the... (0 Replies)
Discussion started by: itik
0 Replies

7. Solaris

Update Solaris patch

Hi All I had update the solaris version, and now wish to update the patch. but when i check my patch version, i cant find any version for that. any idea? root@leo # showrev Hostname: leo Hostid: 839b58a3 Release: 5.10 Kernel architecture: sun4u Application architecture: sparc... (8 Replies)
Discussion started by: SmartAntz
8 Replies

8. Solaris

Solaris 10 10/09 (Update 8) Patch upgrade

Solaris 10 10/09 (Update 8) Patch upgrade can be done in single user mode? any suggestions.. thanks (2 Replies)
Discussion started by: chandravadrevu
2 Replies

9. AIX

Failed to apply the IZ86736 patch in TL6 SP1

while i was trying to apply the patch IZ86736 in TL6_SP1 its give me the below error instfix -d . -p -f /tmp/.instfix_selections.20512908 > File installp -acgNqXd . -f File File: bos.rte.control 06.01.0006.0003 ... (3 Replies)
Discussion started by: thecobra151
3 Replies
sendmail(4)							   File Formats 						       sendmail(4)

NAME
sendmail, sendmail.cf, submit.cf - sendmail configuration files SYNOPSIS
/etc/mail/sendmail.cf /etc/mail/submit.cf DESCRIPTION
The sendmail.cf and submit.cf files are the configuration files for sendmail(1M). Starting with version 8.12 of sendmail, which was shipped with version 9 of the Solaris operating system, two configuration files are used for submission and transmission of mail, instead of only sendmail.cf, as before. These are: sendmail.cf Remains the principal sendmail configuration file. Used for the Mail Transmission Agent (MTA). submit.cf Used for the Mail Submission Program (MSP). The MSP is used to submit mail messages. Unlike the MTA, it does not run as an SMTP daemon. The MSP does not require root privileges, thus the two-file model provides better security than the pre-sendmail 8.12 model, in which the MSP ran as a daemon and required root privileges. In the default sendmail configuration, sendmail uses submit.cf, as indicated in ps(1) output. In ps output, you will observe two sendmail invocations, such as the ones below: /usr/lib/sendmail -Ac -q15m /usr/lib/sendmail -bd -q15m The first indicates the use of submit.cf, with the client queue (/var/spool/clientmqueue) being checked--and, if needed, flushed--every 15 minutes. The second invocation runs sendmail as a daemon, waiting for incoming SMTP connections. As shipped, sendmail.cf and, in particular, submit.cf, are appropriate for most environments. Where a knowledgeable system administrator needs to make a change, he should use the following procedures. For sendmail.cf: 1. Change directories to the directory that contains the source files for the configuration files. # cd /etc/mail/cf/cf 2. Create a copy of the sendmail file for your system. # cp sendmail.mc `hostname`.mc 3. Edit `hostname`.mc. Make changes suitable for your system and environment. 4. Run make to generate the configuration file. # /usr/bin/make `hostname`.cf 5. Copy the newly generated file to its correct location. # cp `hostname`.cf /etc/mail/sendmail.cf 6. Restart the sendmail service. # svcadm restart sendmail You must restart sendmail for sendmail.cf file changes to take effect, as indicated in step 6. Steps 4 - 6 can be automated. See Automated Rebuilding of Configuration Files below. For submit.cf: 1. Change directories to the directory that contains the source files for the configuration files. # cd /etc/mail/cf/cf 2. Create a copy of the submit file for your system. # cp submit.mc submit-`hostname`.mc 3. Edit submit-`hostname`.mc. Make changes suitable for your system and environment. 4. Run make to generate the configuration file. # /usr/bin/make submit-`hostname`.cf 5. Copy the newly generated file to its correct location. # cp submit-`hostname`.cf /etc/mail/submit.cf You do not need to restart sendmail for changes to submit.cf to take effect. Steps 4 and 5 can be automated. See Automated Rebuilding of Configuration Files below. Enabling Access to Remote Clients The sendmail(1M) man page describes how the config/local_only property can be set to true or false to disallow or allow, respectively, access to remote clients for unmodified systems. Setting values for the following properties for the service instance svc:/network/smtp:sendmail results in automated (re)building of con- figuration files: path_to_sendmail_mc path_to_submit_mc The values for these properties should be strings which represent the path name of the .mc files referred to in steps 2 and 3 of both pro- cedures above. Recommended values are: /etc/mail/cf/cf/`hostname`.mc /etc/mail/cf/cf/submit-`hostname`.mc Each property, if set, results in the corresponding .mc file being used to (re)build the matching .cf file when the service is started. These properties persist across upgrades and patches. To prevent a patch or upgrade from clobbering your .cf file, or renaming it to .cf.old, you can set the desired properties instead. FILES
/etc/mail/cf/README Describes sendmail configuration files. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsndmr | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ SEE ALSO
make(1S), ps(1), sendmail(1M), svcadm(1M), attributes(5) System Administration Guide: Network Services SunOS 5.11 8 May 2008 sendmail(4)
All times are GMT -4. The time now is 11:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy