Hello David!
-> The macro .start.ncftp runs every time you start NcFTP, the macro
-> .quit.ncftp runs every time you quit NcFTP, any macro of the form
-> .open.{site} will execute whenever you open a session with that
-> {site}. This info was found in a few seconds of scanning in the
-> NcFTP.INF file that shipped with ver 2.3.0.
Don't get mad with me, as I told you I'm very new to OS/2. :)
I did several scans to the .INF file looking for other keywords: script,
automatic, auto-start, etc and as I didn't find what I was looking for I
thought that it didn't have it. Now looking for 'macro' I found the
information that you showed me and that I need it. Right now I'm
downloading the emx's run time libraries that are need it to execute it.
BTW, also looking deeply in the OS/2 help files I found a way to
auto-start macros with the FTP client that comes bundled, you have to
call the auto-start macro as init. It's working well for what I want.
The only problem that I've found so far is that if you try to connect
to a site that is down for some reason the program returns to the FTP
command prompt instead of returning to OS/2. So, in these situations
you could find your computer just sitting there waiting for your
intervention.
Have you used NcFTP? What are the main advantages that I would have by
using it, compare it with the FTP client that comes with OS/2?
-> Lastly, a very basic but often overlooked tool is piping and
-> redirection. Type all the commands you want into a text file and then
-> invoke the FTP client like so:
->
-> NcFTP {command line stuff here} < script.file
I tried this with the OS/2 FTP client and it didn't work well, at some
points, like waiting for the transfers, some entries in the script were
sent out of the command prompts.
-> OK... in that case explain why FiFTP won't do what you need and I
-> will work with Mike and the other Alpha team members to find out what
-> can be done to fix it or get it to do what you need.
With Fido works well as I told you, but not in other networks like in
RIME, where the packages that have the public mail have to be downloaded
by all the nodes, so we don't have to delete them after the downloads.
Also the private packages and the packages that you sent are kept for
all nodes in one directory, that is were you upload your public/private
mail and download just your private mail, you have to download just the
ones that are for you and in this case delete them.
-> Don't know... I haven't used Sendmail in over 2 years since switching
-> to GIGO for all my mail. My information doesn't mention a -a
-> paramater. My information is from a search of sendmail after hitting
-> F1 at my 4os2 prompt. -af according to my docs says include the
-> following file. There is also a param to have sendmail attempt to get
-> the address info from the file itself. Personnally. I much prefer
-> sending all my outbound to my ISPs SMTP system for delivery. They can
-> handle the complexity of every addressing system much better than I
-> can. All I need to do is make sure what I send the SMTP system is
-> understandable and it either delivers or returns it.
Well in Warp 4 there is no reference to an -af parameter, I'm using the
-a and is doing the job. What I do with sendmail is something similar to
what you do, my SMTP server (I'm an ISP) is the one that really delivers
the mail, I've made the changes in the sendmail.cf file to route all the
outgoing mail to my server. It's working very well.
Thanks again for all your help.
Greetings,
@X00@X0E
Adolfo Justiniano º Santa Cruz, BOLIVIA º Santa Cruz BBS: +591 3 37-1133
 Fidonet: 4:823/1 º   RIME: SANTACRUZ   º e-mail: sysop@scbbs-bo.com@XFF
--- PCBoard (R) v15.3 (OS/2) 25
---------------