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 "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
92 .sp
93 .LP
94 followed by one or more standardized message header lines of the form:
95 .sp
96 .in +2
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
137
138 .sp
139 .ne 2
140 .na
141 \fB\fB-w\fR\fR
142 .ad
143 .RS 19n
144 A letter is sent to a remote recipient without waiting for the completion of
145 the remote transfer program.
146 .RE
147
148 .sp
149 .LP
150 If a letter is found to be undeliverable, it is returned to the sender with
151 diagnostics that indicate the location and nature of the failure. If \fBmail\fR
152 is interrupted during input, the message is saved in the file \fBdead.letter\fR
153 to allow editing and resending. \fBdead.letter\fR is always appended to, thus
154 preserving any previous contents. The initial attempt to append to (or create)
155 \fBdead.letter\fR is in the current directory. If this fails, \fBdead.letter\fR
156 is appended to (or created in) the user's login directory. If the second
157 attempt also fails, no \fBdead.letter\fR processing is done.
158 .sp
159 .LP
160 \fBrmail\fR only permits the sending of mail; \fBuucp\fR(1C) uses \fBrmail\fR
161 as a security precaution. Any application programs that generate mail messages
162 should be sure to invoke \fBrmail\fR rather than \fBmail\fR for message
163 transport and/or delivery.
164 .sp
165 .LP
166 If the local system has the Basic Networking Utilities installed, mail can be
167 sent to a recipient on a remote system. There are numerous ways to address mail
168 to recipients on remote systems depending on the transport mechanisms available
169 to the local system. The two most prevalent addressing schemes are Domain-style
170 and UUCP-style.
171 .sp
172 .ne 2
173 .na
174 \fBDomain-style addressing\fR
175 .ad
176 .RS 27n
177 Remote recipients are specified by appending an `\fB@\fR' and domain (and
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.
218 .sp
219 An exit status of \fB0\fR is returned if the user has new mail
220 to read, an exit status of \fB1\fR is returned if the user has no
221 mail, or an exit status of \fB2\fR is returned if the user has mail
222 which has already been read.
223 .RE
224
225 .sp
226 .ne 2
227 .na
228 \fB\fB-h\fR\fR
229 .ad
230 .RS 11n
231 A window of headers are initially displayed rather than the latest message. The
232 display is followed by the \fB?\fR prompt.
233 .RE
234
235 .sp
236 .ne 2
237 .na
238 \fB\fB-p\fR\fR
239 .ad
240 .RS 11n
241 All messages are printed without prompting for disposition.
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 with \fIall\fR header lines displayed, rather than the
251 default selective header line display.
252 .RE
253
254 .sp
255 .ne 2
256 .na
257 \fB\fB-q\fR\fR
258 .ad
259 .RS 11n
260 \fBmail\fR terminates after interrupts. Normally an interrupt causes only the
261 termination of the message being printed.
262 .RE
263
264 .sp
265 .ne 2
266 .na
267 \fB\fB-r\fR\fR
268 .ad
269 .RS 11n
270 Messages are printed in first-in, first-out order.
271 .RE
272
273 .sp
274 .ne 2
275 .na
276 \fB\fB-f\fR \fIfile\fR\fR
277 .ad
278 .RS 11n
279 \fBmail\fR uses \fIfile\fR (such as \fBmbox\fR) instead of the default
280 \fImailfile\fR.
281 .RE
282
283 .sp
284 .LP
285 \fBmail\fR, unless otherwise influenced by command-line arguments, prints a
286 user's mail messages in last-in, first-out order. The default mode for printing
287 messages is to display only those header lines of immediate interest. These
288 include, but are not limited to, the UNIX \fBFrom\fR and \fB>From\fR postmarks,
289 \fBFrom:\fR, \fBDate:\fR, \fBSubject:\fR, and \fBContent-Length:\fR header
290 lines, and any recipient header lines such as \fBTo:\fR, \fBCc:\fR, \fBBcc:\fR,
291 and so forth. After the header lines have been displayed, \fBmail\fR displays
292 the contents (body) of the message only if it contains no unprintable
293 characters. Otherwise, \fBmail\fR issues a warning statement about the message
294 having binary content and \fBnot\fR display the content. This can be overridden
295 by means of the \fBp\fR command.
296 .sp
297 .LP
298 For each message, the user is prompted with a \fB?\fR and a line is read from
299 the standard input. The following commands are available to determine the
300 disposition of the message:
301 .sp
302 .ne 2
303 .na
304 \fB\fB#\fR\fR
305 .ad
306 .RS 22n
307 Print the number of the current message.
308 .RE
309
310 .sp
311 .ne 2
312 .na
313 \fB\fB\(mi\fR\fR
314 .ad
315 .RS 22n
316 Print previous message.
317 .RE
318
319 .sp
320 .ne 2
321 .na
322 \fB<new-line>,\fB+\fR, or \fBn\fR\fR
323 .ad
324 .RS 22n
325 Print the next message.
326 .RE
327
328 .sp
329 .ne 2
330 .na
331 \fB\fB!\fR\fIcommand\fR\fR
332 .ad
333 .RS 22n
334 Escape to the shell to do \fIcommand\fR.
335 .RE
336
337 .sp
338 .ne 2
339 .na
340 \fB\fBa\fR\fR
341 .ad
342 .RS 22n
343 Print message that arrived during the \fBmail\fR session.
344 .RE
345
346 .sp
347 .ne 2
348 .na
349 \fB\fBd\fR, or \fBdp\fR\fR
350 .ad
351 .RS 22n
352 Delete the current message and print the next message.
353 .RE
354
355 .sp
356 .ne 2
357 .na
358 \fB\fBd\fR \fIn\fR\fR
359 .ad
360 .RS 22n
361 Delete message number \fIn\fR. Do not go on to next message.
362 .RE
363
364 .sp
365 .ne 2
366 .na
367 \fB\fBdq\fR\fR
368 .ad
369 .RS 22n
370 Delete message and quit \fBmail\fR.
371 .RE
372
373 .sp
374 .ne 2
375 .na
376 \fB\fBh\fR\fR
377 .ad
378 .RS 22n
379 Display a window of headers around current message.
380 .RE
381
382 .sp
383 .ne 2
384 .na
385 \fB\fBh\fR\fIn\fR\fR
386 .ad
387 .RS 22n
388 Display a window of headers around message number \fIn\fR.
389 .RE
390
391 .sp
392 .ne 2
393 .na
394 \fB\fBh a\fR\fR
395 .ad
396 .RS 22n
397 Display headers of all messages in the user's \fImailfile\fR.
398 .RE
399
400 .sp
401 .ne 2
402 .na
403 \fB\fBh d\fR\fR
404 .ad
405 .RS 22n
406 Display headers of messages scheduled for deletion.
407 .RE
408
409 .sp
410 .ne 2
411 .na
412 \fB\fBm\fR [ \fIpersons\fR ]\fR
413 .ad
414 .RS 22n
415 Mail (and delete) the current message to the named \fIpersons\fR.
416 .RE
417
418 .sp
419 .ne 2
420 .na
421 \fB\fIn\fR\fR
422 .ad
423 .RS 22n
424 Print message number \fIn\fR.
425 .RE
426
427 .sp
428 .ne 2
429 .na
430 \fB\fBp\fR\fR
431 .ad
432 .RS 22n
433 Print current message again, overriding any indications of binary (that is,
434 unprintable) content.
435 .RE
436
437 .sp
438 .ne 2
439 .na
440 \fB\fBP\fR\fR
441 .ad
442 .RS 22n
443 Override default brief mode and print current message again, displaying all
444 header lines.
445 .RE
446
447 .sp
448 .ne 2
449 .na
450 \fB\fBq\fR, or Control-d\fR
451 .ad
452 .RS 22n
453 Put undeleted mail back in the \fImailfile\fR and quit \fBmail\fR.
454 .RE
455
456 .sp
457 .ne 2
458 .na
459 \fB\fBr\fR [ \fIusers\fR ]\fR
460 .ad
461 .RS 22n
462 Reply to the sender, and other \fIusers\fR, then delete the message.
463 .RE
464
465 .sp
466 .ne 2
467 .na
468 \fB\fBs\fR [ \fIfiles\fR ]\fR
469 .ad
470 .RS 22n
471 Save message in the named \fIfiles\fR (\fBmbox\fR is default) and delete the
472 message.
473 .RE
474
475 .sp
476 .ne 2
477 .na
478 \fB\fBu\fR [ \fIn\fR ]\fR
479 .ad
480 .RS 22n
481 Undelete message number \fIn\fR (default is last read).
482 .RE
483
484 .sp
485 .ne 2
486 .na
487 \fB\fBw\fR [ \fIfiles\fR ]\fR
488 .ad
489 .RS 22n
490 Save message contents, without any header lines, in the named \fIfiles\fR
491 (\fBmbox\fR is default) and delete the message.
492 .RE
493
494 .sp
495 .ne 2
496 .na
497 \fB\fBx\fR\fR
498 .ad
499 .RS 22n
500 Put all mail back in the \fImailfile\fR unchanged and exit \fBmail\fR.
501 .RE
502
503 .sp
504 .ne 2
505 .na
506 \fB\fBy\fR [ \fIfiles\fR ]\fR
507 .ad
508 .RS 22n
509 Same as \fB-w\fR option.
510 .RE
511
512 .sp
513 .ne 2
514 .na
515 \fB\fB?\fR\fR
516 .ad
517 .RS 22n
518 Print a command summary.
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
584 Inform the sender that the message was successfully delivered to the
585 \fIrecipient\fR's mailbox.
586 .RE
587
588 .sp
589 .ne 2
590 .na
591 \fB\fB/nodelivery\fR\fR
592 .ad
593 .RS 15n
594 Do not inform the sender of successful deliveries.
595 .RE
596
597 .sp
598 .ne 2
599 .na
600 \fB\fB/ignore\fR\fR
601 .ad
602 .RS 15n
603 Do not inform the sender of failed deliveries.
604 .RE
605
606 .sp
607 .ne 2
608 .na
609 \fB\fB/return\fR\fR
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
708 \fB\fB$HOME/mbox\fR\fR
709 .ad
710 .RS 20n
711 saved mail
712 .RE
713
714 .sp
715 .ne 2
716 .na
717 \fB\fB$MAIL\fR\fR
718 .ad
719 .RS 20n
720 variable containing path name of \fImailfile\fR
721 .RE
722
723 .sp
724 .ne 2
725 .na
726 \fB\fB/tmp/MLDBG\fR*\fR
727 .ad
728 .RS 20n
729 debug trace file
730 .RE
731
732 .sp
733 .ne 2
734 .na
735 \fB\fB/var/mail/*.lock\fR\fR
736 .ad
737 .RS 20n
738 lock for mail directory
739 .RE
740
741 .sp
742 .ne 2
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.