Sponsored Content
Operating Systems Solaris sendmail failed after patch update Post 302222447 by Smiling Dragon on Wednesday 6th of August 2008 11:10:13 PM
Old 08-07-2008
This all assumes you havn't manually hacked your sendmail.cf, if you have, the following steps will eat any changes youve made (but then, it looks like your patch did that too, so...)
  1. cd /etc/mail
  2. cp -p sendmail.cf sendmail.cf.borked
  3. cd /usr/lib/mail/cf
  4. make
  5. cp subsidiary.cf /etc/mail/sendmail.cf
  6. /etc/init.d/sendmail stop
  7. /etc/init.d/sendmail start
  8. tail /var/adm/messages
Smilie

*I haven't worked with sol7 for a while, it could be /etc/sendmail.cf instead of /etc/mail/sendmail.cf
 

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
mailsetup(8)						      System Manager's Manual						      mailsetup(8)

NAME
mailsetup - Configures the host's mail system SYNOPSIS
/usr/sbin/mailsetup [-f file] OPTIONS
Specifies the name of the resulting configuration file. DESCRIPTION
The mailsetup script sets up the sendmail system on your host. You can use this script to do a quick setup where defaults are used or to do a more extensive setup. Alternatively, you can use the mailconfig command. Before you run the mailsetup script, your machine should be established on a local area network (LAN). If you want to use domain-based addressing, you must also configure the Berkeley Internet Name Domain (BIND) service in your environment. Furthermore, if you want to dis- tribute your /var/adm/sendmail/aliases database (see aliases(4)) amongst the machines in your environment, you must configure the Network Information Service (NIS). See the Network Administration guide, bind_intro(7), and nis_intro(7) for more information about the BIND and NIS services. For a quick setup, the only information you are asked for is the name of the mail relay you are using and which users are considered local. For the more extensive setup, you are asked for the same information in addition to UUCP, DECnet, and UMC configuration information, mail aliases for your machine, local address formats, and other domain information. You must run the mailsetup script as superuser and with the system in multiuser mode. When you run mailsetup a menu is displayed giving you a choice of responses. You are then prompted for further information. If you do not use the -f option, before mailsetup exits, it asks if you wish to restart your mail with this new configuration. If you answer no, your configuration file is saved in /var/adm/sendmail/sendmail.cf.tmp and the install is aborted. If you answer yes, your /var/adm/sendmail/sendmail.cf file is moved to /var/adm/sendmail/sendmail.cf.orig, if no file by this name exists. If /var/adm/send- mail/sendmail.cf.orig exists, /var/adm/sendmail/sendmail.cf is moved to /var/adm/sendmail/sendmail.cf.n, where n is the version number (0 to 6 where 0 is the most recent). The new configuration file is then moved to /var/adm/sendmail/sendmail.cf and sendmail is restarted. If you use the -f option, the configuration file is saved with the file name specified and sendmail is not restarted. The mailsetup script produces the following three files in /var/adm/sendmail: sendmail.m4 hostname.m4 Makefile.cf.hostname You can fine tune your configuration by modifying the hostname.m4 file and issuing a make -f Makefile.cf.hostname command, which produces a hostname.cf file. You can then copy the hostname.cf file to sendmail.cf and restart sendmail using the /sbin/init.d/sendmail restart com- mand. Running mailsetup To set up your mail system using the mailsetup script, log in as root and complete the following steps: Invoke the mailsetup script. The script asks whether you want to do a quick setup. If you answer yes, the mailsetup script prompts you for the following information: The name of the general-purpose relay If you want to modify the list of aliases and users that are considered local If you want to complete the mail setup To do an advanced mail setup, answer no. The mailsetup script prompts you for the information you collected on the worksheet. When you finish providing the information, the mailsetup script asks if you want to complete the configuration. If you answer yes, the script moves the new sendmail.cf file to the system space, saves the old sendmail.cf file, and restarts sendmail. If you answer no, the script moves the new sendmail.cf file to /var/adm/sendmail/sendmail.cf.tmp and exits. Running mailsetup in a TruCluster Server Cluster The following restrictions apply to setting up mail with the mailsetup script in a TruCluster Server cluster: You can run the mailsetup script on an entire cluster, but not focused on any one cluster member. If you try to run mailsetup with the -focus option, you will see the following error message: Mail can only be configured for the entire cluster. The cluster members and the cluster alias are added to the Cw macro, which defines the nicknames for the cluster. If you delete the cluster members or the cluster alias from the nicknames list via the mailsetup script, they are added again. If you do a quick setup with the mailsetup script, the cluster members and the cluster alias are automically added to the Cw macro (nicknames list) and you are not prompted to update the list of nicknames. Any file that includes the hostname string as part of the file name is changed to includecluster_alias. For example, hostname.m4 becomes cluster_alias.m4 and Makefile.cf.hostname becomes Makefile.cf.cluster_alias. FILES
Contains alias definitions for the sendmail program. Specifies the users who should receive mail on the local host. Specifies the send- mail configuration file. Specifies the mail setup product description for the configuration file. Specifies the backup configuration files. Specifies the original configuration file. Specifies the configuration file produced by mailsetup. Specifies the user config- urable file produced by mailsetup. In a TruCluster Server cluster, this file is named after the cluster alias, i.e., cluster_alias.m4. Specifies the Makefile file produced by mailsetup and used to make a hostname.cf file from the sendmail.cf and hostname.m4 files. In a Tru- Cluster Server cluster, this file is named after the cluster alias, i.e., Makefile.cf.cluster_alias. SEE ALSO
Commands: m4(1), , mailconfig(8), sendmail(8) Introductions: mail_intro(7), bind_intro(7), nis_intro(7) Network Administration mailsetup(8)
All times are GMT -4. The time now is 04:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy