Subj : File attached routed netmail To : All From : Joe Davis Date : Wed Jul 30 2003 04:06 pm Hello, Recently I asked for help with a problem that I have, with Squish not being able to properly handle a routed netmail passing through and allowing a file attach to go with it. Thank you each for your replies and help. Bo and Bob and others: I doubt that it is a bug in Squish now. There is perhaps room for an enhancement though. :) I'd like to share what I've learned. I was experimenting with Squish.cfg, having saved a few old .pkt files from my earlier attempts to get Squish to do it. Using a copy of the old .pkt file, and its associated attached file, I would Squish IN. Here's the catch: I didn't know that seeing the fully qualified path on the subject line was not "normal". That's what I was used to seeing. The FQPath was still there on the subject line. Next, Squish out would produce the failed results that I reported earlier. The problem was not Squish, but that the FQPath was still in the netmail .pkt when it arrived on my system. I did some more rooting around, with a shareware copy of FD. It did not create nor deliver .pkts with a FQPath in the ..pkt. On the next test, a netmail wil file attached was sent througy my system, from a Bink system, using Squish. This time there was only the filename.ext in the ..pkt before tossing. Netmail w/file attached delivered to my system passed both the netmail and the attached file just fine. Two other sysops participated in that experiment. One sent, one received, and my system was in the middle. Here is one way that a netmail .pkt can arrive, with the FQPath still in it: the netmail was sent by Irex in FD mode. I believe this to be the snag. Netmail w/file attached sent by Irex, from a Bink style system has its netmail packed out by the tosser/scanner/packer software. For example, I use Squish in a Bink setup. Attaching a file and packing out a netmail, I looked at the newly created .pkt. No FQPath in it. :) In a system using Irex in FD mode, there is no packing, and FD itself does not get to send the netmail ( in my test FD had a .pkt waiting and another file with the FQPath in it). Apparently Irex comes along and scans the *.msg directory, sends unsent netmail, with any file attaches. It looks like Irex does not change the subject line before sending. I hope I've explained this clearly, so that should anyone else encounter this, that maybe they will save some time. To those of you whose time I may have wasted, thank you for your patience. I had no idea that seeing the FQPath on the subject line was to be questioned. To Mike Tripp: Thank you for the huge investment in time you have made, along with the long distance polling. To Dave Nemeth: thanks for being our 'receiver' on the testing. .....Joe --- Msged/2 TE 05 * Origin: Cairdeas (1:261/1380) .