{
    "mode": "man",
    "parameter": "rmm",
    "section": "1",
    "url": "https://www.chedong.com/phpMan.php/man/rmm/1/json",
    "generated": "2026-05-30T06:10:48Z",
    "synopsis": "rmm [-help] [-version] [+folder] [msgs] [-unlink | -nounlink] [-rmmproc program] [-normmproc]",
    "sections": {
        "NAME": {
            "content": "rmm - remove nmh messages\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "rmm [-help] [-version] [+folder] [msgs] [-unlink | -nounlink] [-rmmproc program] [-normmproc]\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "By default, rmm will remove the specified messages by renaming each of the message files with\na site-dependent prefix (usually a comma).  Such files will then need to be removed  in  some\nmanner after a period of time.  Many sites arrange for cron to remove these files once a day,\nso check with your system administrator.\n\nAlternately, if you wish for rmm to really remove the files representing these messages,  you\ncan use the -unlink switch.  But messages removed by this method cannot be later recovered.\n\nIf  you prefer a more sophisticated method of `removing' messages, you can define the rmmproc\nprofile component.  For example, you can add a profile component such as\n\nrmmproc:    /home/foouser/bin/rmmmsgs\n\nThen instead of simply renaming the message file, rmm will call the named program  or  script\nto  handle  the  files that represent the messages to be deleted.  The -rmmproc switch may be\nused to override this profile component.  The -normmproc switch disables the use of any  rmm‐\nproc profile component and negates all prior -rmmproc switches.\n\nAn  example  of  a rmmproc script that saves a message based in its Message-ID is provided in\n/usr/share/doc/nmh/examples/rmmproc.messageid.  To enable it, simply add an rmmproc component\nthat names it, to your profile.\n\nSome users of csh prefer the following:\n\nalias rmm 'refile +d'\n\nwhere folder `+d' is a folder for deleted messages, and\n\nalias mexp 'rm `mhpath +d all`'\n\nis used to “expunge” deleted messages.\n\nThe  current message is not changed by rmm, so a next will advance to the next message in the\nfolder as expected.\n",
            "subsections": []
        },
        "FILES": {
            "content": "$HOME/.mhprofile          The user profile\n",
            "subsections": []
        },
        "PROFILE COMPONENTS": {
            "content": "Path:                To determine the user's nmh directory\nCurrent-Folder:      To find the default current folder\nrmmproc:             Program to delete the message\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "rmf(1)\n",
            "subsections": []
        },
        "DEFAULTS": {
            "content": "`+folder' defaults to the current folder\n`msgs' defaults to cur\n`-nounlink'\n",
            "subsections": []
        },
        "CONTEXT": {
            "content": "If a folder is given, it will become the current folder.\n",
            "subsections": []
        },
        "BUGS": {
            "content": "Since rmm and refile use your rmmproc to delete the message, the rmmproc must not call rmm or\nrefile without specifying -normmproc, or you will create an infinite loop.\n\n\n\nnmh-1.7.1                                    2013-03-19                                     RMM(1mh)",
            "subsections": []
        }
    },
    "summary": "rmm - remove nmh messages",
    "flags": [],
    "examples": [],
    "see_also": [
        {
            "name": "rmf",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/rmf/1/json"
        }
    ]
}