TIP: Click on subject to list as thread! ANSI
echo: tub
to: Alan Ianson
from: Joe Davis
date: 2003-07-30 14:41:50
subject: Forward File routing

Hi Alan,


[...]

 AI> Sure, fire away..

 JD>> From your statement above it appears that you and the 
 JD>> other two nodes involved all communicated via direct 
 JD>> POTS polling.  True?

 AI> Yes, mind you that was 6 - 8 years ago now.. :))

Ancient history, huh?   :)


 JD>> Is your system FD style or Bink Style?   and while we 
 JD>> are on that,  what was your frontend software then?

 AI> Bink style. I was either using the original BinkleyTerm or
 AI> Portal of Power (Binkley style outbound) in those days.

ok


 JD>> Here's one that may be difficult to get into postion to 
 JD>> answer:   When a netmail with a file attached is sent 
 JD>> to your system, upon tossing it, and reading the 
 JD>> netmail,  exactly what appears in the subject line?
 JD>> Just the filename.ext? or a fully qualified path+filename.ext  ?

 AI> Just a filename.ext, at least that's what we hope for.

:) more on this later.


 AI>  I have
 AI> noticed at times when I get a file attach from a dynamic mailer
 AI> like FD or IM I get the fully qualified path from the senders
 AI> system. 

Are you sure?
I ask because I set up... enough to write a netmail and send it to
myself... an old copy of FD.  v2.12 it is.

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

Return to FD.

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

InspectA reads the .pkt fine ....  on the subject line is just the
filename.ext of the attached file!  the FQPath is gone.  

The other file, I don't know what it is, but I suspect it has to do with
the actual sending of the file attach,  does contain the FQPath... I can
see it in there with List.

Using FD, I sent that to myself.    No FQPath on the subject line upon
tossing the netmail.


I do have an idea to propose though, as to how and why you may have been
fooled into thinking it was FD that did it.   


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



 AI>  That might create a problem if you want to forward the
 AI> attached file on to another node. 

    Bingo!   :)


 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..

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


 AI> Might have to experiment a bit in that case and see what happens.

I did.
a bunch.

See another echomail message. 


Thanks




                                                ......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™.