1 .TH RMM %manext1% "February 13, 2013" "%nmhversion%"
13 .RB [ \-unlink " | " \-nounlink ]
20 will remove the specified messages by renaming
21 each of the message files with a site-dependent prefix (usually a
22 comma). Such files will then need to
23 be removed in some manner after a certain amount of time. Many sites
26 to remove these files once a day, so check
27 with your system administrator.
29 Alternately, if you wish for
31 to really remove the files
32 representing these messages, you can use the
35 messages removed by this method cannot be later recovered.
37 If you prefer a more sophisticated method of `removing' messages, you
40 profile component. For example, you can
41 add a profile component such as
44 rmmproc: /home/foouser/bin/rmm_msgs
47 then instead of simply renaming the message file,
50 the named program or script to handle the files that represent the
51 messages to be deleted.
55 script that saves a message based in its Message-ID is provided in
56 %etcdir%/rmmproc.messageid. To enable it, simply add a
58 component that names it to your profile.
68 where folder `+d' is a folder for deleted messages, and
71 alias mexp 'rm `mhpath +d all`'
74 is used to \*(lqexpunge\*(rq deleted messages.
76 The current message is not changed by
81 advance to the next message in the folder as expected.
85 .ta \w'%etcdir%/ExtraBigFileName 'u
86 ^$HOME/\&.mh\(ruprofile~^The user profile
88 .SH "PROFILE COMPONENTS"
92 .ta \w'ExtraBigProfileName 'u
93 ^Path:~^To determine the user's nmh directory
94 ^Current\-Folder:~^To find the default current folder
95 ^rmmproc:~^Program to delete the message
101 .RB ` +folder "' defaults to the current folder"
102 .RB ` msgs "' defaults to cur"
106 If a folder is given, it will become the current folder.
112 to delete the message,
121 or you will create an infinte loop.