Subj : Problems
To : Bill Gordon
From : mark lewis
Date : Tue Feb 10 2004 02:06 am
BG>>> Anyone familiar with this problem?
>> can't say that i am... i run mine another way... i tell
>> binkd to create a semaphore file when inbound mail is
>> received... then i have a cron program fire up a .bat
>> file that looks for the semaphore... if its there, do the
>> toss stuff... if not, exit the bat and wait till next
>> round...
>> much easier and simpler...
BG> Sounds like a better idea. Care to share the bat file and go
BG> into greater detail about the semaphore file creation?
that's all on one line... it'll create the semaphore file (mail-in.sem) if it
receives any of those extensions...
the .bat file... hummm... how about something similar? what i have is rather
large and intricate do to the way i process everything...
@echo off
os2title in.bat start
:top
if exist %fdsema\tossing.sem goto end
if exist %fdsema\fdinsess.* goto end
if exist %fdsema\maint.sem goto end
if exist %fdsema\scanning.sem goto end
rem>%fdsema\fdnoscan.now
rem>%fdsema\tossing.sem
os2title in.bat 10sec
wait 10
echo.
echo Tossing INBOUND Mail...
rem *************************
rem ** i spawn "fastech2 afix" for areafix messages
rem ** i generate a new areas.bbs file with "fesetup -XA"
rem ** i use SPAZ to pull out the PKTs from the bundles
rem ** i check the PKTs for y2k complient message dates and fix bad ones
rem ** any other PKT scans like GMD or NOBOGUS can be run here
rem ** now i spawn "fastech2 toss -B -C"
if errorlevel 11 rem>%fdsema\dolink.sem
rem ** NETMGR gets a run
rem ** OTTRACK gets a run
rem ** i spawn "feutil2 import" to import netmail into the bbs
if not exist %fdsems\dolink.sem goto feh
rem ** i spawn "feutil2 link -force"
rem ** gather some stats
rem ** update timed's config with any new message areas
del %fdsema\dolink.sem
:feh
del %fdsema\tossing.sem
:end
yes, there's a lot of "fd" in there... why? because i've integrated binkd into
my existing FrontDoor setup... its not pretty but it is functional and works
for what i need... somewhere up there, i check if there are any TIC files and
if so, i fire up allfix to handle that stuff...
the "spawn" sections are due to the .bat file running in a DOS task and firing
up native OS/2 flavors of the utils...
yes, its not windows but the idea process is still the same -=B-)
