![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to mailcnfg.4 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Research Unix] / researchv10no / lbin / mailx / man|
Return to mailcnfg.4 CVS log | Up to [Research Unix] / researchv10no / lbin / mailx / man |
1.1 root 1: '\"macro stdmacro
2: .if n .pH g4.mailcnfg %W% of %G%
3: .nr X
4: .if \nX=0 .ds x} mailcnfg 4 "Essential Utilities" "\&"
5: .if \nX=1 .ds x} mailcnfg 4 "Essential Utilities"
6: .if \nX=2 .ds x} mailcnfg 4 "" "\&"
7: .if \nX=3 .ds x} mailcnfg "" "" "\&"
8: .TH \*(x}
9: .SH NAME
10: \f4mailcnfg\f1 \- initialization information for \f4mail\fP and \f4rmail\fP
11: .SH DESCRIPTION
12: The \f4/etc/mail/mailcnfg\fP file contains initialization information for
13: the \f4mail\fP and \f4rmail\fP commands.
14: Each entry in \f4mailcnfg\f1 consists of a line of the form
15: .P
16: .RS 20
17: \f2Keyword\f4 = \f2Value\f1
18: .RE
19: .P
20: Leading whitespace, whitespace surrounding the equal sign, and trailing
21: whitespace is ignored.
22: \f2Keyword\fP may not contain embedded whitespace,
23: but whitespace may appear within \f2Value\fP.
24: Undefined keywords or badly formed entries are silently ignored.
25: .SS Keyword Definitions
26: .TP 20
27: \f4DEBUG\fP
28: Takes the same values as the \f4\-x\fP invocation option of \f4mail\fP.
29: This provides a way of setting a system-wide debug/tracing level.
30: Typically \f4DEBUG\fP is set to a value of 2, which provides minimal diagnostics
31: useful for debugging \f4mail\fP and \f4rmail\fP failures. The value of the
32: \f4\-x\fP \f4mail\fP invocation option will override any specification of
33: \f4DEBUG\fP in \f4mailcnfg\fP.
34: .TP 20
35: \f4CLUSTER\fP
36: To identify a closely coupled set of systems by one name to
37: all other systems, set \f2Value\fP to the cluster name.
38: This string is used to supply the \f5...remote from...\fP information
39: on the \f5From\fP header line rather than the system nodename returned by
40: \f4uname\fP(2).
41: .TP 20
42: \f4FAILSAFE\fP
43: In the event that the \f4/var/mail\fP directory is accessed via RFS or NFS within
44: a cluster (see \f4CLUSTER\fP above),
45: provisions must be made to allow for the directory not being available
46: when local mail is to be delivered (remote system crash, RFS or NFS problems,
47: etc.). \f2Value\fP is a string that indicates where to forward the
48: current message for delivery. Typically this is the remote system
49: that actually \f2owns\fP \f4/var/mail\fP. In this way, the message is
50: queued for delivery to that system when it becomes available.
51: For example, assume a cluster of systems (\f4sysa\fP, \f4sysb\fP, \f4sysc\fP) where
52: \f4/var/mail\fP is physically mounted on \f4sysc\fP and made available to the
53: other machines via RFS or NFS.
54: If \f4sysc\fP were to crash,
55: the RFS/NFS-accessible \f4/var/mail\fP would become unavailable
56: and local deliveries of mail would go to \f4/var/mail\fP on the local
57: system. When \f4/var/mail\fP is re-mounted via RFS/NFS, all messages
58: deposited in the local directory would be hidden and essentially lost.
59: To prevent this, if \f4FAILSAFE\fP is defined in \f4mailcnfg\fP,
60: \f4mail\fP and \f4rmail\fP check for the existence of
61: \f4/var/mail/:saved\fP, a required subdirectory.
62: If this subdirectory does not exist, \f4mail\fP assumes that
63: the RFS/NFS-accessible \f4/var/mail\fP is not available and invokes the
64: failsafe mechanism of automatically forwarding the message to \f2Value\fP.
65: In this example \f2Value\fP would be \f4sysc!%n\fP.
66: The \f4%\f2n\f1 keyword is expanded to be the recipient name
67: [see \f4mail\fP(1) for details]
68: and thus the message would be forwarded to \f4sysc\fP!\f2recipient_name\fP.
69: Because \f4sysc\fP is not available, the message remains on the local system
70: until \f4sysc\fP is available, and then sent there for delivery.
71: .TP 20
72: \f4DEL_EMPTY_MFILE\fP
73: If not specified, the default action of \f4mail\fP and \f4rmail\fP is to
74: delete empty mailfiles if the permissions are 0660 and to retain empty
75: mailfiles if the permissions are anything else.
76: If \f2Value\fP is \f4yes\fP, empty mailfiles are always deleted,
77: regardless of file permissions.
78: If \f2Value\fP is \f4no\fP, empty mailfiles are never deleted.
79: .TP 20
80: \f4DOMAIN\fP
81: This string is used to supply the system domain name in place of the
82: domain name returned by \f4getdomainame\fP(3).
83: .TP 20
84: \f4SMARTERHOST\fP
85: This string may be set to a smarter host which may be referenced within the
86: mail surrogate file via \f4%\&X\f1.
87: .TP 20
88: \f4%\f2mailsurr_keyword\f1
89: As described in \f4mailsurr\fP(4), certain pre-defined single letter keywords
90: are textually substituted in surrogate command fields before they are
91: executed.
92: While none of the predefined keywords may be changed in meaning,
93: new ones may be defined to provide a shorthand notation for long strings
94: (such as \f4/usr/lib/mail/surrcmd\fP) which may appear repeatedly within
95: the \f4mailsurr\fP file.
96: Upper case letters are reserved for future use and will be ignored if
97: encountered here.
98: .SH FILES
99: .ft 4
100: .nf
101: /etc/mail/mailcnfg
102: /etc/mail/mailsurr
103: /var/mail/:saved
104: /usr/lib/mail/surrcmd
105: .fi
106: .ft 1
107: .SH SEE ALSO
108: \f4mailsurr\fP(4)
109: .br
110: \f4mail\fP(1) in the \f2User's Reference Manual\f1
111: .br
112: \f4uname\fP(2),
113: \f4getdomainame\fP(3) in the \f2Programmer's Reference Manual\f1
114: .SH NOTES
115: If \f4/var/mail\fP is accessed via RFS or NFS and the subdirectory
116: \f4/var/mail/:saved\fP is not removed from the local system,
117: the \f4FAILSAFE\fP mechanism will be subverted.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.