Here's what I have:

flag /home/imp/bink/toss.now [0-9a-Z][0-9a-Z][0-9a-Z][0-9a-Z][0-9a-Z][0-9a-Z][0-9a-Z][0-9a-Z].???
exec "/home/imp/imp/impmail.sh /home/imp/hpt/secure" /home/imp/hpt/secure/*.[STFWMstfWM][ouaherOUAHER][0-9A-ZA-a] *.[pP][kK][tT]

Thanks,
ignatius
--- SBBSecho 3.00-Linux
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

On 2017 Mar 09 05:50:08, you wrote to All:

Here's what I have:

flag /home/imp/bink/toss.now [0-9a-Z][0-9a-Z][0-9a-Z][0-9a-Z][0-9a-Z][0-9a-Z][0-9a-Z][0-9a-Z].???
exec "/home/imp/imp/impmail.sh /home/imp/hpt/secure" /home/imp/hpt/secure/*.[STFWMstfWM][ouaherOUAHER][0-9A-ZA-a]

*.[pP][kK][tT]

you're doing it twice... choose one or the other for your tossing... either use
a semaphore to signal the toss needs to be done at some point in time OR execute the toss script directly... one or the other...

FWIW: the regexes i gave are much easier to read and understand ;)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Be very afraid: The people fixing Iraq are going to fix Social Security. ---
* Origin: (1:3634/12.73)

Re: binkd.conf
By: mark lewis to j b l on Thu Mar 09 2017 10:25 am

you're doing it twice... choose one or the other for your tossing... either use a semaphore to signal the toss needs to be done at some point in time OR execute the toss script directly... one or the other...

If I go the semaphore route, how will it know when to use the tosser/scanner? It isn't defined in the "flag" line..

Thanks,
ignatius
--- SBBSecho 3.00-Linux
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Hello j b l,

you're doing it twice... choose one or the other for your tossing...
either use a semaphore to signal the toss needs to be done at some point
in time OR execute the toss script directly... one or the other...

If I go the semaphore route, how will it know when to use the tosser/scanner? It isn't defined in the "flag" line..

If you go the flag route it would up to the mail tosser to monitor either the existence of or the time stamp of the flag file then run the tosser.

If you go the exec route then upon BinkD session termination BinkD would call the tosser either by command line execution or by calling a bash script file which would run the tosser.

I use the exec option with the pertinent BinkD line being:

exec "/home/bbbs/mailin.sh" *.su? *.mo? *.tu? *.we? *.th? *.fr? *.sa? *.tic *.pkt

Which calls the "mailin.sh" bash file run the tosser upon the existence of files with any of the specified extensions. The mailin.sh bash file might be:

-------------------------------------
#!/bin/sh
cd /home/bbbs

# incoming fido mail or tics
./bbbs bogus w > /dev/null 2>&1
./bbbs btick > /dev/null 2>&1

# outgoing fido mail
./bbbs bogus r > /dev/null 2>&1

# notify node 1 to rescan outbound
touch work/rescan.1
#
./bbbs bogus f upd.log &
#
# Make New file Announcements of any newly received files.
./bbbs btxt2bbs New File Announcements /home/bbbs/work/tickinfo.txt /F SysOp /T
All /S New File Announcement
#
exit
------------------------------------

The above bash file is for running BBBS's mail tosser and doing other tasks. Your bash file would be of course tailored to your particular tosser. It should be noted that BBBS has it's own BinkD capabilities and I use BinkD separately only when needed.


Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: The OuijaBoard - Anoka, MN (1:282/1031)

On 2017 Mar 09 20:59:46, you wrote to me:

you're doing it twice... choose one or the other for your tossing...
either use a semaphore to signal the toss needs to be done at some
point in time OR execute the toss script directly... one or the
other...

If I go the semaphore route, how will it know when to use the tosser/scanner? It isn't defined in the "flag" line..

binkd doesn't care... it doesn't need to know for a simple disk-based flag file
(aka semaphore)... all it does is create the file... that other process i spoke
of that would handle your tossing would need to know, though... it would be a stand-alone looping script or a single-shot one fired by cron every so often...

if you already have a script to toss inbound mail, you could easily let cron fire it off and have it look for the mail-in.sem before thinking about doing any work... it should create its own semaphore (eg: tossing.sem) so that it won't run more than once at a time... this would be your single-shot script i mentioned before... using the methods i demonstrated in that sample script the other day...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Now I definitely crave a pork product of some kind.
---
* Origin: (1:3634/12.73)