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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML//EN">
<html>
<head>
<title>MHonArc v2.5 -- Release Notes</title>
</head>
<!--
<body background="ssbg75.jpg"
text="#000000" link="#0000ee" vlink="#551a8b" alink="ff0000">
-->
<body>
<!--X-NavButtons-Start-->
<table width="100%">
<tr valign="top">
<td align="left"><nobr><a href="intro.html"><img src="prev.gif"border=0 alt="[Prev]"></a> </nobr></td><td align="center" width="99%"><a href="mhonarc.html"><img src="up.gif" border=0 alt="[TOC]"></a><a href="faq/faq.html"><img src="faq.gif" border=0 alt="[FAQ]"></a><a href="app-bugs.html"><img src="bug.gif" border=0 alt="[Bugs]"></a><a href="http://www.mhonarc.org/"><img src="home.gif" border=0 alt="[Home]"></a></td><td align="right"><nobr> <a href="install.html"><img src="next.gif" border=0 alt="[Next]"></a></nobr></td></tr></table>
<!--X-NavButtons-End-->
<hr>
<h1><a name="relnotes">Release Notes</a></h1>
<p>Read the <tt>CHANGES</tt> document included in the distribution
for a more complete summary of changes to
MHonArc. This document highlights important changes that have occurred
and important usage details which you should be aware of before using
MHonArc. If you are upgrading from a previous release, make sure to
check for the
<a href="#important">highlighted incompatibilites</a>
from earlier releases.
</p>
<!--X-TOC-Start-->
<ul>
<li><a href="#important">Compatibility Notes</a>
<ul>
<li><small><a href="#v2.4.x-defrcname">UPGRADING FROM v2.4.x OR EARLIER: DEFRCNAME Change</a></small>
<li><small><a href="#v2.4.x-header-footer">UPGRADING FROM v2.4.x OR EARLIER: HEADER and FOOTER Removed</a></small>
<li><small><a href="#v2.4.x-mimefilters">UPGRADING FROM v2.4.x OR EARLIER: MIMEFILTERS API Change</a></small>
<li><small><a href="#v2.1.x-dbedit">UPGRADING FROM v2.1.x OR EARLIER: Database Format Change</a></small>
<li><small><a href="#down">DOWNGRADING TO OLDER VERSIONS</a></small>
</ul>
<li><a href="#general">General Notes</a>
</ul>
<!--X-TOC-End-->
<!-- *************************************************************** -->
<hr>
<h2><a name="important">Compatibility Notes</a></h2>
<p>This sections provides notes dealing with compatibility issues
if upgrading from a previous release of MHonArc:
</p>
<h3><a name="v2.4.x-defrcname">UPGRADING FROM v2.4.x OR EARLIER: DEFRCNAME Change</a></h3>
<p>The default value for the <a
href="resources/defrcname.html">DEFRCNAME</a> is now called
"<tt>.mhonarc.mrc</tt>", or "<tt>mhonarc.mrc</tt>" under
Windows and VMS. The old value was "<tt>.mhonarc.rc</tt>", or
"<tt>mhonarc.rc</tt>". If you use the default resource file,
you will need to rename the file to match the filenames used for
v2.5 and later.
</p>
<h3><a name="v2.4.x-header-footer">UPGRADING FROM v2.4.x OR EARLIER: HEADER and FOOTER Removed</a></h3>
<p>The HEADER and FOOTER resources are no longer supported.
If you are using these resources, the HEADER content and
FOOTER content will be lost once v2.5, or later, of
MHonArc processes an archive containing these resources.
</p>
<p>The HEADER and FOOTER resources have been deprecated for
a long time since they only applied to the main index; the
thread index has no equivalent. The
<a href="resources/idxpgbegin.html">IDXPGBEGIN</a>
or <a href="resources/listbegin.html">LISTBEGIN</a>
resources can be used to achieve the same effect of HEADER.
The <a href="resources/idxpgend.html">IDXPGEND</a>
or <a href="resources/listend.html">LISTEND</a>
can be used to achieve the same effect
of FOOTER.
</p>
<h3><a name="v2.4.x-mimefilters">UPGRADING FROM v2.4.x OR EARLIER: MIMEFILTERS API Change</a></h3>
<p>The API for data filters registered via
<a href="resources/mimefilters.html">MIMEFILTERS</a>
is not capability with filters written for v2.4.x and
earlier. See CHANGES and the documentation for the
<a href="resources/mimefilters.html">MIMEFILTERS</a> resource
for the API.
</p>
<p>If you use custom style filters written for v2.4.x, or earlier,
you will need to update them for them to work properly under
v2.5, and later.
</p>
<h3><a name="v2.1.x-dbedit">UPGRADING FROM v2.1.x OR EARLIER: Database Format Change</a></h3>
<p>If you have archives created with v2.1.x, or earlier, you
must update the archives before using versions v2.2, or
later. The format of how mime-related information is stored
has changed.
</p>
<p>To update your archives, you use the <tt>mha-dbedit</tt> program
using the <tt>def-mime.mrc</tt> in the examples directory. For example:
</p>
<pre>
mha-dbedit -rcfile examples/def-mime.mrc \
-outdir /path/to/archive </pre>
<p>Make sure that the mhonarc you are using is v2.2, or later.
Change the <a href="resources/rcfile.html">-rcfile</a>
and <a href="resources/outdir.html">-outdir</a> pathnames to reflect where
you are running mhonarc and where your archive is located,
respectively.
</p>
<p>Note, if your archives are using custom settings of
<a href="resources/mimefilters.html">MIMEFILTERS</a>,
<a href="resources/mimeargs.html">MIMEARGS</a>, and/or
<a href="resources/charsetconverters.html">CHARSETCONVERTERS</a>
resources,
you will need to create a variant version of def-mime.mrc
(included in the examples directory) to include your settings
and use the variant version when updating your archives.
</p>
<h3><a name="down">DOWNGRADING TO OLDER VERSIONS</a></h3>
<p>Downgrading to an earlier version of MHonArc can be
dangerous, especially if downgrading to an older version that
used different storage formats in archive database files from
the current version in use.
If an older version of MHonArc is
used to process an archive last updated by a new version, archive
data can get lost and/or unexpected output can occur.
</p>
<p>Changes in archive format are not common, so downgrading
can be okay depending on the versions involved. The key versions
to watch out for are the ones noted in this section where
database format changes have occured. The following lists
release numbers where a format change occured:
</p>
<ul>
<li>2.0.0</li>
<li>2.2.0</li>
<li>2.5.0</li>
</ul>
<p>For example, if an archive was last updated with v2.5.0,
processing the archive with a previous release will cause problems.
</p>
<p>A possible method for successfully downgrading to a release
with differences in the database format,
is to try to reconstruct the database file using
the <a href="app-utilsprg.html#mha-dbrecover"><tt>mha-dbrecover</tt></a>
utility contained in the MHonArc version the archive is being
downgraded to.
</p>
<p>Of course, the safest way to downgrade is to recreate an archive
from the original raw mail data. It is good practice to preserve
the raw mail data in some form for cases like these and for
general archive recovering situations due to file corruption or other
system failures.
</p>
<!-- *************************************************************** -->
<hr>
<h2><a name="general">General Notes</a></h2>
<ul>
<li><p>For v2.5, the default text/html filter (mhtxthtml.pl) will
now convert auto-loaded URL attributes to
'<tt>javascript:void(0);</tt>' for some HTML elements --
<tt>IMG</tt>, <tt>BODY</tt>, <tt>IFRAME</tt>, <tt>FRAME</tt>,
<tt>OBJECT</tt>, <tt>SCRIPT</tt>, <tt>INPUT</tt> -- except for cid:
URLs. This behavior can be disabled if the '<tt>allownoncidurls</tt>'
filter argument is specified.
</p>
<p>The new behavior is to prevent malicious URLs that verify
mail addresses for spam purposes, secretly set cookies, or
gather some statistical data automatically with the use of
elements that cause browsers to automatically fetch data.
</p>
</li>
<li><p>ISO-8859 character set data processing now defaults to using
the <tt>MHonArc::CharEnt</tt> module in v2.5. The old <tt>iso8859.pl</tt>
library is still provided for compatibility with older
archives. To update archives to use the new settings, you
can run the following command,
</p>
<pre>
mha-dbedit -rcfile examples/def-mime.mrc \
-outdir /path/to/archive </pre>
<p>where "examples/def-mime.mrc" represents the default MIME
processing resources for MHonArc provided within the MHonArc
distribution.
</p>
</li>
<li><p>The value of the <a href="resources/tslice.html">TSLICE</a>
resource is used to determine the number of messages to update,
before and after by thread, of each new message added. To
insure that messages within a thread slice are updated when
a new message is added, make sure the before and after ranges
specified for <a href="resources/tslice.html">TSLICE</a> is
equal to maximum before and the maximum after range arguments
specifed in the uses of the
<a href="rcvars.html#TSLICE"><tt>$TSLICE$</tt></a> resource
variable. For example, if you have <tt>$TSLICE(0;4)$</tt> and
<tt>$TSLICE(3;3)$</tt> in message layout resources, you should
set TSLICE to <tt>3:4</tt>.
</p>
<p>If you only use <tt>$TSLICE$</tt> once, it is best to
set options for thread slice formatting via the
TSLICE resource so you will not have anything to worry about.
</p>
<li><p>If updgrading from v2.4.x, or earlier, reference and follow-up
information of a message is now stored in a different format
in the database (and internally). MHonArc will auto-update
older archives to the new format, so no action should be
required on your part.
</p>
</li>
<li><p>If upgrading from v2.1.x, or earlier, any custom filters you
have developed may need to modified. If your filter accessed
some main variables, your filter will not operate properly.
All variables that used to be in package "main" are no longer.
The major variables are now in package "mhonarc". For example,
<tt>$::OUTDIR</tt> is now <tt>$mhonarc::OUTDIR</tt>. See the
<a href="resources/mimefilters.html">MIMEFILTERS</a>
resource page for more information.
</p>
</li>
<li><p>See the warnings in the documentation for the
<a href="resources/htmlext.html">HTMLEXT</a> and
<a href="resources/msgprefix.html">MSGPREFIX</a>
resources before using them.
</p>
</li>
<li><p>Occasionally, a new release of MHonArc may contain new
MIME filters. See the <tt>CHANGES</tt> file to check if any new filters
have been added.
</p>
<p>If you confirm that new filters have been added, and you want
to apply them to your archives, you use the <tt>mha-dbedit</tt>
program
using the <tt>def-mime.mrc</tt> in the examples directory. For example:
</p>
<pre>
mha-dbedit -rcfile examples/def-mime.mrc \
-outdir /path/to/archive </pre>
<p>Change the <a href="resources/rcfile.html">-rcfile</a>
and <a href="resources/outdir.html">-outdir</a> pathnames to reflect where
you are running mhonarc and where your archive is located,
respectively.
</p>
<p>Note, if your archives are using custom settings of
<a href="resources/mimefilters.html">MIMEFILTERS</a>,
<a href="resources/mimeargs.html">MIMEARGS</a>, and/or
<a href="resources/charsetconverters.html">CHARSETCONVERTERS</a>
resources,
you will need to create a variant version of def-mime.mrc
(included in the examples directory) to include your settings
and use the variant version when updating your archives.
</p>
</li>
</ul>
<hr>
<!--X-NavButtons-Start-->
<table width="100%">
<tr valign="top">
<td align="left"><nobr><a href="intro.html"><img src="prev.gif"border=0 alt="[Prev]"></a> </nobr></td><td align="center" width="99%"><a href="mhonarc.html"><img src="up.gif" border=0 alt="[TOC]"></a><a href="faq/faq.html"><img src="faq.gif" border=0 alt="[FAQ]"></a><a href="app-bugs.html"><img src="bug.gif" border=0 alt="[Bugs]"></a><a href="http://www.mhonarc.org/"><img src="home.gif" border=0 alt="[Home]"></a></td><td align="right"><nobr> <a href="install.html"><img src="next.gif" border=0 alt="[Next]"></a></nobr></td></tr></table>
<!--X-NavButtons-End-->
<!-- *************************************************************** -->
<hr>
<address>
01/11/13 23:07:07<br>
<img align="top" src="monicon.gif" alt="">
<a href="http://www.mhonarc.org/"><strong>MHonArc</strong></a><br>
Copyright © 1997-2001, <a href="http://www.mhonarc.org/~ehood/"
>Earl Hood</a>, <a href="mailto:mhonarc@mhonarc.org"
>mhonarc@mhonarc.org</a><br>
</address>
</BODY>
</HTML>
|
