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
|
[Prev] [TOC] [FAQ] [Bugs] [Home] [Next]
---------------------------------------------------------------------------
Release Notes
Read the CHANGES 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 highlighted incompatibilites from earlier releases.
* Compatibility Notes
+ UPGRADING FROM v2.4.x OR EARLIER: DEFRCNAME Change
+ UPGRADING FROM v2.4.x OR EARLIER: HEADER and FOOTER Removed
+ UPGRADING FROM v2.4.x OR EARLIER: MIMEFILTERS API Change
+ UPGRADING FROM v2.1.x OR EARLIER: Database Format Change
+ DOWNGRADING TO OLDER VERSIONS
* General Notes
---------------------------------------------------------------------------
Compatibility Notes
This sections provides notes dealing with compatibility issues if upgrading
from a previous release of MHonArc:
UPGRADING FROM v2.4.x OR EARLIER: DEFRCNAME Change
The default value for the DEFRCNAME is now called ".mhonarc.mrc", or
"mhonarc.mrc" under Windows and VMS. The old value was ".mhonarc.rc", or
"mhonarc.rc". If you use the default resource file, you will need to rename
the file to match the filenames used for v2.5 and later.
UPGRADING FROM v2.4.x OR EARLIER: HEADER and FOOTER Removed
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.
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 IDXPGBEGIN or LISTBEGIN resources can be used to achieve the same
effect of HEADER. The IDXPGEND or LISTEND can be used to achieve the same
effect of FOOTER.
UPGRADING FROM v2.4.x OR EARLIER: MIMEFILTERS API Change
The API for data filters registered via MIMEFILTERS is not capability with
filters written for v2.4.x and earlier. See CHANGES and the documentation
for the MIMEFILTERS resource for the API.
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.
UPGRADING FROM v2.1.x OR EARLIER: Database Format Change
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.
To update your archives, you use the mha-dbedit program using the
def-mime.mrc in the examples directory. For example:
mha-dbedit -rcfile examples/def-mime.mrc \
-outdir /path/to/archive
Make sure that the mhonarc you are using is v2.2, or later. Change the
-rcfile and -outdir pathnames to reflect where you are running mhonarc and
where your archive is located, respectively.
Note, if your archives are using custom settings of MIMEFILTERS, MIMEARGS,
and/or CHARSETCONVERTERS 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.
DOWNGRADING TO OLDER VERSIONS
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.
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:
* 2.0.0
* 2.2.0
* 2.5.0
For example, if an archive was last updated with v2.5.0, processing the
archive with a previous release will cause problems.
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 mha-dbrecover utility contained in the MHonArc version the
archive is being downgraded to.
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.
---------------------------------------------------------------------------
General Notes
* For v2.5, the default text/html filter (mhtxthtml.pl) will now convert
auto-loaded URL attributes to 'javascript:void(0);' for some HTML
elements -- IMG, BODY, IFRAME, FRAME, OBJECT, SCRIPT, INPUT -- except
for cid: URLs. This behavior can be disabled if the 'allownoncidurls'
filter argument is specified.
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.
* ISO-8859 character set data processing now defaults to using the
MHonArc::CharEnt module in v2.5. The old iso8859.pl library is still
provided for compatibility with older archives. To update archives to
use the new settings, you can run the following command,
mha-dbedit -rcfile examples/def-mime.mrc \
-outdir /path/to/archive
where "examples/def-mime.mrc" represents the default MIME processing
resources for MHonArc provided within the MHonArc distribution.
* The value of the TSLICE 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 TSLICE is equal to maximum before and the maximum after range
arguments specifed in the uses of the $TSLICE$ resource variable. For
example, if you have $TSLICE(0;4)$ and $TSLICE(3;3)$ in message layout
resources, you should set TSLICE to 3:4.
If you only use $TSLICE$ once, it is best to set options for thread
slice formatting via the TSLICE resource so you will not have anything
to worry about.
* 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.
* 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, $::OUTDIR is now $mhonarc::OUTDIR.
See the MIMEFILTERS resource page for more information.
* See the warnings in the documentation for the HTMLEXT and MSGPREFIX
resources before using them.
* Occasionally, a new release of MHonArc may contain new MIME filters.
See the CHANGES file to check if any new filters have been added.
If you confirm that new filters have been added, and you want to apply
them to your archives, you use the mha-dbedit program using the
def-mime.mrc in the examples directory. For example:
mha-dbedit -rcfile examples/def-mime.mrc \
-outdir /path/to/archive
Change the -rcfile and -outdir pathnames to reflect where you are
running mhonarc and where your archive is located, respectively.
Note, if your archives are using custom settings of MIMEFILTERS,
MIMEARGS, and/or CHARSETCONVERTERS 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.
---------------------------------------------------------------------------
[Prev] [TOC] [FAQ] [Bugs] [Home] [Next]
---------------------------------------------------------------------------
01/11/13 23:07:07
[monicon] MHonArc
Copyright 1997-2001, Earl Hood, mhonarc@mhonarc.org
|
