ml> local time or are you running on UTC time?

 DM> It is local time.  Even so, the date and time on the echomail
 DM> should change  (even if is incorrect) yet they are all the same.

"should change" or "should NOT change"??

 ml> highly unlikely... unless it has a bug and doesn't understand the
 ml> time in the PKTs... are you running anything else on the PKTs before
 ml> squish gets them??

 DM> Nope.

 ml> i have an idea but let's see what the above turns up...

 DM> Let's hear it. :)

it may be that your software isn't recognizing dates in PKTs that are y2k 
buggy... there is still software out there like this... on my system, my 
mailer pulls in the PKTs and mail bundles... mail bundles being those FR1, 
TU3, WE0 archive files with one or more PKTs inside it... my system then uses 
spaz or a similar tool to open the mail bundles and pull out the raw PKTs... 
then we run pktdate on all those PKT files... it will fix the dates for 
tossing and make a backup of the original PKT file as a Y2K file for you to 
study if you want... then i finally let my mail tosser at the PKT files... my 
mail tosser hasn't seen a mail bundle to unarchive in at least 12 years ;)

Y2KTOOL5.ZIP   378994 14-Jan-2000
==============================================
Fido Year 2000 Tools Rel. 5 by Tobias Ernst

PKTDATE  1.4  is a program that can analyse
PKT files for structural errors that result
from year 2000 related bugs in the creating
software and automatically  fix such broken
PKT files.  It is intended for use  at  hub
level in the Fidonet distribution structure
in  order  to  alleviate the effects of the
year 2000 problem  on  the smooth operation
of Fidonet.  Also included  are  a  general
information  text  on the year 2000 problem
in Fidonet,  and  tools  for analysing MSG,
JAM  and   Squish   message   base   files.


)\/(ark

 
* Origin:  (1:3634/12
--- Platinum Xpress/Win/WINServer v3.0pr5
a
 * Origin: LiveWire BBS -=*=- telnet://livewirebbs.com (1:2320/100)

--- WILDMAIL!/WC v4.20a
 * Origin: LiveWire BBS  (1:2320/100.0)