Hi Bob,  


 BJ> Thanks for documenting the issue.  We'll have to put this on the back 
 BJ> burner till we get a number of other issues resolved. 

np.
understood.

Just so long as it is on a list somewhere, so it doesn't get forgotten.
:)



 BJ> The basics of 
 BJ> squish are now running under Linux.  We still need some major cleanup 
 BJ> of other Maximus source code, and get SqaFix (for areafix capability) 
 BJ> and a tick type processor working.  


And OS/2 versions of same too.  




 BJ> If you can figure out what needs to change in the code, we could 
 BJ> probably integrate it while we work on other things.  There probably 
 BJ> needs to be a config variable added so that Maximus and Squish can 

??
Maximus?

Max is not involved.   Sorry if I somehow led you to this.

As far as I know, any editor could have been used for what I was doing.
I happen to use MsgEd.


 BJ> work together when the sysop wants to send out a file attachment.  
 BJ> I've normally usesd just the fully qualified file name, but I haven't 

Yep..  the fully qualified path and filename are necessary when creating a
file attach netmail.  When I Squish Squash, that FQPath is reduced to just
the filename.ext,  both in the outbound mail packet and in the netmail,
should I go back and re-read it.
In this use of the FQPath, Squish works fine.

 BJ> tried to forward files -- only send them direct to another 
           ^^^^^^^^^^^^^^\and this was where Squish choked, upon finding
the FQPath still in the routed netmail as it passed through.


 BJ> system.....  An yes, normally I end up using Bink or Squish to send 
 BJ> the file direct with out a netmail attached.....

 BJ> Hmmmm.....

:)   Yes, it was a certain set of conditions that produced the result.



 BJ> Thanks for the info and notes.


I hope it is useful to someone.


Thank you


                                                .......Joe

--- Msged/2 TE 05