-
-Furthermore, the incoming message may be added to additional sequences
-as they arrive by the use of the `\-sequence' switch. As with the
-commands \fIpick\fP and \fImark\fP, you may also use the switches
-`\-zero' and `\-nozero' to specify whether to zero old sequences or not.
-Similarly, use of the `\-public' and `\-nopublic switches may be used
-to force these sequences to be public or private sequences.
-
-.Fi
-^$HOME/\&.mh\(ruprofile~^The user profile
-.Pr
+.PP
+Furthermore, the incoming messages may be added to additional sequences
+as they arrive by the use of the
+.B \-sequence
+switch. As with the commands
+.B pick
+and
+.BR mark ,
+you may also use the switches
+.B \-zero
+and
+.B \-nozero
+to specify whether to zero old sequences or not.
+Similarly, use of the
+.B \-public
+and
+.B \-nopublic
+switches may be used to force these sequences to be public or
+private sequences.
+.SS Locking and \-unseen
+If you use the \*(lqUnseen-Sequence\*(rq profile entry, rcvstore could
+try to read and update its sequence state while another
+.B nmh
+process is also trying to do so. This can cause the sequence state to
+lose track. To avoid this, just between asynchronous invocations of
+.BR rcvstore ,
+do not use it without an external locking mechanism, for example, a
+.IR procmailrc (5)
+local lockfile, if you use the \*(lqUnseen-Sequence\*(rq profile entry.
+.SH FILES
+.fc ^ ~
+.nf
+.ta \w'%nmhetcdir%/ExtraBigFileName 'u
+^$HOME/.mh_profile~^The user profile
+.fi
+.SH "PROFILE COMPONENTS"
+.fc ^ ~
+.nf
+.ta 2.4i
+.ta \w'ExtraBigProfileName 'u