Hello Oli!

03 Feb 21, Oli wrote to Kai Richter:

 O>   The  XMSG  structure  has  the following format:

Thanks, you found the XMSG definition i was looking for.

 KR>> I don't doubt that the problem exist but for fault confirmation
 KR>> and trouble shooting it is easier to know the software in use.

 O> hpt does it wrong. I tested it. What else is there to trouble shoot?

The other side of the medal. As said i'm no coder and my search for hpt found this one:

https://github.com/huskyproject/hpt/search?q=__ftsc_date&type=

 src/scan.c
96    msg->destAddr.point = xmsg.dest.point;
97    strcpy((char *)msg->datetime, (char *)xmsg.__ftsc_date);
98    xstrcat(&(msg->subjectLine), (char *)xmsg.subj);

This looks like the xmsg.* is the squish base message.
It looks like the ftsc date is overwritten by some copy -> wrong, i'm no coder.

https://www.cplusplus.com/reference/cstring/strcpy/

char * strcpy ( char * destination, const char * source );

Unlike usual copy the C++ strcpy works reversed, the scan.c of hpt get the original squish base ftsc data and uses it for the datetime field.

 O> It's just a simple bug ...

If it is it would be fixed already.
You reported this one a year ago, don't you?

My knowledge does end here. It was interesting but i can't help you further.

 O> It only affects systems that use a Squish database and have downlinks
 O> that do a %RESCAN.

And it does apply to mails without msgid only. Good luck.

Regards

Kai

--- GoldED+/LNX 1.1.4.7