Subj : Forward File routing To : Mike Tripp From : Joe Davis Date : Wed Jul 23 2003 02:03 pm [...] MT> "ForwardFrom File " was the only statement required to MT> support my scenario. MT> It might be worthwhile to test again without the "ROUTE File" in the MT> mix and see if your ?LO entry looks straight in the original ?LO MT> before being shuffled over to another by a routing command. And, of MT> course, verify that the file is actually still in your inbound and MT> not shuffled off elsewhere or deleted by other processing logic. [...] Commented out route hold file x:xxx/xxx in route.cfg for all the below First test: Used ForwardTo File x:xxx/xxx as the only "Forward" type command in Squish.cfg. Result Squish logged: ! 23 Jul 13:10:14 SQSH File attach `D:\BT\In\I' does not exist! in \out dir found: compressed mail pkt for node - looked normal ..hlo file to send that pkt - looked normal another .hlo file to send file attach - text inside : D:\BT\In\I Which appears to begin with a valid referance to my inbound dir of D:\BT\In and appears to begin to append the orginal senders path of I:\xxxNET\ which is in his netmail file attach that was routed through my system. === Second Test: commented out ForwardTo File command from previous test Used ForwardFrom File x:xxx/xxx as the only Forward command in Squish.cfg Result: Same as above ==== Third test commented out ForwardFrom File from second test Restored ForwardTo File x:xxx/xxxx command Restored ForwardTo World command, as this is necessary for normal netmail routing service. After squash, Result: in \out dir found normal compressed pkt containing the netmail found .hlo file to send the netmail - looked normal found nothing else. attached file was ignored. Same for Squish log Interesting, eh? :) Curiosity question: Squish does process Squish.cfg from the beginning to the end, correct? Note that they were in this order for that third test. ForwardTo File x:xxx/xxx ForwardTo World Thanks .....Joe --- Msged/2 TE 05 * Origin: Cairdeas (1:261/1380) .