sendmail[25143]:SYSERR(root): savemail: cannot save rejected email anywhere

Incorrect entry in sendmail .forward file causes Savemail Panic

Symptoms
 Where syslog.conf contains the lines:

*.err;kern.debug;daemon.notice;mail.crit /var/adm/messages
mail.debug   ifdef(`LOGHOST', /var/log/syslog, @loghost)

 The following messages are appearing /var/adm/messages:

Sep 29 20:48:03 solarishost030 sendmail[25143]: [ID 801593 mail.alert] q8U0ONCL009518: Losing ./qfq8U0ONCL009518: savemail panic
Sep 29 20:48:03 solarishost030 sendmail[25143]: [ID 801593 mail.crit] q8U0ONCL009518: SYSERR(root): savemail: cannot save rejected email anywhere
 Also /var/log/syslog:

Sep 29 20:48:03 solarishost030 sendmail[25143]: [ID 801593 mail.info] q8U0ONCL009518: to=sp.unixadmin.some-ip.com, ctladdr=root (0/0), delay=00:23:40, mailer=local, pri=121866, dsn=5.1.1, stat=User unknown
Sep 29 20:48:03 solarishost030 last message repeated 1 time
Sep 29 20:48:03 solarishost030 sendmail[25143]: [ID 801593 mail.info] q8U0ONCL009518: q8U0SmP6025143: return to sender: User unknown
Sep 29 20:48:03 solarishost030 sendmail[25143]: [ID 801593 mail.info] q8U0SmP6025143: to=sp.unixadmin.some-ip.com, ctladdr=root (0/0), delay=00:00:00, mailer=local, pri=3536, dsn=5.1.1, stat=User unknown
Sep 29 20:48:03 solarishost030 sendmail[25143]: [ID 801593 mail.alert] q8U0ONCL009518: Losing ./qfq8U0ONCL009518: savemail panic
Sep 29 20:48:03 solarishost030 sendmail[25143]: [ID 801593 mail.crit] q8U0ONCL009518: SYSERR(root): savemail: cannot save rejected email anywhere

Changes
 A .forward file was created for the root user.

Cause
There was a typo in the .forward file for the root user.

Solution
1. Correct the entry in the file:

% cat /.forward
# sp.unixadmin.some-ip.com  #<== incorrect entry

sp.unixadmin@some-ip.com #<== entry had a "dot" and needed a "@" to create the proper "user@domain" entry sendmail requires
2. Check that the entry resolves using sendmail:

% /usr/lib/sendmail -bv root
sp.unixadmin@some-ip.com... deliverable: mailer relay, host smtp.global.some-ip.com, user sp.unixadmin@some-ip.com
3. Run the "newaliases" command to update the alias.db:

% newaliases

/etc/mail/aliases: 15 aliases, longest 53 bytes, 264 bytes total

Comments

Post a Comment

Popular posts from this blog

Understanding How ZFS Calculates Used Space

This document explains how ZFS calculates the amount of used space within a zpool and provides examples of how various ZFS features affect that calculation. DETAILS A ZFS storage pool is a logical collection of devices that provide space for datasets such as filesystems, snapshots and volumes. A zfs pool can be used as a filesystem, i.e. such as mounting/unmounting; to take snapshots that provides read-only (clones are writable copies of snapshots) copies of the filesystem taken in the past; to create volumes that can be accessed as a raw and a block device and for setting properties on datasets. Interaction of all these datasets and associated properties such as quotas, reservations, compression and deduplication (Solaris 11 only) play a role in how ZFS calculates space usage. Neither the du nor df command have been updated to account for ZFS file system space usage. When calculating zfs space usage, always use the following command. # zfs list -r -o space <pool_name...
Read more

Restart autosys agent

#/etc/init.d/uajm_agent stop CA-UAJM Agent stopped. #/etc/init.d/uajm_agent start CA-UAJM Agent started. Follow the below workaround if the autosys agent does not start. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1.Run the command to check the status of both process, auto_remote and csampmuxf # ps -ef|grep 'auto'     root 14712     1  0   Aug 27 ?        2:42 auto_remote     root 27652     1  0 13:00:22 ?        0:00 auto_remote     root 27782     1  0 13:00:40 ?        0:00 auto_remote     root 29066 24480  0 13:01:07 pts/7    0:00 grep auto 2.There should be two entries for /opt/CA/SharedComponents/Csam/SockAdapter/bin/csampmux status . If you see one entry then stop agent and check the autore...
Read more

How To Verify Remote System Controller (RSC) is Configured and Current on Sun Fire[TM] 280R/V480/V490/V880/V890 servers

Steps to Follow: How To Verify Remote System Controller(RSC) is Configured and Current 1.Check to see if the RSC software is already installed. # /usr/bin/pkginfo | grep SUNWrsc 2.If the software is installed the command should output the package name and info.   The version of the package installed in Solaris should match the version of firmware installed on the card.   `rscadm version` in Solaris will display the firmware version. 3.If the software is not installed the packages can be found on the supplemental CD that came with the Solaris Operating Environment. If you do not have the CD the software can be downloaded from MOS: RSC 2.2.2 is supported with Solaris 10, but you need to get this from a supplemental CD (for Solaris 9, since there is no supplemental CD for S10). The packages for Solaris 8 and 9 (and later) are both in the zip file. There are two options of the zip file, 32bit, and 64bit, but they both have the same checksums, so there are...
Read more