08-13-2008
patching sendmail is very dangerous. Before patching ALWAYS!!! backup
/etc/mail <--- everything in here
/usr/lib/sendmail <--- backup the binary
The patch special instruction does not say anything but once you install sendmail patch it will generate new sendmail binary and overwrite everything else, aliases files, cf files everything - make sure you do backup.
some crazy sites use multiple sendmail versions especially telco can have very messy systems, I did one customer some years back, there's at least 5 different sendmail binaries location on the server after issuing the "find" command, messy guy.
To tell what is your current sendmail and which cf file it is using run command
/usr/lib/sendmail -d0.11 -bp
9 More Discussions You Might Find Interesting
1. Cybersecurity
(0 Replies)
Discussion started by: Neo
0 Replies
2. Solaris
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
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
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
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
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
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 can be done in single user mode? any suggestions.. thanks (2 Replies)
Discussion started by: chandravadrevu
2 Replies
9. AIX
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
LEARN ABOUT NETBSD
mailer.conf
MAILER.CONF(5) BSD File Formats Manual MAILER.CONF(5)
NAME
mailer.conf -- configuration file for mailwrapper(8)
DESCRIPTION
The file /etc/mailer.conf contains a series of lines of the form
name program [arguments ...]
The first word of each line is the name of a program invoking mailwrapper(8). (For example, on a typical system /usr/sbin/sendmail would be
a symbolic link to mailwrapper(8), as would newaliases(1) and mailq(1). Thus, name might be ``sendmail'' or ``newaliases'' etc.)
The second word of each line is the name of the program to actually execute when the first name is invoked.
The further arguments, if any, are passed to the program, followed by the arguments mailwrapper(8) was called with.
The file may also contain comment lines, denoted by a '#' mark in the first column of any line.
The default mailer is postfix(1), which will also start by default (unless specifically disabled via an rc.conf(5) setting) so that locally
generated mail can be delivered, if the ``sendmail'' setting in /etc/mailer.conf is set to ``/usr/libexec/postfix/sendmail''.
FILES
/etc/mailer.conf
EXAMPLES
This example shows how to set up mailer.conf to invoke the postfix(1) program:
sendmail /usr/libexec/postfix/sendmail
mailq /usr/libexec/postfix/sendmail
newaliases /usr/libexec/postfix/sendmail
This example shows the use of the mini-sendmail package from pkgsrc in place of postfix(1):
# Send outgoing mail to a smart relay using mini-sendmail
sendmail /usr/pkg/sbin/mini-sendmail -srelayhost
send-mail /usr/pkg/sbin/mini-sendmail -srelayhost
Note the use of additional arguments.
SEE ALSO
mail(1), mailq(1), newaliases(1), postfix(1), mailwrapper(8)
pkgsrc/mail/sendmail, pkgsrc/mail/mini_sendmail
HISTORY
mailer.conf appeared in NetBSD 1.4.
AUTHORS
Perry E. Metzger <perry@piermont.com>
BUGS
The entire reason this program exists is a crock. Instead, a command for how to submit mail should be standardized, and all the ``behave
differently if invoked with a different name'' behavior of things like mailq(1) should go away.
BSD
April 10, 2010 BSD