On August 20, 1998 at 17:21, J C Lawrence wrote:
> Okay, perhaps I'm being dense here. Are you saying that MHonArc will
> read the contents of previously generated mail*html files for MSG ID
> strings to do reference threading?
Sort of, but not the way you think.
> Surely MHonArc checks the MSG ID
> strings found in incoming message bodies against its DB of MSG ID's,
> and since both are unmunged (the original message source and the DB)
> such reference threading works correctly. The munging then affects
> only the post-MHonArc generated HTML files -- something that MHonArc
> pays no attention to from there on out in its operations.
Yes on first sentence. No on second. If MHonArc tags a message for
updating (ie. an existing message page must be updated due to an
add), it will scan for message-ids in the page and check them against
the new message-ids that came in. If there is a match, MHonArc
makes the message-id a link.
> On cursory search I don't see evidence of MHonArc searching previously
> generated mail*.html files for MSG ID tags to map to MSG ID's found in
> messages being archived...or am I missing something?
You missed something. If you look at the output_mail() function,
here are the lines (not necessarily together) that do the search:
$tmp2 =~ s%($AddrExp)%&link_refmsgid($1,1)%geo;
$MsgHead{$index} =~ s%($AddrExp)%&link_refmsgid($1)%geo;
$Message{$index} =~ s%($AddrExp)%&link_refmsgid($1)%geo;
Take a look at
<URL:http://www.oac.uci.edu/indiv/ehood/mhaeg/msg00052.html> as
an example. See how the message-ids listed in the References: in
the message header are links.
--ewh
----
Earl Hood | University of California: Irvine
[EMAIL PROTECTED] | Electronic Loiterer
http://www.oac.uci.edu/indiv/ehood/ | Dabbler of SGML/WWW/Perl/MIME
