Hi Oliver,

On 2019-11-21 20:56:36, you wrote to me:

 WV>> There's also the problem that the squish message base stores
 WV>> date/time stamps with a resolution of 2 seconds. That has been
 WV>> causing problems in the past where a squish system forwarded messages
 WV>> to its other links with the date/times changed from the original, and
 WV>> so causing undetected dupes on some systems.

 OT> This might be a problem with some tossers, but it's not a problem with the
 OT> Squish specification itself. It would surprise me, if Squish didn't use
the
 OT> original date for rescanned messages.

 OT> Quote from the Squish Developers Kit Version 2.00:

 OT>   __ftsc_date    char[20]  218  FTS-0001  compatible date.   Squish
 OT>                                 applications should not access this
 OT>                                 field directly.  This field is used
 OT>                                 exclusively by tossers and scanners
 OT>                                 for  preserving the  original ASCII
 OT>                                 message date.   Squish applications
 OT>                                 should  use  the  binary  dates  in
 OT>                                 date_written  and  date_arrived  to
 OT>                                 retrieve the message date.

Looks good (if it's used when forwarding mail).

 OT> I suspect hpt from the husky project. In scanarea.c, function makeMsg:

 OT>   sc_time((union stamp_combo *) &(xmsg.date_written), (char
 OT> *)msg->datetime)

I don't remember what tosser the guilty system used, when we found out...

 WV>> This is of course only a problem if you have more than 1 link to an
 WV>> echomail area. Which is never (or shouldn't) be the case for a point
 WV>> system. ;)

 OT> I'm a node in the othernet ;)

Are you a "leaf" node, or do you have multiple links?

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815