| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | dates |
Tue 2002-11-19 03:13, andrew clarke (3:633/267) wrote to All:
> Wed 2028-05-10 13:27, andrew clarke (3:633/267) wrote to All:
>> After a lot of work, my modifications to the SMAPI are progressing.
> Erm, I'm not sure what caused the date to appear as 2028-05-10! Looks
> like I may have messed up something. ;-)
OK, this one has me really confused. Somehow HPT tossed a message into my
netmail folder and the FTSC date ended up as "11 May 28
21:36:30":
Dump of SQXMSG structure
attr : 00020005h (131077)
orig_user : "Peter Knapper"
orig_addr : 3:772/1.10
dest_user : "Andrew Clarke"
dest_addr : 3:633/267.0
subject : "nlmaint"
date/time writ : 60ABh AC8Fh (1900-04-11 21:36:30)
date/time ariv : 60ACh 112Eh (1900-04-12 02:09:28)
utc_ofs : 0
replyto : 207
see : 0 0 0 0 0 0 0 0 0
umsgid : 218
ftsc_date : "11 May 28 21:36:30"
I happen to keet PKTs, and the FTSC date in the PKT is normal, so I think
HPT is dirty playing tricks on me! So I retossed the packet:
Dump of SQXMSG structure
attr : 00020005h (131077)
orig_user : "Peter Knapper"
orig_addr : 3:772/1.10
dest_user : "Andrew Clarke"
dest_addr : 3:633/267.0
subject : "nlmaint"
date/time writ : 2D72h 9C39h (2002-10-18 19:33:50)
date/time ariv : 2D73h 1F5Ah (2002-10-19 03:58:52)
utc_ofs : 0
replyto : 207
see : 0 0 0 0 0 0 0 0 0
umsgid : 223
ftsc_date : "18 Nov 02 19:33:50"
So whatever happened, I can't reproduce it!
This is using hpt 1.3.0/w32 11-11-02.
Would there be anything in Msged (or the SMAPI?) that would cause it to
modify existing messages just by reading them (I hope not!) ?
Regards
Andrew
-- mail{at}ozzmosis.com
--- Msged/NT 6.1.1
* Origin: Blizzard of Ozz, Mt Eliza, Victoria, Australia (3:633/267)SEEN-BY: 633/270 @PATH: 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.