/usr/share/doc/mailutils-doc/mailutils.html/Specifying-Messages.html is in mailutils-doc 1:2.99.99-1ubuntu2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Published by the Free Software Foundation,
51 Franklin Street, Fifth Floor
Boston, MA 02110-1301, USA
Copyright (C) 1999-2004, 2008-2012, 2014-2015 Free Software
Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover, and no Back-Cover texts.
A copy of the license is included in the section entitled "GNU Free
Documentation License". -->
<!-- Created by GNU Texinfo 6.1, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Mailutils Manual: Specifying Messages</title>
<meta name="description" content="GNU Mailutils Manual: Specifying Messages">
<meta name="keywords" content="GNU Mailutils Manual: Specifying Messages">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="index.html#Top" rel="start" title="Top">
<link href="Function-Index.html#Function-Index" rel="index" title="Function Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="mail.html#mail" rel="up" title="mail">
<link href="Composing-Mail.html#Composing-Mail" rel="next" title="Composing Mail">
<link href="Invoking-Mail.html#Invoking-Mail" rel="prev" title="Invoking Mail">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smalllisp {margin-left: 3.2em}
kbd {font-style: oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nolinebreak {white-space: nowrap}
span.roman {font-family: initial; font-weight: normal}
span.sansserif {font-family: sans-serif; font-weight: normal}
ul.no-bullet {list-style: none}
-->
</style>
</head>
<body lang="en">
<a name="Specifying-Messages"></a>
<div class="header">
<p>
Next: <a href="Composing-Mail.html#Composing-Mail" accesskey="n" rel="next">Composing Mail</a>, Previous: <a href="Invoking-Mail.html#Invoking-Mail" accesskey="p" rel="prev">Invoking Mail</a>, Up: <a href="mail.html#mail" accesskey="u" rel="up">mail</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Function-Index.html#Function-Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="How-to-Specify-Message-Sets"></a>
<h4 class="subsection">2.5.2 How to Specify Message Sets</h4>
<p>Many mail commands such as print and delete can be given a <em>message list</em>
to operate upon. Wherever the message list is omitted, the command
operates on the current message.
</p>
<p>The <em>message list</em> in its simplest form is one of:
</p>
<dl compact="compact">
<dt>.</dt>
<dd><p>Selects current message. It is equivalent to empty message list.
</p></dd>
<dt>*</dt>
<dd><p>Selects all messages in the mailbox.
</p></dd>
<dt>^</dt>
<dd><p>Selects first non-deleted message.
</p></dd>
<dt>$</dt>
<dd><p>Selects last non-deleted message.
</p></dd>
</dl>
<p>In its complex form, the <em>message list</em> is a comma or whitespace-separated
list of <em>message specifiers</em>. A <em>message specifier</em> is one
of
</p>
<dl compact="compact">
<dt>Message Number</dt>
<dd><p>This specifier addresses the message with the given ordinal number
in the mailbox.
</p></dd>
<dt>Message range</dt>
<dd><p><em>Message range</em> is specified as two message numbers separated by
a dash. It selects all messages with the number lying within that range.
</p></dd>
<dt>Attribute specifier</dt>
<dd><p>An <em>Attribute specifier</em> is a colon followed by a single
letter. The <em>Attribute specifier</em> addresses all messages in the
mailbox that have the given attribute. These are the valid attribute
specifiers:
</p>
<dl compact="compact">
<dt>‘<samp>:d</samp>’</dt>
<dd><p>Selects all deleted messages.
</p></dd>
<dt>‘<samp>:n</samp>’</dt>
<dd><p>Selects all recent messages, i.e. the messages that have not been
neither read not seen so far.
</p></dd>
<dt>‘<samp>:o</samp>’</dt>
<dd><p>Selects all messages that have been seen.
</p></dd>
<dt>‘<samp>:r</samp>’</dt>
<dd><p>Selects all messages that have been read.
</p></dd>
<dt>‘<samp>:u</samp>’</dt>
<dd><p>Selects all messages that have <em>not</em> been read.
</p></dd>
<dt>‘<samp>:t</samp>’</dt>
<dd><p>Selects all tagged messages.
</p></dd>
<dt>‘<samp>:T</samp>’</dt>
<dd><p>Selects all untagged messages.
</p></dd>
</dl>
</dd>
<dt>Header match</dt>
<dd><p>The <em>header match</em> is a string in the form:
</p>
<div class="example">
<pre class="example">[<var>header</var>:]/<var>string</var>/
</pre></div>
<p>It selects all messages that contain header field <var>header</var>
matching given <var>regexp</var>. If the variable <code>regexp</code> is set,
the <var>string</var> is assumed to be a POSIX regexp. Otherwise, a
header is considered to match <var>string</var> if the latter constitutes
a substring of the former (comparison is case-insensitive).
</p>
<p>If <var>header</var>: part is omitted, it is assumed to be ‘<samp>Subject:</samp>’.
</p></dd>
<dt>Message body match</dt>
<dd><p>The <em>message body match</em> is a string in the form:
</p>
<div class="example">
<pre class="example">:/<var>string</var>/
</pre></div>
<p>It selects all messages whose body matches the string. The matching
rules are the same as described under “Header match”.
</p></dd>
</dl>
<p>A <em>message specifier</em> can be followed by <em>message part
specifier</em>, enclosed in a pair of brackets. A <em>message part
specifier</em> controls which part of a message should be operated upon.
It is meaningful only for multipart messages. A <em>message part
specifier</em> is a comma or whitespace - separated list of part numbers
or ranges. Each part number can in turn be <em>message part specifier</em>,
thus allowing for operating upon multiply-encoded messages.
</p>
<p>The following are the examples of valid message lists:
</p>
<hr>
<div class="header">
<p>
Next: <a href="Composing-Mail.html#Composing-Mail" accesskey="n" rel="next">Composing Mail</a>, Previous: <a href="Invoking-Mail.html#Invoking-Mail" accesskey="p" rel="prev">Invoking Mail</a>, Up: <a href="mail.html#mail" accesskey="u" rel="up">mail</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Function-Index.html#Function-Index" title="Index" rel="index">Index</a>]</p>
</div>
</body>
</html>
|