ml> FDNODE.CTL is pretty static as is the inbound directory where all 
 ml> files (mail and otherwise) end up before tossing... when FD receives 
 ml> a message with a fileattach and it is set up to allow that message 
 ml> and file to travel on to another system, it knows to look in the 
 ml> inbound directory for the file to send on... this works fine if FD is 
 ml> doing all the routing handling and as long as there are no duplicate 
 ml> files received which would cause FD to adjust the extension of the 


Duplicate files received.
Interesting...

I hadn't thought to try that with Squish.


 ml> additional files... in the case of a netmail message that is carbon 
 ml> copied to multiple systems with a file attach that arrives on the FD 
 ml> system for forwarding to two or more system, IIRC, FD doesn't remove 
 ml> the file until after the last message referencing it is sent...

[...]
 ml> mind you, i'm speaking from the point of FD being an internediate 
 ml> system in the routing... not the originating or destination system...

--- Msged/2 TE 05