O>>>> And also PKTs from hpt itself? (which doesn't set the
 O>>>> JAM OADDRESS and rewrites the message date for Squish
 O>>>> messages.

 Ol>> As far as I understand it from the documentation hpt
 Ol>> always does import/export in one pass, is that correct?
 Ol>> But What about echoareas that get rescanned? Around 50%
 Ol>> of the mails (or a little bit less) will have a modified
 Ol>> timestamp (DOS time format with 2 second granularity). To
 Ol>> be clear, Squish message base format has a field for
 Ol>> storing the original FTN time field, it is just not used
 Ol>> by hpt (if I understand the C sources correctly).

 MD> Could you please send me a bug report with full
 MD> description of actions to reproduce the error with an
 MD> example of the message base and pkt taking part in the
 MD> actions. I am very busy at the moment but I'll try to
 MD> investigate it when time permits.

I'm not using hpt and I cannot provide example files, but the problem is
simple:

a squish tosser should write the date string to the __ftsc_date field when
importing mails and should use the __ftsc_date field (if it is not empty) on
export. see the squish spec. smapi seems to support that field, but hpt doesn't
use it.

the JAM problem:
it was mentioned in some other echoarea that hpt doesn't set the OADDRESS for
echomail and that the origin address is missing on rescans. i also couldn't
find a place in the sources where the OADDRESS is set.

jammnntpd even has a workaround for missing OADDRESS fields.

please correct me if i'm wrong. if i had the time, i would do some testing with
hpt.

and thank you for your hpt support and bug fixing, michael.