-=> Quoting Jean Parrot to 2bruce Clark <=-

 BC> That was probably me: 
 
 JP> See tailer !  ;-)))))

 JP> ___ Blue Wave/DOS v2.30

Slowly getting there. 

Until you get the BWREPFIX working properly, manually change "2bruce" 
to "Bruce" in the To: field. 

You'll have to do that on every reply, no matter what the name, until 
the BWREPFIX is installed properly. 

From the BWREPFIX.DOC: 

  There are three types of errors in messages that have been observed so
  far with the BlueWave Y2K QWK Reply problem.   On the initial creation
  of a message, BlueWave will output the value of YEAR-1900 into a two
  digit field.  Since this will be a three digit number after 1 January
  2000, it causes most of the rest of the header record to be skewed to
  the right by one character.  This effects the date, the time, the TO:
  field and other subsequent fields.  A second type of error is that
  whenever BlueWave version 2.30 reads a reply message with a date that
  it thinks is out of bounds (which would be any date with a two digit
  year less than 70), it replaces the date and time fields with 01-01-70
  and 00:00 respectively.  It then seems to manage to insert the correct
  thing into all other fields except for the TO: field.  That field may
  have a leading digit which is a left over effect from when the time
  field was slid on the previous mangling of the message header by
  BlueWave.   The third type of error is observed with BlueWave version
  2.12.  When BW 2.12 opens a .REP packet which has dates with years of
  00 and beyond, it gets very confused and converts those dates to
  erroneous month/day/year figures, possibly negative.  Because of this,
  a parameter "-c" has been introduced which allows the forcing of dates
  to be current (within 45 days).


What you are experiencing is the second type of error. 

Bruce Clark 

 
___ Blue Wave/386 v2.30
--- Platinum Xpress/Win/WINServer v3.0pr5a