home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 25 Icons
/
25-Icons.zip
/
yodomain.zip
/
yodomain.doc
< prev
Wrap
Text File
|
1999-10-20
|
3KB
|
72 lines
OS/2 Domain-POP Client Setup
I am collecting the pieces of code that I used for two years
to provide me with mail service for my domain -- dashs.denver.co.us.
This was an OS/2 setup using InJoy as a dialer (using its Dial-on-Demand
feature). My InterNet Provider is prescient enough to allow me
two MX records, one of higher priority for my static IP address,
and another which deposits all mail for my domain into a POP3 box.
These days I have Linux server that performs the collection and
distribution function. However, it can be done with a single OS/2
system.
The parts:
(1) your favorite scheduler or rexx script to invoke
(2) my modified souper.exe POP client at intervals or
(3) OS/2 SENDMAIL 2.02 to handle direct SMTP connection while online
(4) and deliver.exe to handle local delivery in both cases.
You will need to acquire the OS/2 SENDMAIL 2.02 which you should
already have, or be able to acquire easily.
Included is a template (SENDMAIL.CF0) for the SENDMAIL.CF control
file. Remember, when editing this, file - use the 'E' editor or
one that preserves tabs a la UNIX.
The SENDMAIL elements originated with Niel Kempson (kempson@snowyowl.co.uk),
as well as the original deliver.exe.
SENDMAIL should be started in daemon mode when you make your first
InterNet connect after bootup.
It may be detached and a sample command 'sendem.cmd' is included.
My setup makes copious use of Albert Shan's Super Virtual Disk package
to obtain performance. You may, of course direct files to actual
hard-disk directories and your mileage will certainly vary.
Once your ISP has setup the MX records and Domain POP box, and you
are running SENDMAIL with you domain info in the SENDMAIL.CF file
you are now ready to configure the mail-polling portion of the setup.
See the included souper.doc for information on the normal souper.exe if
you need to know more.
My modifications are documented here.
To cause souper.exe to invoke deliver.exe for local delivery,
specify '-D' on the command line.
To download and distribute mail according to specification in
the deliver.cfg file, set the DELIVER_CFG environment variable
(at least in the process shell that is downloading mail).
In your REXX script:
del_cfg = value("DELIVER_CFG", "deliver.exe -c h:\deliver.cfg -l e:\uupc\spool\dmail.log -f $f -v $u $s", "OS2ENVIRONMENT")
This variable is inspected by souper.exe when the '-D' option is given,
to indicate how to invoke deliver.exe.
For -c use the path to your deliver.cfg file (see deliver.txt for details).
For -l point to your log file for mail delivery
The other options indicate replacement strings for deliver.exe.
See my sample deliver.cfg.
The executables have been compiled with the old IBM C/SET++ compiler.
On my system, they were linked with dynamic runtime (DLL) support and
were small enough to fit on a RAM disk. For distribution, they are
statically linked and quite a bit larger. If you have that ancient
compiler and its DLLs, rename and use the .bin versions of souper
and deliver.