Misleading "received" date is shown in messages instead of date "sent" -
more seriously misleading when old messages with seriously wrong dates
are bounced to add them to list as recommended in FAQ.
Looks to me like there could be a quick fix from your end to problem we
are currently having trying to figure out a work around to this
(explained in previous email not copied to gossip list).
Sorry I cannot supply a tested patch as we don't have anything
installed.
Could the following change in "mailme" work?
If so, as well as solving our urgent problem for adding old messages I
believe it could enhance user friendliness of browsing by making date
sequences more coherent than the random variations resulting from mail
propagation delays (e.g. replies should ALWAYS come after messages
replied to, both in date indexes and within subject threads).
From:
FLAGS="$FLAGS -idxsize 300 -multipg -add -nomailto"
To:
FLAGS="$FLAGS -idxsize 300 -multipg -add -nomailto"
FLAGS="$FLAGS -datefields date:receieved"
Or else the equivalent "rcfile" entry added as specified below (not sure
where it goes though):
<DateFields>
date:received
</DateFields>
(To replace the default sequence "received:date" which causes the date
the message was "received" to be used when found in the message whereas
the less "accurate" but more user friendly behaviour is to use the
"date" the message was sent first and only use "received" when "date" is
not present - especially but not only to take into account addition of
old messages).
As far as I can see this would carry through to the displayed date
$MMDDYYYY$
as specified in "rcfile" and there isn't any easy way to just display
the (sent) "date" value instead of the "received" value, without also
making it affect the indexing as (hopefully) achieved above.
(Caveat I still haven't read docs thoroughly let alone installed or
looked at code)
***
Found following in MHonArc2.3.3/CHANGES
Enhancements/Changes
--------------------
o Added DATEFIELDS resource. The resource allows the user to
specify the fields (and order) that are checked when
MHonArc extracts the date of a message.
Following in MHonArc2.3.3/doc/resources/datefields.html
DATEFIELDS
Syntax
Envariable
M2H_DATEFIELDS=field1:field2:...:fieldN
Element
<DATEFIELDS>
field1:field2:...:fieldN
</DATEFIELDS>
Command-line Option
-datefields field1:field2:...:fieldN
Description
DATEFIELDS specify the message header fields MHonArc will search to
determine the dates of messages. Each field will be checked in the
ordered specified.
The value of the DATEFIELDS is a colon separated list of message header
fields to check.
Default Setting
received:date
Resource Variables
N/A
Examples
By default. MHonArc looks at the Received fields of a message to
determine a message's date. This tends to be more accurate as it tells
when the message was actually received. However, you may want to have
the date based upon the time the sender composed the message. The Date
field usually reflects the composition date. Therefore, the following
setting can be used:
<DateFields>
date:received
</DateFields>
***
