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
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
|
Major changes since 0.96.3
--------------------------
- The $in_reply_to configuration variable is gone. The In-Reply-To
header currently only contains the message-id of the message to
which the reply refers. This is to make sure that this header is
correctly formatted.
- There is a new variable named $pgp_getkeys_command. It's invoked
before mutt invokes PGP in a way which may require public keys.
The %r format string expands to an e-mail address corresponding to
that key. The command given in $pgp_getkeys_command could, for
instance, query a key server and add public keys to your key ring.
See also http://home.pages.de/~roessler/pkspxy-0.1.tar.gz for a
possible application of this with the traditional PGP versions.
- RFC 2231 is (at least partially) implemented. Additionally, there
is an option named $rfc2047_parameters. When it's set, mutt will
decode RFC2047-encoded MIME parameters.
- Various IMAP-related fixes and patches. This includes the ability
to use IMAP folders for postponed messages, improved IMAP folder
browsing, tab completion for IMAP folders, etc.
- A new variable $from is added.
* $from is used as the default from address, if defined.
Otherwise, the local user nanme and (if the user wishes so) the
local domain are used.
* This address can be overridden by $reverse_name, if set.
* Now, send-hooks are evaluated.
* Afterwards, user headers are evaluated. In this step, the from
header can be overridden using my_hdr From:.
* When there is no real name, $realname is used for it. Note
that, when the default from header is used and $from defines a
real name, it takes precedence over $realname.
- There is a new model for mailing list handling: We distinguish
between subscribed and unsubscribed lists. With the configuration
command "lists", you add a list to the list of known mailing
lists. With "subscribe", you add a list to the lists of known
_and_ subscribed lists. With "unsubscribe", you remove a list
from the list of subscribed lists. With "unlists", you remove a
list from the lists of subscribed and known mailing lists.
The list of known mailing lists is used for the list-reply command
and the $ignore_list_reply_to configuration optio. The list of
subscribed mailig lists is used for header display, and the
construction of Mail-Followup-To headers.
- The various weeding options are gone. You have a global option
$weed now which can be influenced using confugration commands, or
using the display-headers or display-message functions. This
option is applied when forwarding, replying, or printing messages.
Essentially, this means that you have some "WYSIWIG-like"
behaviour with respect to message header weeding.
Major changes since 0.96.2
--------------------------
- The PGP configuration interface was completely redone. Please
read doc/PGP-Notes.txt before installing this version on any
production system.
Major changes since 0.95
------------------------
- Mutt was affected by the so-called "pine remote exploit". We have
implemented a work-around we believe to be safe. See
README.SECURITY and the mailcap_sanitize option for details, and
check your mailcap files for insecure entries.
- The use_mailcap option has gone. Instead, we now have
implicit_autoview. See the manual for details.
- We have more translations than ever before. Supported languages
now include cs, de, es, fr, id, it, ko, nl, pl, ru, sk, uk. And
en, as usual.
- Mutt now uses version 0.12 of the "regex" library instead of rx.
This library is believed to be far more stable than rx. See
INSTALL for details.
- The annoying "maildir erratic behaviour" bug could finally be
tracked down and fixed as of 0.95.6.
- There were some major improvements with the IMAP code. It should
work rather correctly against most common IMAP servers now.
Major changes since 0.93
------------------------
- i18n support of various kinds: Mutt now comes with character set
definitions, so it is able to convert character sets you encounter
in e-mail messagese to your local display's character set as
defined by the $charset configuration variable. This includes a
poorly-tested UTF-8 decoder.
Additionally, mutt includes GNU gettext support, so you can make
it speak your own language. To use this, just set the environment
variable "LANG" appropriately.
(For a list of currently supported languages, have a look at the
po files in the po subdirectory.)
- There is support for the POP3 "last" command for just fetching the
latest unread messages from your POP server. To enable use of
this feature, set the $pop_last configuration option.
- The IMAP code's handling of server-side EXPUNGE messages was
fixed, so mutt should now be able to cope with concurrent access
to IMAP folders. This is, e.g., supported by the CMU and MS
Exchange IMAP servers.
- mh_sequences support was _dropped_. The reason is, on the one
hand, a major re-write of the mh and maildir folder
resynchronization code, and the fact that there is no locking
protocol defined for this file. If you want to use
one-file-per-message folders, you should better rely on maildir.
- The new patterns ~g and ~G in the pattern language match PGP
signed and encrypted messages, respectively.
- The $smileys configuration variable defines exceptions from the
quote-detecting regular expressions. This can be used to
correctly handle lines beginning with smileys such as ":-)" -
these lines were detected as quoted text by the old code.
- You can now edit messages in your mail folders.
The function 'edit' (default 'e') will make a copy of the
current message and you can edit the message. After editing is
complete, you are taken to the Compose menu. You can further
modify the message here or re-send it. Note that the message is
re-sent to the original recipients (similar to `bounce-message')
unless you have changed the recipients in the Compose menu (or the
editor).
You can also write the edited message back to any mail folder
using the write-fcc function (default w). Remember that you are
working with a copy and the original message is not affected.
- new command 'unhdr_order'
`unhdr_order *' will clear all previous headers from the order
list, thus removing the header order effects set by the
system-wide startup file (via `hdr_order')
- You can now attach message(s) to an outgoing message. Use the
attach-message function (default 'A') from the Compose menu;
specify the folder to open and tag the messages you want to
attach.
- You can now collapse a thread.
collapse-thread (default ESC v) toggles the collapsed state of the
current thread.
collapse-all (default ESC V) toggles the collapsed state of all
threads in the folder.
When a collapsed thread received new messages, it is automatically
uncollapsed. Also, when you display the first message in the
collapsed thread, it is automatically uncollapsed.
The variables $collapse_unread and $uncollapse_jump can be used to
fine-tune this feature.
Note: Collapsing a thread displays only the first message in the
thread and hides the others. This is useful when threads contain
so many messages that you can only see a handful of threads on the
screen. See %M in ``$index_format''. For example, you could use
"%?M?(#%03M)&(%4l)?" in ``$index_format'' to optionally display
the number of hidden messages if the thread is collapsed.
- The syntax for function keys in key bindings and macro definitions
has changed: Instead of "fN", you have to use "<fN>" now. This
is more consistant with the syntax for the other special keys like
"<up>", "<down>", and so on.
- You can now use function names in macros. The syntax is <function-name>
Example:
macro index z "v<down><down><first-entry><down><save-entry>"
push "<first-entry><display-message>"
Note that the function has to be a valid function for the menu when
the macro is _executed_. If not, the literal string of characters is
used as usual. Also, if you enter a string <...> which is NOT a Mutt
function like <vikas>, the literal string of characters is used as
usual.
Keep in mind that macros are evaluated at runtime, and so the
current menu could change _during_ the execution of a macro. Be sure
to use functions that make sense for the menu at that point in the
macro's execution.
- new command 'exec'.
You can now use the 'exec' command to execute any internal function
in Mutt. You can also execute functions in this fashion even if they
are not bound to any key.
Also, the 'exec' command has command completion so that
:exec <TAB><TAB>
will cycle thru all the commands for that menu.
If you type something that is not found in the current menu, the
generic menu is used for completion.
The 'exec' command accepts multiple arguments each with its own
command-completion.
For example:
:exec first-entry display-message ....
Similar to macros, keep in mind that the sequence of functions are
evaluated at runtime, and so the current menu could change _during_
the execution of a sequence of functions. Be sure to use functions
that make sense for the menu _at that point_ in the execution.
- improved command and variable completion.
Pressing <TAB>, on the command-line now cycles through all possible
matches of the command (or variable) based on what you have typed so
far. When all matches have been cycled through, your original input
(that started the completion) is restored. Pressing <TAB> again
repeats the cycle.
Note that variable completion is done only when appropriate (for the
following commands: set, reset, unset, toggle). Also, when entering
a 'set' command, the possible prefixes to the variable name (no,
inv, ?, &) are honored. This makes it possible to do something like
:set inv<TAB><TAB>
to cycle through the possible matches.
When you press <TAB> without entering any text, Mutt cycles through
all possible matches (commands or variables, as appropriate)
- you can now use special keys in a key _sequence_. Special keys are
<Home>, <End>, <PageUp>, etc.
Example:
macro attach s "<Home>~/<End>" "Pre-pend ~/ when saving attachments"
- You can now specify an optional description for your macros.
Usage: macro menu key sequence [ description ]
The specified description is listed on the help screen.
Example:
macro index "^\cb" "|urlview\n" "call urlview to extract URLs"
- We have a new set of functions decrypt-{save,copy}. They strip off
the initial layer of PGP/MIME encryption. For "classical"
application/pgp messages, they are equivalent to the decode
functions, for unencrypted messages they fall back to the normal
save functions.
- new variable $forward_decrypt. See the manual for details.
- The build-time "hidden host" option has gone. Use the
$hidden_host configuration variable instead.
- Unknown major MIME types are recognized properly.
- new variables $attach_split (boolean, default set) and $attach_sep
(string, default "\n")
If $attach_split is unset, when operating (saving, printing, piping,
etc) on a list of tagged attachments, Mutt will concatenate the
attachments and will operate on them as a single attachment. The
`$attach_sep' separator is added after each attachment. When set
(default), Mutt will operate on the attachments one by one.
- An option $write_bcc controls whether or not the Bcc header is
written out to the mail transport agent or not. Exim users may
wish to use this.
- The compose menu tries to detect and smoothly handle changes to
attached files. Additionally, you can use the update-encoding
function to update an attachment's encoding.
- On the compose menu, you can generate a "private" copy of an
attached file using the get-attachment function.
- sendmail's exit values are properly interpreted, so you will no
longer get a "no such file or directory" error when sending mail
to a non-existing local user.
- The variable $attach_format controls the look of the compose and
attach menus.
- The file browser permits you to view files before selecting them.
- Bug fixes of all kinds. Look at the ChangeLog file for details.
- The configuration files now go to a directory determined by the
--sysconfdir parameter to the configure script. The default is
${prefix}/etc. (The install target of the top-level Makefile will
take care of your old site-global configuration file and
automagically move it to the new place.)
- new variable $mh_purge (boolean, default unset)
When unset, mutt will mimic mh's behaviour and rename deleted
messages to ,<old file name> in mh folders instead of really
deleting them. If the variable is set, the message files will
simply be deleted.
- new variable $forward_weed (boolean, default set)
When set, this decode-forwarding a message will weed the message's
header. (That's the current behaviour.)
$Id$
|