1 .\"
2 .\" Sun Microsystems, Inc. gratefully acknowledges The Open Group for
3 .\" permission to reproduce portions of its copyrighted documentation.
4 .\" Original documentation from The Open Group can be obtained online at
5 .\" http://www.opengroup.org/bookstore/.
6 .\"
7 .\" The Institute of Electrical and Electronics Engineers and The Open
8 .\" Group, have given us permission to reprint portions of their
9 .\" documentation.
10 .\"
11 .\" In the following statement, the phrase ``this text'' refers to portions
12 .\" of the system documentation.
13 .\"
14 .\" Portions of this text are reprinted and reproduced in electronic form
15 .\" in the SunOS Reference Manual, from IEEE Std 1003.1, 2004 Edition,
16 .\" Standard for Information Technology -- Portable Operating System
17 .\" Interface (POSIX), The Open Group Base Specifications Issue 6,
18 .\" Copyright (C) 2001-2004 by the Institute of Electrical and Electronics
19 .\" Engineers, Inc and The Open Group. In the event of any discrepancy
20 .\" between these versions and the original IEEE and The Open Group
21 .\" Standard, the original IEEE and The Open Group Standard is the referee
22 .\" document. The original Standard can be obtained online at
23 .\" http://www.opengroup.org/unix/online.html.
24 .\"
25 .\" This notice shall appear on any product containing this material.
26 .\"
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
97 .sp
98 .LP
99 followed by one or more standardized message header lines of the form:
100 .sp
101 .in +2
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
144
145 .sp
146 .ne 2
147 .na
148 \fB\fB-w\fR\fR
149 .ad
150 .RS 19n
151 A letter is sent to a remote recipient without waiting for the completion of
152 the remote transfer program.
153 .RE
154
155 .sp
156 .LP
157 If a letter is found to be undeliverable, it is returned to the sender with
158 diagnostics that indicate the location and nature of the failure. If \fBmail\fR
159 is interrupted during input, the message is saved in the file \fBdead.letter\fR
160 to allow editing and resending. \fBdead.letter\fR is always appended to, thus
161 preserving any previous contents. The initial attempt to append to (or create)
162 \fBdead.letter\fR is in the current directory. If this fails, \fBdead.letter\fR
163 is appended to (or created in) the user's login directory. If the second
164 attempt also fails, no \fBdead.letter\fR processing is done.
165 .sp
166 .LP
167 \fBrmail\fR only permits the sending of mail; \fBuucp\fR(1C) uses \fBrmail\fR
168 as a security precaution. Any application programs that generate mail messages
169 should be sure to invoke \fBrmail\fR rather than \fBmail\fR for message
170 transport and/or delivery.
171 .sp
172 .LP
173 If the local system has the Basic Networking Utilities installed, mail can be
174 sent to a recipient on a remote system. There are numerous ways to address mail
175 to recipients on remote systems depending on the transport mechanisms available
176 to the local system. The two most prevalent addressing schemes are Domain-style
177 and UUCP-style.
178 .sp
179 .ne 2
180 .na
181 \fBDomain-style addressing\fR
182 .ad
183 .RS 27n
184 Remote recipients are specified by appending an `\fB@\fR' and domain (and
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.
227 .sp
228 An exit status of \fB0\fR is returned if the user has new mail
229 to read, an exit status of \fB1\fR is returned if the user has no
230 mail, or an exit status of \fB2\fR is returned if the user has mail
231 which has already been read.
232 .RE
233
234 .sp
235 .ne 2
236 .na
237 \fB\fB-h\fR\fR
238 .ad
239 .RS 11n
240 A window of headers are initially displayed rather than the latest message. The
241 display is followed by the \fB?\fR prompt.
242 .RE
243
244 .sp
245 .ne 2
246 .na
247 \fB\fB-p\fR\fR
248 .ad
249 .RS 11n
250 All messages are printed without prompting for disposition.
251 .RE
252
253 .sp
254 .ne 2
255 .na
256 \fB\fB-P\fR\fR
257 .ad
258 .RS 11n
259 All messages are printed with \fIall\fR header lines displayed, rather than the
260 default selective header line display.
261 .RE
262
263 .sp
264 .ne 2
265 .na
266 \fB\fB-q\fR\fR
267 .ad
268 .RS 11n
269 \fBmail\fR terminates after interrupts. Normally an interrupt causes only the
270 termination of the message being printed.
271 .RE
272
273 .sp
274 .ne 2
275 .na
276 \fB\fB-r\fR\fR
277 .ad
278 .RS 11n
279 Messages are printed in first-in, first-out order.
280 .RE
281
282 .sp
283 .ne 2
284 .na
285 \fB\fB-f\fR \fIfile\fR\fR
286 .ad
287 .RS 11n
288 \fBmail\fR uses \fIfile\fR (such as \fBmbox\fR) instead of the default
289 \fImailfile\fR.
290 .RE
291
292 .sp
293 .LP
294 \fBmail\fR, unless otherwise influenced by command-line arguments, prints a
295 user's mail messages in last-in, first-out order. The default mode for printing
296 messages is to display only those header lines of immediate interest. These
297 include, but are not limited to, the UNIX \fBFrom\fR and \fB>From\fR postmarks,
298 \fBFrom:\fR, \fBDate:\fR, \fBSubject:\fR, and \fBContent-Length:\fR header
299 lines, and any recipient header lines such as \fBTo:\fR, \fBCc:\fR, \fBBcc:\fR,
300 and so forth. After the header lines have been displayed, \fBmail\fR displays
301 the contents (body) of the message only if it contains no unprintable
302 characters. Otherwise, \fBmail\fR issues a warning statement about the message
303 having binary content and \fBnot\fR display the content. This can be overridden
304 by means of the \fBp\fR command.
305 .sp
306 .LP
307 For each message, the user is prompted with a \fB?\fR and a line is read from
308 the standard input. The following commands are available to determine the
309 disposition of the message:
310 .sp
311 .ne 2
312 .na
313 \fB\fB#\fR\fR
314 .ad
315 .RS 22n
316 Print the number of the current message.
317 .RE
318
319 .sp
320 .ne 2
321 .na
322 \fB\fB\(mi\fR\fR
323 .ad
324 .RS 22n
325 Print previous message.
326 .RE
327
328 .sp
329 .ne 2
330 .na
331 \fB<new-line>,\fB+\fR, or \fBn\fR\fR
332 .ad
333 .RS 22n
334 Print the next message.
335 .RE
336
337 .sp
338 .ne 2
339 .na
340 \fB\fB!\fR\fIcommand\fR\fR
341 .ad
342 .RS 22n
343 Escape to the shell to do \fIcommand\fR.
344 .RE
345
346 .sp
347 .ne 2
348 .na
349 \fB\fBa\fR\fR
350 .ad
351 .RS 22n
352 Print message that arrived during the \fBmail\fR session.
353 .RE
354
355 .sp
356 .ne 2
357 .na
358 \fB\fBd\fR, or \fBdp\fR\fR
359 .ad
360 .RS 22n
361 Delete the current message and print the next message.
362 .RE
363
364 .sp
365 .ne 2
366 .na
367 \fB\fBd\fR \fIn\fR\fR
368 .ad
369 .RS 22n
370 Delete message number \fIn\fR. Do not go on to next message.
371 .RE
372
373 .sp
374 .ne 2
375 .na
376 \fB\fBdq\fR\fR
377 .ad
378 .RS 22n
379 Delete message and quit \fBmail\fR.
380 .RE
381
382 .sp
383 .ne 2
384 .na
385 \fB\fBh\fR\fR
386 .ad
387 .RS 22n
388 Display a window of headers around current message.
389 .RE
390
391 .sp
392 .ne 2
393 .na
394 \fB\fBh\fR\fIn\fR\fR
395 .ad
396 .RS 22n
397 Display a window of headers around message number \fIn\fR.
398 .RE
399
400 .sp
401 .ne 2
402 .na
403 \fB\fBh a\fR\fR
404 .ad
405 .RS 22n
406 Display headers of all messages in the user's \fImailfile\fR.
407 .RE
408
409 .sp
410 .ne 2
411 .na
412 \fB\fBh d\fR\fR
413 .ad
414 .RS 22n
415 Display headers of messages scheduled for deletion.
416 .RE
417
418 .sp
419 .ne 2
420 .na
421 \fB\fBm\fR [ \fIpersons\fR ]\fR
422 .ad
423 .RS 22n
424 Mail (and delete) the current message to the named \fIpersons\fR.
425 .RE
426
427 .sp
428 .ne 2
429 .na
430 \fB\fIn\fR\fR
431 .ad
432 .RS 22n
433 Print message number \fIn\fR.
434 .RE
435
436 .sp
437 .ne 2
438 .na
439 \fB\fBp\fR\fR
440 .ad
441 .RS 22n
442 Print current message again, overriding any indications of binary (that is,
443 unprintable) content.
444 .RE
445
446 .sp
447 .ne 2
448 .na
449 \fB\fBP\fR\fR
450 .ad
451 .RS 22n
452 Override default brief mode and print current message again, displaying all
453 header lines.
454 .RE
455
456 .sp
457 .ne 2
458 .na
459 \fB\fBq\fR, or Control-d\fR
460 .ad
461 .RS 22n
462 Put undeleted mail back in the \fImailfile\fR and quit \fBmail\fR.
463 .RE
464
465 .sp
466 .ne 2
467 .na
468 \fB\fBr\fR [ \fIusers\fR ]\fR
469 .ad
470 .RS 22n
471 Reply to the sender, and other \fIusers\fR, then delete the message.
472 .RE
473
474 .sp
475 .ne 2
476 .na
477 \fB\fBs\fR [ \fIfiles\fR ]\fR
478 .ad
479 .RS 22n
480 Save message in the named \fIfiles\fR (\fBmbox\fR is default) and delete the
481 message.
482 .RE
483
484 .sp
485 .ne 2
486 .na
487 \fB\fBu\fR [ \fIn\fR ]\fR
488 .ad
489 .RS 22n
490 Undelete message number \fIn\fR (default is last read).
491 .RE
492
493 .sp
494 .ne 2
495 .na
496 \fB\fBw\fR [ \fIfiles\fR ]\fR
497 .ad
498 .RS 22n
499 Save message contents, without any header lines, in the named \fIfiles\fR
500 (\fBmbox\fR is default) and delete the message.
501 .RE
502
503 .sp
504 .ne 2
505 .na
506 \fB\fBx\fR\fR
507 .ad
508 .RS 22n
509 Put all mail back in the \fImailfile\fR unchanged and exit \fBmail\fR.
510 .RE
511
512 .sp
513 .ne 2
514 .na
515 \fB\fBy\fR [ \fIfiles\fR ]\fR
516 .ad
517 .RS 22n
518 Same as \fB-w\fR option.
519 .RE
520
521 .sp
522 .ne 2
523 .na
524 \fB\fB?\fR\fR
525 .ad
526 .RS 22n
527 Print a command summary.
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
597 Inform the sender that the message was successfully delivered to the
598 \fIrecipient\fR's mailbox.
599 .RE
600
601 .sp
602 .ne 2
603 .na
604 \fB\fB/nodelivery\fR\fR
605 .ad
606 .RS 15n
607 Do not inform the sender of successful deliveries.
608 .RE
609
610 .sp
611 .ne 2
612 .na
613 \fB\fB/ignore\fR\fR
614 .ad
615 .RS 15n
616 Do not inform the sender of failed deliveries.
617 .RE
618
619 .sp
620 .ne 2
621 .na
622 \fB\fB/return\fR\fR
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
730 \fB\fB$HOME/mbox\fR\fR
731 .ad
732 .RS 20n
733 saved mail
734 .RE
735
736 .sp
737 .ne 2
738 .na
739 \fB\fB$MAIL\fR\fR
740 .ad
741 .RS 20n
742 variable containing path name of \fImailfile\fR
743 .RE
744
745 .sp
746 .ne 2
747 .na
748 \fB\fB/tmp/MLDBG\fR*\fR
749 .ad
750 .RS 20n
751 debug trace file
752 .RE
753
754 .sp
755 .ne 2
756 .na
757 \fB\fB/var/mail/*.lock\fR\fR
758 .ad
759 .RS 20n
760 lock for mail directory
761 .RE
762
763 .sp
764 .ne 2
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.