Print this page
11586 NAME field in man pages should match what's installed
Split |
Close |
Expand all |
Collapse all |
--- old/usr/src/man/man1m/mailwrapper.1m.man.txt
+++ new/usr/src/man/man1m/mailwrapper.1m.man.txt
1 1 MAILWRAPPER(1M) Maintenance Commands MAILWRAPPER(1M)
2 2
3 3 NAME
4 - /usr/lib/mailwrapper - invoke appropriate MTA software based on
5 - configuration file
4 + mailwrapper - invoke appropriate MTA software based on configuration file
6 5
7 6 SYNOPSIS
8 7 Special. See below.
9 8
10 9 DESCRIPTION
11 10 At one time, the only Mail Transfer Agent (MTA) software easily available
12 11 was sendmail(1M). As a result of this, most Mail User Agents (MUAs) such
13 12 as mail(1) had the path and calling conventions expected by sendmail(1M)
14 13 compiled in.
15 14
16 15 Times have changed, however. On a modern UNIX system, the administrator
17 16 may wish to use one of several available MTAs.
18 17
19 18 It would be difficult to modify all MUA software typically available on a
20 19 system, so most of the authors of alternative MTAs have written their
21 20 front end message submission programs so that they use the same calling
22 21 conventions as sendmail(1M) and may be put into place instead of
23 22 sendmail(1M) in /usr/lib/sendmail.
24 23
25 24 sendmail(1M) also typically has aliases named mailq(1) and newaliases(1M)
26 25 linked to it. The program knows to behave differently when its argv[0]
27 26 is "mailq" or "newaliases" and behaves appropriately. Typically,
28 27 replacement MTAs provide similar functionality, either through a program
29 28 that also switches behavior based on calling name, or through a set of
30 29 programs that provide similar functionality.
31 30
↓ open down ↓ |
16 lines elided |
↑ open up ↑ |
32 31 Although having drop-in replacements for sendmail(1M) helps in installing
33 32 alternative MTAs, it essentially makes the configuration of the system
34 33 depend on hand installing new programs in /usr. This leads to
35 34 configuration problems for many administrators, since they may wish to
36 35 install a new MTA without altering the system provided /usr. (This may
37 36 be, for example, to avoid having upgrade problems when a new version of
38 37 the system is installed over the old.) They may also have a shared /usr
39 38 among several machines, and may wish to avoid placing implicit
40 39 configuration information in a read-only /usr.
41 40
42 - The /usr/lib/mailwrapper utility is designed to replace /usr/lib/sendmail
43 - and to invoke an appropriate MTA instead of sendmail(1M) based on
44 - configuration information placed in /etc/mailer.conf. This permits the
45 - administrator to configure which MTA is to be invoked on the system at
46 - run time.
41 + The mailwrapper utility is designed to replace /usr/lib/sendmail and to
42 + invoke an appropriate MTA instead of sendmail(1M) based on configuration
43 + information placed in /etc/mailer.conf. This permits the administrator
44 + to configure which MTA is to be invoked on the system at run time.
47 45
48 46 Other configuration files may need to be altered when replacing
49 47 sendmail(1M).
50 48
51 49 EXIT STATUS
52 - The /usr/lib/mailwrapper utility exits 0 on success, and >0 if an error
53 - occurs.
50 + The mailwrapper utility exits 0 on success, and >0 if an error occurs.
54 51
55 52 DIAGNOSTICS
56 - The /usr/lib/mailwrapper will print a diagnostic if its configuration
57 - file is missing or malformed, or does not contain a mapping for the name
58 - under which it was invoked.
53 + The mailwrapper will print a diagnostic if its configuration file is
54 + missing or malformed, or does not contain a mapping for the name under
55 + which it was invoked.
59 56
60 57 SEE ALSO
61 58 mail(1), mailq(1), newaliases(1M), sendmail(1M), mailer.conf(4)
62 59
63 -illumos August 7, 2006 illumos
60 +illumos August 20, 2019 illumos
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX