AI> I'm pretty sure I've seen fully qualified paths from messages
 AI> from FD/IM. It could be that the person who sent it used a FQP
 AI> when they wrote the message??

those are/were old versions of FD... newer versions do not leave the path
in the subject line... at least, not from what i remember...

[trim]

 AI> The dynamic mailers need to have the path somewhere since they
 AI> don't have a static control file like BSO mailers.

FDNODE.CTL is pretty static as is the inbound directory where all files
(mail and otherwise) end up before tossing... when FD receives a message
with a fileattach and it is set up to allow that message and file to travel
on to another system, it knows to look in the inbound directory for the
file to send on... this works fine if FD is doing all the routing handling
and as long as there are no duplicate files received which would cause FD
to adjust the extension of the additional files... in the case of a netmail
message that is carbon copied to multiple systems with a file attach that
arrives on the FD system for forwarding to two or more system, IIRC, FD
doesn't remove the file until after the last message referencing it is
sent...

 AI> It would be
 AI> a plus if Squish would just use the filename.ext if the FQP is
 AI> on the subject line. Of coarse that's easy for me to suggest..
 AI> it may not be as easy to impliment and makes squish more and
 AI> more complicated..

the best thing would be for something to strip the path out... i don't
recall if FD does this or not...

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

)\/(ark
member, FD BETA Team