27 .\" The contents of this file are subject to the terms of the
28 .\" Common Development and Distribution License (the "License").
29 .\" You may not use this file except in compliance with the License.
30 .\"
31 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
32 .\" or http://www.opensolaris.org/os/licensing.
33 .\" See the License for the specific language governing permissions
34 .\" and limitations under the License.
35 .\"
36 .\" When distributing Covered Code, include this CDDL HEADER in each
37 .\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
38 .\" If applicable, add the following below this CDDL HEADER, with the
39 .\" fields enclosed by brackets "[]" replaced with your own identifying
40 .\" information: Portions Copyright [yyyy] [name of copyright owner]
41 .\"
42 .\"
43 .\" Copyright 1989 AT&T
44 .\" Portions Copyright (c) 1992, X/Open Company Limited All Rights Reserved
45 .\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved
46 .\"
47 .TH MAIL 1 "Jul 24, 2008"
48 .SH NAME
49 mail, rmail \- read mail or send mail to users
50 .SH SYNOPSIS
51 .SS "Sending Mail"
52 .LP
53 .nf
54 \fBmail\fR [\fB-tw\fR] [\fB-m\fR \fImessage_type\fR] \fIrecipient\fR...
55 .fi
56
57 .LP
58 .nf
59 \fBrmail\fR [\fB-tw\fR] [\fB-m\fR \fImessage_type\fR] \fIrecipient\fR...
60 .fi
61
62 .SS "Reading Mail"
63 .LP
64 .nf
65 \fBmail\fR [\fB-ehpPqr\fR] [\fB-f\fR \fIfile\fR]
66 .fi
67
68 .SS "Debugging"
69 .LP
70 .nf
71 \fBmail\fR [\fB-x\fR \fIdebug_level\fR] [\fIother_mail_options\fR] \fIrecipient\fR...
72 .fi
73
74 .SH DESCRIPTION
75 .sp
76 .LP
77 A \fIrecipient\fR is usually a domain style address
78 ("\fIuser\fR@\fImachine\fR") or a user name recognized by \fBlogin\fR(1). When
79 \fIrecipient\fRs are named, \fBmail\fR assumes a message is being sent. It
80 reads from the standard input up to an end-of-file (Control-d) or, if reading
81 from a terminal device, until it reads a line consisting of just a period. When
82 either of those indicators is received, \fBmail\fR adds the \fIletter\fR to the
83 \fImailfile\fR for each \fIrecipient\fR.
84 .sp
85 .LP
86 A \fIletter\fR is composed of some \fIheader lines\fR followed by a blank line
87 followed by the \fImessage content\fR. The \fIheader lines\fR section of the
88 letter consists of one or more UNIX postmarks:
89 .sp
90 .in +2
91 .nf
92 \fBFrom\fR \fIsender date_and_time\fR [\fBremote from\fR \fIremote_system_name\fR]
93 .fi
94 .in -2
95 .sp
96
102 .nf
103 \fIkeyword-name\fR\fB:\fR [\fIprintable text\fR]
104 .fi
105 .in -2
106 .sp
107
108 .sp
109 .LP
110 where \fIkeyword-name\fR is comprised of any printable, non-whitespace
111 characters other than colon (`\fB:\fR'). A \fBMIME-version:\fR header line
112 indicates that the message is formatted as described in RFC 2045. A
113 \fBContent-Length:\fR header line, indicating the number of bytes in the
114 \fImessage content\fR, is always present unless the letter consists of only
115 header lines with no message content. A \fBContent-Type:\fR header line that
116 describes the type of the \fImessage content\fR (such as text/plain,
117 application/octet-stream, and so on) is also present, unless the letter
118 consists of only header lines with no message content. Header lines may be
119 continued on the following line if that line starts with white space.
120 .SH OPTIONS
121 .SS "Sending Mail"
122 .sp
123 .LP
124 The following command-line arguments affect sending mail:
125 .sp
126 .ne 2
127 .na
128 \fB\fB-m\fR \fImessage_type\fR\fR
129 .ad
130 .RS 19n
131 A \fBMessage-Type:\fR line is added to the message header with the value of
132 \fImessage_type\fR.
133 .RE
134
135 .sp
136 .ne 2
137 .na
138 \fB\fB-t\fR\fR
139 .ad
140 .RS 19n
141 A \fBTo:\fR line is added to the message header for each of the intended
142 \fIrecipient\fRs.
143 .RE
185 possibly sub-domain) information to the recipient name (such as
186 \fBuser@sf.att.com\fR). (The local system administrator should be consulted for
187 details on which addressing conventions are available on the local system.)
188 .RE
189
190 .sp
191 .ne 2
192 .na
193 \fBUUCP-style addressing\fR
194 .ad
195 .RS 27n
196 Remote recipients are specified by prefixing the recipient name with the remote
197 system name and an exclamation point, such as \fBsysa!user.\fR If \fBcsh\fR(1)
198 is the default shell, \fBsysa\e!user\fR should be used. A series of system
199 names separated by exclamation points can be used to direct a letter through an
200 extended network (such as \fBsysa!sysb!sysc!user\fR or
201 \fBsysa\e!sysb\e!sysc\e!user\fR).
202 .RE
203
204 .SS "Reading Mail"
205 .sp
206 .LP
207 The following command-line arguments affect reading mail:
208 .sp
209 .ne 2
210 .na
211 \fB\fB-e\fR\fR
212 .ad
213 .RS 11n
214 Test for the presence of mail. \fBmail\fR prints nothing.
215 .sp
216 An exit status of \fB0\fR is returned if the user has mail. Otherwise, an exit
217 status of \fB1\fR is returned.
218 .RE
219
220 .sp
221 .ne 2
222 .na
223 \fB\fB-E\fR\fR
224 .ad
225 .RS 11n
226 Similar to \fB-e\fR, but tests only for the presence of \fBnew\fR mail.
528 .RE
529
530 .sp
531 .LP
532 When a user logs in, the presence of mail, if any, is usually indicated. Also,
533 notification is made if new mail arrives while using \fBmail\fR.
534 .sp
535 .LP
536 The permissions of \fImailfile\fR can be manipulated using \fBchmod\fR(1) in
537 two ways to alter the function of \fBmail\fR. The other permissions of the file
538 can be read-write (\fB0666\fR), read-only (\fB0664\fR), or neither read nor
539 write (\fB0660\fR) to allow different levels of privacy. If changed to other
540 than the default (mode \fB0660\fR), the file is preserved even when empty to
541 perpetuate the desired permissions. (The administrator can override this file
542 preservation using the \fBDEL_EMPTY_MAILFILE\fR option of \fBmailcnfg\fR.)
543 .sp
544 .LP
545 The group \fBID\fR of the mailfile must be \fBmail\fR to allow new messages to
546 be delivered, and the mailfile must be writable by group \fBmail\fR.
547 .SS "Debugging"
548 .sp
549 .LP
550 The following command-line arguments cause \fBmail\fR to provide debugging
551 information:
552 .sp
553 .ne 2
554 .na
555 \fB\fB-x\fR \fIdebug_level\fR\fR
556 .ad
557 .RS 18n
558 \fBmail\fR creates a trace file containing debugging information.
559 .RE
560
561 .sp
562 .LP
563 The \fB-x\fR option causes \fBmail\fR to create a file named
564 \fB/tmp/MLDBG\fR\fIprocess_id\fR that contains debugging information relating
565 to how \fBmail\fR processed the current message. The absolute value of
566 \fIdebug_level\fR controls the verboseness of the debug information. \fB0\fR
567 implies no debugging. If \fIdebug_level\fR is greater than \fB0\fR, the debug
568 file is retained \fIonly\fR if \fBmail\fR encountered some problem while
569 processing the message. If \fIdebug_level\fR is less than \fB0\fR, the debug
570 file is always be retained. The \fIdebug_level\fR specified via \fB-x\fR
571 overrides any specification of \fBDEBUG\fR in \fB/etc/mail/mailcnfg\fR. The
572 information provided by the \fB-x\fR option is esoteric and is probably only
573 useful to system administrators.
574 .SS "Delivery Notification"
575 .sp
576 .LP
577 Several forms of notification are available for mail by including one of the
578 following lines in the message header.
579 .sp
580 .LP
581 \fBTransport-Options:\fR [ \fB/\fR\fIoptions\fR ]
582 .sp
583 .LP
584 \fBDefault-Options:\fR [ \fB/\fR\fIoptions\fR ]
585 .sp
586 .LP
587 \fB>To:\fR \fIrecipient\fR [ \fB/\fR\fIoptions\fR ]
588 .sp
589 .LP
590 Where the "/\fIoptions\fR" can be one or more of the following:
591 .sp
592 .ne 2
593 .na
594 \fB\fB/delivery\fR\fR
595 .ad
596 .RS 15n
623 .ad
624 .RS 15n
625 Inform the sender if mail delivery fails. Return the failed message to the
626 sender.
627 .RE
628
629 .sp
630 .ne 2
631 .na
632 \fB\fB/report\fR\fR
633 .ad
634 .RS 15n
635 Same as \fB/return\fR except that the original message is not returned.
636 .RE
637
638 .sp
639 .LP
640 The default is \fB/nodelivery/return\fR. If contradictory options are used, the
641 first is recognized and later, conflicting, terms are ignored.
642 .SH OPERANDS
643 .sp
644 .LP
645 The following operand is supported for sending mail:
646 .sp
647 .ne 2
648 .na
649 \fB\fIrecipient\fR\fR
650 .ad
651 .RS 13n
652 A domain style address ("\fIuser\fR@\fImachine\fR") or user login name
653 recognized by \fBlogin\fR(1).
654 .RE
655
656 .SH USAGE
657 .sp
658 .LP
659 See \fBlargefile\fR(5) for the description of the behavior of \fBmail\fR and
660 \fBrmail\fR when encountering files greater than or equal to 2 Gbyte ( 2^31
661 bytes).
662 .SH ENVIRONMENT VARIABLES
663 .sp
664 .LP
665 See \fBenviron\fR(5) for descriptions of the following environment variables
666 that affect the execution of \fBmail\fR: \fBLC_CTYPE\fR, \fBLC_MESSAGES\fR, and
667 \fBNLSPATH\fR.
668 .sp
669 .ne 2
670 .na
671 \fB\fBTZ\fR\fR
672 .ad
673 .RS 6n
674 Determine the timezone used with date and time strings.
675 .RE
676
677 .SH EXIT STATUS
678 .sp
679 .LP
680 The following exit values are returned:
681 .sp
682 .ne 2
683 .na
684 \fB\fB0\fR\fR
685 .ad
686 .RS 6n
687 Successful completion when the user had mail.
688 .RE
689
690 .sp
691 .ne 2
692 .na
693 \fB\fB1\fR\fR
694 .ad
695 .RS 6n
696 The user had no mail or an initialization error occurred.
697 .RE
698
699 .sp
700 .ne 2
701 .na
702 \fB\fB>1\fR\fR
703 .ad
704 .RS 6n
705 An error occurred after initialization.
706 .RE
707
708 .SH FILES
709 .sp
710 .ne 2
711 .na
712 \fB\fBdead.letter\fR\fR
713 .ad
714 .RS 20n
715 unmailable text
716 .RE
717
718 .sp
719 .ne 2
720 .na
721 \fB\fB/etc/passwd\fR\fR
722 .ad
723 .RS 20n
724 to identify sender and locate \fIrecipient\fRs
725 .RE
726
727 .sp
728 .ne 2
729 .na
765 .na
766 \fB\fB/var/mail/:saved\fR\fR
767 .ad
768 .RS 20n
769 directory for holding temp files to prevent loss of data in the event of a
770 system crash
771 .RE
772
773 .sp
774 .ne 2
775 .na
776 \fB\fB/var/mail/\fIuser\fR\fR\fR
777 .ad
778 .RS 20n
779 incoming mail for \fIuser\fR; that is, the \fImailfile\fR
780 .RE
781
782 .sp
783 .ne 2
784 .na
785 \fB\fBvar/tmp/ma\fR*\fR
786 .ad
787 .RS 20n
788 temporary file
789 .RE
790
791 .SH SEE ALSO
792 .sp
793 .LP
794 \fBchmod\fR(1), \fBcsh\fR(1), \fBlogin\fR(1), \fBmailx\fR(1), \fBuucp\fR(1C),
795 \fBuuencode\fR(1C), \fBvacation\fR(1), \fBwrite\fR(1), \fBattributes\fR(5),
796 \fBenviron\fR(5), \fBlargefile\fR(5)
797 .sp
798 .LP
799 \fISolaris Advanced User\&'s Guide\fR
800 .SH NOTES
801 .sp
802 .LP
803 The interpretation and resulting action taken because of the header lines
804 described in the Delivery Notifications section only occur if this version of
805 \fBmail\fR is installed on the system where the delivery (or failure) happens.
806 Earlier versions of \fBmail\fR might not support any types of delivery
807 notification.
808 .sp
809 .LP
810 Conditions sometimes result in a failure to remove a lock file.
811 .sp
812 .LP
813 After an interrupt, the next message might not be printed. Printing can be
814 forced by typing a \fBp\fR.
|
27 .\" The contents of this file are subject to the terms of the
28 .\" Common Development and Distribution License (the "License").
29 .\" You may not use this file except in compliance with the License.
30 .\"
31 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
32 .\" or http://www.opensolaris.org/os/licensing.
33 .\" See the License for the specific language governing permissions
34 .\" and limitations under the License.
35 .\"
36 .\" When distributing Covered Code, include this CDDL HEADER in each
37 .\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
38 .\" If applicable, add the following below this CDDL HEADER, with the
39 .\" fields enclosed by brackets "[]" replaced with your own identifying
40 .\" information: Portions Copyright [yyyy] [name of copyright owner]
41 .\"
42 .\"
43 .\" Copyright 1989 AT&T
44 .\" Portions Copyright (c) 1992, X/Open Company Limited All Rights Reserved
45 .\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved
46 .\"
47 .TH MAIL 1 "May 17, 2020"
48 .SH NAME
49 mail, rmail \- read mail or send mail to users
50 .SH SYNOPSIS
51 .SS "Sending Mail"
52 .nf
53 \fBmail\fR [\fB-tw\fR] [\fB-m\fR \fImessage_type\fR] \fIrecipient\fR...
54 .fi
55
56 .LP
57 .nf
58 \fBrmail\fR [\fB-tw\fR] [\fB-m\fR \fImessage_type\fR] \fIrecipient\fR...
59 .fi
60
61 .SS "Reading Mail"
62 .nf
63 \fBmail\fR [\fB-ehpPqr\fR] [\fB-f\fR \fIfile\fR]
64 .fi
65
66 .SS "Debugging"
67 .nf
68 \fBmail\fR [\fB-x\fR \fIdebug_level\fR] [\fIother_mail_options\fR] \fIrecipient\fR...
69 .fi
70
71 .SH DESCRIPTION
72 A \fIrecipient\fR is usually a domain style address
73 ("\fIuser\fR@\fImachine\fR") or a user name recognized by \fBlogin\fR(1). When
74 \fIrecipient\fRs are named, \fBmail\fR assumes a message is being sent. It
75 reads from the standard input up to an end-of-file (Control-d) or, if reading
76 from a terminal device, until it reads a line consisting of just a period. When
77 either of those indicators is received, \fBmail\fR adds the \fIletter\fR to the
78 \fImailfile\fR for each \fIrecipient\fR.
79 .sp
80 .LP
81 A \fIletter\fR is composed of some \fIheader lines\fR followed by a blank line
82 followed by the \fImessage content\fR. The \fIheader lines\fR section of the
83 letter consists of one or more UNIX postmarks:
84 .sp
85 .in +2
86 .nf
87 \fBFrom\fR \fIsender date_and_time\fR [\fBremote from\fR \fIremote_system_name\fR]
88 .fi
89 .in -2
90 .sp
91
97 .nf
98 \fIkeyword-name\fR\fB:\fR [\fIprintable text\fR]
99 .fi
100 .in -2
101 .sp
102
103 .sp
104 .LP
105 where \fIkeyword-name\fR is comprised of any printable, non-whitespace
106 characters other than colon (`\fB:\fR'). A \fBMIME-version:\fR header line
107 indicates that the message is formatted as described in RFC 2045. A
108 \fBContent-Length:\fR header line, indicating the number of bytes in the
109 \fImessage content\fR, is always present unless the letter consists of only
110 header lines with no message content. A \fBContent-Type:\fR header line that
111 describes the type of the \fImessage content\fR (such as text/plain,
112 application/octet-stream, and so on) is also present, unless the letter
113 consists of only header lines with no message content. Header lines may be
114 continued on the following line if that line starts with white space.
115 .SH OPTIONS
116 .SS "Sending Mail"
117 The following command-line arguments affect sending mail:
118 .sp
119 .ne 2
120 .na
121 \fB\fB-m\fR \fImessage_type\fR\fR
122 .ad
123 .RS 19n
124 A \fBMessage-Type:\fR line is added to the message header with the value of
125 \fImessage_type\fR.
126 .RE
127
128 .sp
129 .ne 2
130 .na
131 \fB\fB-t\fR\fR
132 .ad
133 .RS 19n
134 A \fBTo:\fR line is added to the message header for each of the intended
135 \fIrecipient\fRs.
136 .RE
178 possibly sub-domain) information to the recipient name (such as
179 \fBuser@sf.att.com\fR). (The local system administrator should be consulted for
180 details on which addressing conventions are available on the local system.)
181 .RE
182
183 .sp
184 .ne 2
185 .na
186 \fBUUCP-style addressing\fR
187 .ad
188 .RS 27n
189 Remote recipients are specified by prefixing the recipient name with the remote
190 system name and an exclamation point, such as \fBsysa!user.\fR If \fBcsh\fR(1)
191 is the default shell, \fBsysa\e!user\fR should be used. A series of system
192 names separated by exclamation points can be used to direct a letter through an
193 extended network (such as \fBsysa!sysb!sysc!user\fR or
194 \fBsysa\e!sysb\e!sysc\e!user\fR).
195 .RE
196
197 .SS "Reading Mail"
198 The following command-line arguments affect reading mail:
199 .sp
200 .ne 2
201 .na
202 \fB\fB-e\fR\fR
203 .ad
204 .RS 11n
205 Test for the presence of mail. \fBmail\fR prints nothing.
206 .sp
207 An exit status of \fB0\fR is returned if the user has mail. Otherwise, an exit
208 status of \fB1\fR is returned.
209 .RE
210
211 .sp
212 .ne 2
213 .na
214 \fB\fB-E\fR\fR
215 .ad
216 .RS 11n
217 Similar to \fB-e\fR, but tests only for the presence of \fBnew\fR mail.
519 .RE
520
521 .sp
522 .LP
523 When a user logs in, the presence of mail, if any, is usually indicated. Also,
524 notification is made if new mail arrives while using \fBmail\fR.
525 .sp
526 .LP
527 The permissions of \fImailfile\fR can be manipulated using \fBchmod\fR(1) in
528 two ways to alter the function of \fBmail\fR. The other permissions of the file
529 can be read-write (\fB0666\fR), read-only (\fB0664\fR), or neither read nor
530 write (\fB0660\fR) to allow different levels of privacy. If changed to other
531 than the default (mode \fB0660\fR), the file is preserved even when empty to
532 perpetuate the desired permissions. (The administrator can override this file
533 preservation using the \fBDEL_EMPTY_MAILFILE\fR option of \fBmailcnfg\fR.)
534 .sp
535 .LP
536 The group \fBID\fR of the mailfile must be \fBmail\fR to allow new messages to
537 be delivered, and the mailfile must be writable by group \fBmail\fR.
538 .SS "Debugging"
539 The following command-line arguments cause \fBmail\fR to provide debugging
540 information:
541 .sp
542 .ne 2
543 .na
544 \fB\fB-x\fR \fIdebug_level\fR\fR
545 .ad
546 .RS 18n
547 \fBmail\fR creates a trace file containing debugging information.
548 .RE
549
550 .sp
551 .LP
552 The \fB-x\fR option causes \fBmail\fR to create a file named
553 \fB/tmp/MLDBG\fR\fIprocess_id\fR that contains debugging information relating
554 to how \fBmail\fR processed the current message. The absolute value of
555 \fIdebug_level\fR controls the verboseness of the debug information. \fB0\fR
556 implies no debugging. If \fIdebug_level\fR is greater than \fB0\fR, the debug
557 file is retained \fIonly\fR if \fBmail\fR encountered some problem while
558 processing the message. If \fIdebug_level\fR is less than \fB0\fR, the debug
559 file is always be retained. The \fIdebug_level\fR specified via \fB-x\fR
560 overrides any specification of \fBDEBUG\fR in \fB/etc/mail/mailcnfg\fR. The
561 information provided by the \fB-x\fR option is esoteric and is probably only
562 useful to system administrators.
563 .SS "Delivery Notification"
564 Several forms of notification are available for mail by including one of the
565 following lines in the message header.
566 .sp
567 .LP
568 \fBTransport-Options:\fR [ \fB/\fR\fIoptions\fR ]
569 .sp
570 .LP
571 \fBDefault-Options:\fR [ \fB/\fR\fIoptions\fR ]
572 .sp
573 .LP
574 \fB>To:\fR \fIrecipient\fR [ \fB/\fR\fIoptions\fR ]
575 .sp
576 .LP
577 Where the "/\fIoptions\fR" can be one or more of the following:
578 .sp
579 .ne 2
580 .na
581 \fB\fB/delivery\fR\fR
582 .ad
583 .RS 15n
610 .ad
611 .RS 15n
612 Inform the sender if mail delivery fails. Return the failed message to the
613 sender.
614 .RE
615
616 .sp
617 .ne 2
618 .na
619 \fB\fB/report\fR\fR
620 .ad
621 .RS 15n
622 Same as \fB/return\fR except that the original message is not returned.
623 .RE
624
625 .sp
626 .LP
627 The default is \fB/nodelivery/return\fR. If contradictory options are used, the
628 first is recognized and later, conflicting, terms are ignored.
629 .SH OPERANDS
630 The following operand is supported for sending mail:
631 .sp
632 .ne 2
633 .na
634 \fB\fIrecipient\fR\fR
635 .ad
636 .RS 13n
637 A domain style address ("\fIuser\fR@\fImachine\fR") or user login name
638 recognized by \fBlogin\fR(1).
639 .RE
640
641 .SH USAGE
642 See \fBlargefile\fR(5) for the description of the behavior of \fBmail\fR and
643 \fBrmail\fR when encountering files greater than or equal to 2 Gbyte ( 2^31
644 bytes).
645 .SH ENVIRONMENT VARIABLES
646 See \fBenviron\fR(5) for descriptions of the following environment variables
647 that affect the execution of \fBmail\fR: \fBLC_CTYPE\fR, \fBLC_MESSAGES\fR, and
648 \fBNLSPATH\fR.
649 .sp
650 .ne 2
651 .na
652 \fB\fBTZ\fR\fR
653 .ad
654 .RS 6n
655 Determine the timezone used with date and time strings.
656 .RE
657
658 .SH EXIT STATUS
659 The following exit values are returned:
660 .sp
661 .ne 2
662 .na
663 \fB\fB0\fR\fR
664 .ad
665 .RS 6n
666 Successful completion when the user had mail.
667 .RE
668
669 .sp
670 .ne 2
671 .na
672 \fB\fB1\fR\fR
673 .ad
674 .RS 6n
675 The user had no mail or an initialization error occurred.
676 .RE
677
678 .sp
679 .ne 2
680 .na
681 \fB\fB>1\fR\fR
682 .ad
683 .RS 6n
684 An error occurred after initialization.
685 .RE
686
687 .SH FILES
688 .ne 2
689 .na
690 \fB\fBdead.letter\fR\fR
691 .ad
692 .RS 20n
693 unmailable text
694 .RE
695
696 .sp
697 .ne 2
698 .na
699 \fB\fB/etc/passwd\fR\fR
700 .ad
701 .RS 20n
702 to identify sender and locate \fIrecipient\fRs
703 .RE
704
705 .sp
706 .ne 2
707 .na
743 .na
744 \fB\fB/var/mail/:saved\fR\fR
745 .ad
746 .RS 20n
747 directory for holding temp files to prevent loss of data in the event of a
748 system crash
749 .RE
750
751 .sp
752 .ne 2
753 .na
754 \fB\fB/var/mail/\fIuser\fR\fR\fR
755 .ad
756 .RS 20n
757 incoming mail for \fIuser\fR; that is, the \fImailfile\fR
758 .RE
759
760 .sp
761 .ne 2
762 .na
763 \fB\fB/var/tmp/ma\fR*\fR
764 .ad
765 .RS 20n
766 temporary file
767 .RE
768
769 .SH SEE ALSO
770 \fBchmod\fR(1), \fBcsh\fR(1), \fBlogin\fR(1), \fBmailx\fR(1), \fBuucp\fR(1C),
771 \fBuuencode\fR(1C), \fBvacation\fR(1), \fBwrite\fR(1), \fBattributes\fR(5),
772 \fBenviron\fR(5), \fBlargefile\fR(5)
773 .sp
774 .LP
775 \fISolaris Advanced User\&'s Guide\fR
776 .SH NOTES
777 The interpretation and resulting action taken because of the header lines
778 described in the Delivery Notifications section only occur if this version of
779 \fBmail\fR is installed on the system where the delivery (or failure) happens.
780 Earlier versions of \fBmail\fR might not support any types of delivery
781 notification.
782 .sp
783 .LP
784 Conditions sometimes result in a failure to remove a lock file.
785 .sp
786 .LP
787 After an interrupt, the next message might not be printed. Printing can be
788 forced by typing a \fBp\fR.
|