TIP: Click on subject to list as thread! ANSI
echo: tub
to: Alan Ianson
from: Joe Davis
date: 2003-07-31 02:16:40
subject: Forward File routing

Hi Alan,  :)

 JD>> It behaved like this:
 JD>> Write a netmail w/ a file attached, and save with FM, the editor that
 JD>> comes with FD.

 JD>> Return to FD.

 JD>> FD immediately 'senses' that a new *.msg was created and in another 
 JD>> di creates two files, one with .ext = .pkt  and the other with .ext = 
 JD>> .fd

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

Could be.

However, and remember I used an old shareware copy of FD2.12,   it did
behave that way when I tested.

Let me rephrase my first quoted sentence above. :)

 It behaved like this:
 Write a netmail w/ a file attached ( using a FQPath), and save with FM,
the  editor that comes with FD.

IOW, I too used a FQPath in FM, and immediately upon restarting FD found
that the newly created .pkt did not have the FQPath in it.  The other file
did.

FD therefore is designed to not send out the FQPath.

Just the same, for example, as Squish in a Bink setup does.

This is leading me to believe that the "normal" way is for the
sender's system to remove the FQPath.


 AI>  But I don't have anyone sending me messages with 
 AI> either anymore so my memory may be fooling with me a bit too.. ;)

 JD>> IM... I couldn't get it to find my other modem, and I'd found out 
 JD>> what I wanted to find out with FD.   I would like to find time to see 
 JD>> just what IM and its editor really produce too.   I wonder if it is 
 JD>> the sam or different results from FD....

 AI> IM is very much like FD, it uses a lot of the same filenames like 
 AI> route.fd, fdnode.ctl and more like that. I never did use IM a lot 
 AI> though, I've always prefered the look & feel of FD.

 AI >>I'm not sure if squish would
 AI>> be able to find the file and send it on it's way or not in a
 AI>> case like that..

 JD>> Squish does not, if the FQPath is on the subject line.
 JD>> Qualification:  Squish does fine with it, if the local bit is set, 
 JD>> and the path is real.

 AI> The dynamic mailers need to have the path somewhere since they don't 
 AI> have a static control file like BSO mailers. It would be a plus if 
 AI> Squish would just use the filename.ext if the FQP is on the subject 

referring  specifically to routed netmail passing through, w/file attached.
right?
( in case somebody comes along reading this, and hasn't been following the
thread.  :)  )


 AI> line. Of coarse that's easy for me to suggest.. it may not be as easy 
 AI> to impliment and makes squish more and more complicated..

That was one reason I wanted to pin down just what was going on - to
register a request for an improvement, if need be.

The other reason was to share whatever I learned with others.  Bet'cha next
time that somebody pops up with this happening to them, somebody in here
will remember enough to explain it.   :)


                                        ....Joe

--- Msged/2 TE 05
* Origin: Cairdeas (1:261/1380)
SEEN-BY: 633/267 270
@PATH: 261/1380 10/3 106/2000 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.