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

 ml> yes, it should have stripped it or replaced it with where the file 
 ml> was actually residing... that should be in the same directory that 
 ml> all files are received in to... taking into account, of course, the 
 ml> difference between secure and non-secure inbounds...

With intransit files attached to a netmail, Squish likes to see on the
subject line, just the filename.ext.   If the FQPath is present in the
inbound .pkt, Squish does not alter the subject line upon tossing.  Thus,
the FQPath is there upon packing, and that's when Squish chokes.

It seems that the  inbound  dir is assumed, when working with just the filename.ext.

Fwiw, for a locally created outgoing netmail, w/file attached, of course
the sender must put the FQPath on the subject line.  Upon packing it out
however, Squish changes that subjext line to just the filename.ext.  Also,
in the outbound .pkt created by Squish, there is not the FQPath on the
subject line.
Thus, whomever it is going to, will get only a filename.ext on the subject
line.  If they wish to allow it to pass through, it is ready to go. :)


                                                .....Joe

--- Msged/2 TE 05