1RMM(1) [nmh-1.3] RMM(1)
2
3
4
6 rmm - remove messages
7
9 rmm [+folder] [msgs] [-link | -nolink] [-version] [-help]
10
12 By default, rmm will remove the specified messages by renaming the mes‐
13 sage files with preceding commas. Such files will then need to be
14 removed in some manner after a certain amount of time. Many sites
15 arrange for cron to remove these files once a day, so check with your
16 system administrator.
17
18 Alternately, if you wish for rmm to really remove the files represent‐
19 ing these messages, you can use the -unlink switch. But messages
20 removed by this method cannot be later recovered.
21
22 If you prefer a more sophisticated method of `removing' messages, you
23 can define the rmmproc profile component. For example, you can add a
24 profile component such as
25
26 rmmproc: /home/foouser/bin/rmm_msgs
27
28 then instead of simply renaming the message file, rmm will call the
29 named program or script to handle the files that represent the messages
30 to be deleted.
31
32 Some users of csh prefer the following:
33
34 alias rmm 'refile +d'
35
36 where folder `+d' is a folder for deleted messages, and
37
38 alias mexp 'rm `mhpath +d all`'
39
40 is used to “expunge” deleted messages.
41
42 The current message is not changed by rmm, so a next
43 will advance to the next message in the folder as expected.
44
45
47 $HOME/.mh_profile The user profile
48
49
51 Path: To determine the user's nmh directory
52 Current-Folder: To find the default current folder
53 rmmproc: Program to delete the message
54
55
57 refile(1), rmf(1)
58
59
61 `+folder' defaults to the current folder
62 `msgs' defaults to cur
63 `-nounlink'
64
65
67 If a folder is given, it will become the current folder.
68
69
71 Since refile uses your rmmproc to delete the message, the rmmproc must
72 NOT call refile without specifying -normmproc, or you will create an
73 infinte loop.
74
75
76
77MH.6.8 1 June 2008 RMM(1)