1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
|
.TH RMM %manext1% 2013-03-19 "%nmhversion%"
.
.\" %nmhwarning%
.
.SH NAME
rmm \- remove nmh messages
.SH SYNOPSIS
.HP 5
.na
.B rmm
.RB [ \-help ]
.RB [ \-version ]
.RI [ +folder ]
.RI [ msgs ]
.RB [ \-unlink " | " \-nounlink ]
.RB [ \-rmmproc
.IR program ]
.RB [ \-normmproc ]
.ad
.SH DESCRIPTION
By default,
.B rmm
will remove the specified messages by renaming each of the message files
with a site-dependent prefix (usually a comma).
Such files will then need to be removed in some manner after a period of
time.
Many sites arrange for
.B cron
to remove these files once a day, so check with your system administrator.
.PP
Alternately, if you wish for
.B rmm
to really remove the files representing these messages, you can use the
.B \-unlink
switch.
But messages removed by this method cannot be later recovered.
.PP
If you prefer a more sophisticated method of `removing' messages, you
can define the
.I rmmproc
profile component.
For example, you can add a profile component such as
.PP
.RS 5
rmmproc: /home/foouser/bin/rmm_msgs
.RE
.PP
Then instead of simply renaming the message file,
.B rmm
will call the named program or script to handle the files that
represent the messages to be deleted.
The
.B \-rmmproc
switch may be used to override this profile component. The
.B \-normmproc
switch disables the use of any
.I rmmproc
profile component and negates all prior
.B \-rmmproc
switches.
.PP
An example of a
.I rmmproc
script that saves a message based in its Message-ID is provided in
/usr/share/doc/nmh/examples/rmmproc.messageid. To enable it, simply add an
.I rmmproc
component that names it, to your profile.
.PP
Some users of
.B csh
prefer the following:
.PP
.RS 5
alias rmm 'refile +d'
.RE
.PP
where folder `+d' is a folder for deleted messages, and
.PP
.RS 5
alias mexp 'rm \`mhpath +d all\`'
.RE
.PP
is used to \*(lqexpunge\*(rq deleted messages.
.PP
The current message is not changed by
.BR rmm ,
so a
.B next
will advance to the next message in the folder as expected.
.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
^Path:~^To determine the user's nmh directory
^Current\-Folder:~^To find the default current folder
^rmmproc:~^Program to delete the message
.fi
.SH "SEE ALSO"
.IR rmf (1)
.SH DEFAULTS
.nf
.RB ` +folder "' defaults to the current folder"
.RB ` msgs "' defaults to cur"
.RB ` \-nounlink '
.fi
.SH CONTEXT
If a folder is given, it will become the current folder.
.SH BUGS
Since
.B rmm
and
.B refile
use your
.I rmmproc
to delete the message, the
.I rmmproc
must
.I not
call
.B rmm
or
.B refile
without specifying
.BR \-normmproc ,
or you will create an infinite loop.
|
