On 16 Sep 2024, Shurato said the following...
What mailer and frontend do people use who have bbs software withoutit
built-in? Right now I'm running fastecho and irex, but it's startedto
not send routed netmail. I'd like some alternatives, but I don'tknow
what all is available. I'm hoping binkd and fmail, but I don't knowfor
sure.
I've used both FastEcho & hpt with binkd on my Telegard setup. Both work well with binkd.
You can find Windows binaries for binkd here:
http://download.binkd.org/win/
Look for the files beginning with: binkd11a115-
Find one that will work for the version of Windows you're running it on. I'm using the msvc10-4gb one with my Win 10 32bit install.
Here's the binkd config I'm using with my Telegard setup:
https://nrbbs.net/binkd.txt
I looked at that and couldn't figure out what directory on my end
would equate with your echomail directories. the fbox directories
were clear, but I don't have fileboxes with most of my networks, so
I don't know what to put in case there isn't a directory. This is confusing.
On Thu, Sep 26 18:31:00 -0500, you wrote:
I looked at that and couldn't figure out what directory on my end
would equate with your echomail directories. the fbox directories
were clear, but I don't have fileboxes with most of my networks, so I don't know what to put in case there isn't a directory. This is confusing.
Try nothing.
I don't think the fbox/mbox whatever directories need anything when they're not used. However, if you were to skip something like the 'password' field you would have to put a single dash "-" in it's place.
I looked at that and couldn't figure out what directory on my end would equate with your echomail directories. the fbox directories were clear, but I don't have fileboxes with most of my networks, so I don't know
what to put in case there isn't a directory. This is confusing.
Try nothing.
I don't think the fbox/mbox whatever directories need anything
when they're not used. However, if you were to skip something
like the 'password' field you would have to put a single dash "-"
in it's place.
Thanks, I'll do that. What is the directory in the first set of node numbers for? Outbound? The example I have has echomail as the mail directory name and that didn't tell me what the directory was for.
Weird, I don't see Ascension's original message here, just Shurato's reply to it.
It looks like it will be related to Hub 1 sending me zero sized files, and clrghouz rejecting them (SKIP). I musnt be sending the skip correctly as the connection is dropping soon after.
It looks like it will be related to Hub 1 sending me zero sized files, clrghouz rejecting them (SKIP). I musnt be sending the skip correctly a connection is dropping soon after.
OK, looks like I fixed it. A bunch of mail came in.. :)
What should I have in exec "start /min etc..." for fastecho? I tried to start a batch file that irex runs (between.bat) to run all of fastecho's tasks, but got an error that the exec command wasn't correct.
I've got:
exec "@start /min c:\\ele\\irex\\between.bat"
Can I have 5D domains in binkd? I've got 2 domains with the zone of 10 (League10 had it first, but Araknet is more popular) and have been using
2 instances of irex to get around that with one using fastecho and one using gecho.
On 29 Sep 2024, Shurato said the following...
What should I have in exec "start /min etc..." for fastecho? I triedto
start a batch file that irex runs (between.bat) to run all offastecho's
tasks, but got an error that the exec command wasn't correct.
I've got: exec "@start /min c:\\ele\\irex\\between.bat"
It looks like you're missing the *.<extension> at the end. Try:
exec "@start /min c:\\ele\\irex\\between.bat" *.pkt exec "@start
/min c:\\ele\\irex\\between.bat" *.[mwtfs][oehrau][0-9a-zA-Z]
Jay
... What do you call a cow on a trampoline? A milk shake
--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64) * Origin: Northern
Realms (21:3/110)
I've got: exec "@start /min c:\\ele\\irex\\between.bat"
It looks like you're missing the *.<extension> at the end. Try:
exec "@start /min c:\\ele\\irex\\between.bat" *.pkt exec "@start
/min c:\\ele\\irex\\between.bat" *.[mwtfs][oehrau][0-9a-zA-Z]
I did see that, but I'm not using that. I guess it ciuld just be
ignored.
Can I have 5D domains in binkd? I've got 2 domains with the zone of 10 (League10 had it first, but Araknet is more popular) and have been using 2 instances of irex to get around that with one using fastecho and one using gecho. I think I just need to set iport or oport in binkd to specify a different port number. I'd guess one is mine and one is remote, but I'm not sure which is which.
Hello Shurato!
29 Sep 24 20:44, you wrote to Warpslide:
I've got: exec "@start /min c:\\ele\\irex\\between.bat"
It looks like you're missing the *.<extension> at the end. Try:
exec "@start /min c:\\ele\\irex\\between.bat" *.pkt exec "@start /min >> c:\\ele\\irex\\between.bat" *.[mwtfs][oehrau][0-9a-zA-Z]
I did see that, but I'm not using that. I guess it ciuld just be ignored.
If you want binkd to fire off your script then what warpslide posted is correct.
This is what is on my linux system:
exec "/home/husky/hpt-copy.sh" /home/husky/inbound.sec/*.[0-9A-Za-z] *.[pP][kK][tT]
First is the path to the script, and must be in quotes ( " " ) then the dir that binkd looks in, followd by the file name patterns to look for
[...]This is what is on my linux system:
exec "/home/husky/hpt-copy.sh"
/home/husky/inbound.sec/*.[0-9A-Za-z] *.[pP][kK][tT]
I understand that, but I'm don't need to look for any file patterns,
the executables in the batch file do that for me. I would think binkd would be flexible enough to not need something that isn't being used.
I'll just bite the bullet and add *.pkt, even though it really won't
do anything...
[...]This is what is on my linux system:
exec "/home/husky/hpt-copy.sh"
/home/husky/inbound.sec/*.[0-9A-Za-z] *.[pP][kK][tT]
I understand that, but I'm don't need to look for any file patterns,
the executables in the batch file do that for me. I would think binkd would be flexible enough to not need something that isn't being used.
I'll just bite the bullet and add *.pkt, even though it really won't
do anything...
Hello Shurato!
30 Sep 24 14:52, you wrote to me:
This is what is on my linux system:
[...]exec "/home/husky/hpt-copy.sh" /home/husky/inbound.sec/*.[0-9A-Za-z] Vo>> *.[pP][kK][tT]
I understand that, but I'm don't need to look for any file patterns, the executables in the batch file do that for me. I would thinkbinkd
would be flexible enough to not need something that isn't being used. I'll just bite the bullet and add *.pkt, even though it really won't do anything...
Binkd won't do anything at all if you don't give it a file mask to look for.
That's the *.[0-9A-Za-z] *.[pP][kK][tT] part.
The *.[0-9A-Za-z] is looking for compressd packets, while the *.[pP][kK][tT] is looking for raw packets.
When it finds that matching mask at the end of the session, it starts your script. Nothing more nothing less.
It is then upto your script to do any fancy things.
Vorlon
--- GoldED+/LNX 1.1.5-b20240302 * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (21:1/195)
How do I poll periodically, then run between.bat? It's not happening automagically, only systems polling me are working and I'm on hold with some networks so I have to run binkd -P 21:2/100 binkd.cfg to poll fsxnet, then run between.bat manually.
How do I poll periodically, then run between.bat? It's not happening automagically, only systems polling me are working and I'm on hold with some networks so I have to run binkd -P 21:2/100 binkd.cfg to poll fsxnet, then run between.bat manually.
domain fidonet c:\\ele\\irex\\outbound 1 fidonet
domain Araknet c:\\ele\\irex\\outbound 10 Araknet
domain fsxnet c:\\ele\\irex\\outbound 21 fsxnet
domain micronet c:\\ele\\irex\\outbound 618 micronet
domain tqwnet c:\\ele\\irex\\outbound 1337 tqwnet
domain fu-net c:\\ele\\irex\\outbound 38 fu-net
domain sfnet c:\\ele\\irex\\outbound 42 sfnet
#domain league10 c:\\ele\\irex\\outbound 10 league10
Is that wrong? My outbound isn't working so I've temporarily gone
back to irex...
How do I poll periodically, then run between.bat? It's not
happening automagically, only systems polling me are working and
I'm on hold with some networks so I have to run binkd -P 21:2/100
binkd.cfg to poll fsxnet, then run between.bat manually.
I added -P with all of the node numbers I'm using and -n to a
scheduled event hourly. Is that good enough? I'm not sure if -n will
do what I want, but I don't want a bunch of processes running and it
seems to schedule them as needed.
domain fidonet c:\\ele\\irex\\outbound 1 fidonet
domain Araknet c:\\ele\\irex\\outbound 10 Araknet
domain fsxnet c:\\ele\\irex\\outbound 21 fsxnet
Is that wrong? My outbound isn't working so I've temporarily gone
back to irex...
Yes it is wrong (That always catches out people)...
You use the same zone number for all outbounds.
domain amiganet /home/husky/outbound 3
...
address 39:901/0@amiganet
Hello Shurato!
02 Oct 24 15:56, you wrote to Warpslide:
domain fidonet c:\\ele\\irex\\outbound 1 fidonet domain Araknet c:\\ele\\irex\\outbound 10 Araknet domain fsxnet c:\\ele\\irex\\outbound 21 fsxnet domain micronet c:\\ele\\irex\\outbound 618 micronet domain tqwnet c:\\ele\\irex\\outbound 1337 tqwnet domain fu-net c:\\ele\\irex\\outbound 38 fu-net domain sfnet
c:\\ele\\irex\\outbound 42 sfnet #domain league10 c:\\ele\\irex\\outbound 10 league10
Is that wrong? My outbound isn't working so I've temporarily gone back to irex...
Yes it is wrong (That always catches out people)... You use the same
zone number for all outbounds.
I'm on linux but the same applies:
Re: Mailer and front end...
By: Vorlon to Shurato on Thu Oct 03 2024 09:48 am
domain fidonet c:\\ele\\irex\\outbound 1 fidonet domain Araknet c:\\ele\\irex\\outbound 10 Araknet domain fsxnet c:\\ele\\irex\\outbound 21 fsxnet
Is that wrong? My outbound isn't working so I've temporarily gone back to irex...
Yes it is wrong (That always catches out people)... You use the same zone number for all outbounds.
It does catch out everybody, and yes it is wrong.
The number indicates what is the "primary" zone for that path (you have C:\\ele\\irex\\outbound), ie: so everything in that path is zone "x" (you have 1 for the first line). Anything in a path C:\\ele\\irex\\outbound.XXX will be for zone XXX (where XXX is the zone number in hex, so zone 21 will be 015).
So you decide what is your primary domain (most use fidonet) and if you are in zone 1 fidonet, then use "1" for *every* line. binkd will then know anything in a "outbound.XXX" is for the other zones. The mapping is done with the domain from the address, matched to the domain of the "domain":
domain amiganet /home/husky/outbound 3
...
address 39:901/0@amiganet
So binkd in this case will know that anything in outbound.027 is for amignet, and the zone is 39.
You'll need to make sure the "primary" for your mail tosser works a similar way and understands the same primary outbound dir.
Re: Mailer and front end...
By: Vorlon to Shurato on Thu Oct 03 2024 09:48 am
domain fidonet c:\\ele\\irex\\outbound 1 fidonet domain Araknet c:\\ele\\irex\\outbound 10 Araknet domain fsxnet c:\\ele\\irex\\outbound 21 fsxnet
Is that wrong? My outbound isn't working so I've temporarily gone back to irex...
Yes it is wrong (That always catches out people)... You use the same zone number for all outbounds.
It does catch out everybody, and yes it is wrong.
The number indicates what is the "primary" zone for that path (you have C:\\ele\\irex\\outbound), ie: so everything in that path is zone "x" (you have 1 for the first line). Anything in a path C:\\ele\\irex\\outbound.XXX will be for zone XXX (where XXX is the zone number in hex, so zone 21 will be 015).
So you decide what is your primary domain (most use fidonet) and if you are in zone 1 fidonet, then use "1" for *every* line. binkd will then know anything in a "outbound.XXX" is for the other zones. The mapping is done with the domain from the address, matched to the domain of the "domain":
domain amiganet /home/husky/outbound 3
...
address 39:901/0@amiganet
domain fidonet c:\\ele\\irex\\outbound 1
domain Araknet c:\\ele\\irex\\outbound 1
domain fsxnet c:\\ele\\irex\\outbound 1
domain micronet c:\\ele\\irex\\outbound 1
domain tqwnet c:\\ele\\irex\\outbound 1
domain fu-net c:\\ele\\irex\\outbound 1
domain sfnet c:\\ele\\irex\\outbound 1
#domain league10 c:\\ele\\irex\\outbound 1
address 1:340/1101@fidonet
address 10:103/31@Araknet
address 21:2/148@fsxnet
address 38:503/30@fu-net
address 42:12/1@sfnet
address 618:300/50@micronet
address 1337:3/185@tqwnet
#address 10:3/18@league10
Is that correct? I've got i for my hubs, but it never seems to send anything...
Should it send when polling, or only when polled? For my command line
I'm using:
C:\ele\binkd\binkd.exe -s -c -T -P 1:340/400 -P 10:103/0 -P 21:1/10 -P 21:2/100 -P 38:503/1 -P 42:17/1 -P 618:300/1 -P 1337:3/100 -P
618:100/1 binkdall.cfg
My mail tosser uses domain.hex as the directory name, in the directory above the specified outbound directory. I've put zone 1 for everything now. I think this is working, but I'm not positive.
Re: Mailer and front end...
By: Shurato to deon on Wed Oct 02 2024 09:22 pm
Howdy,
My mail tosser uses domain.hex as the directory name, in the directoryabove
the specified outbound directory. I've put zone 1 for everything now.I
think this is working, but I'm not positive.
OK, if your toss is using "domain.hex", then the instructions that vorlon and I are giving you are not appropriate, and they are for a different situation.
If your tosser is putting mail into a directory that has both the domain and hex name, eg: fsxnet.015, fidonet.001, amiganet.027, etc, then you *will* need to use the configuration that you originally had - but you need to use the correct directory with it.
ie: something like
domain fidonet c:\\ele\\irex\\outbound\\fidonet.001 1 domain Araknet c:\\ele\\irex\\outbound\\araknet.00a 10 domain fsxnet c:\\ele\\irex\\outbound\\fsxnet.015 21 domain micronet c:\\ele\\irex\\outbound\\micronet.26a 618
(I think anyway - I've never had a tosser that works this way).
The only problem when I can think of might be fidonet (since it uses zones 1-4), so you might need to have \\fidonet 32767, which should still see stuff for zone 1 in \\fidonet.001, and zone 3 \\fidonet.003, etc
If the above doesnt work correctly, then this might be better
domain fidonet c:\\ele\\irex\\outbound\\fidonet 32767 domain Araknet c:\\ele\\irex\\outbound\\araknet 32767 domain fsxnet c:\\ele\\irex\\outbound\\fsxnet 32767 domain micronet c:\\ele\\irex\\outbound\\micronet 32767
YMMV :)
...δεσ∩
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
Re: Mailer and front end...
By: Shurato to deon on Wed Oct 02 2024 09:22 pm
Howdy,
directoryMy mail tosser uses domain.hex as the directory name, in the
abovenow.
the specified outbound directory. I've put zone 1 for everything
I
think this is working, but I'm not positive.
OK, if your toss is using "domain.hex", then the instructions thatvorlon
and I are giving you are not appropriate, and they are for adifferent
situation.
If your tosser is putting mail into a directory that has both thedomain
and hex name, eg: fsxnet.015, fidonet.001, amiganet.027, etc, thenyou
*will* need to use the configuration that you originally had - butyou
need to use the correct directory with it.
ie: something like
domain fidonet c:\\ele\\irex\\outbound\\fidonet.001 1 domain Araknet c:\\ele\\irex\\outbound\\araknet.00a 10 domain fsxnet c:\\ele\\irex\\outbound\\fsxnet.015 21 domain micronet c:\\ele\\irex\\outbound\\micronet.26a 618
(I think anyway - I've never had a tosser that works this way).
The only problem when I can think of might be fidonet (since it useszones
1-4), so you might need to have \\fidonet 32767, which should stillsee
stuff for zone 1 in \\fidonet.001, and zone 3 \\fidonet.003, etc
If the above doesnt work correctly, then this might be better
domain fidonet c:\\ele\\irex\\outbound\\fidonet 32767 domain Araknet c:\\ele\\irex\\outbound\\araknet 32767 domain fsxnet c:\\ele\\irex\\outbound\\fsxnet 32767 domain micronet c:\\ele\\irex\\outbound\\micronet 32767
YMMV :)
It's working! The only problem is that my exec command is not running when inbound packets are encountered. It was before, but I broke
it some how. I could just schedule between.bat to run hourly.
exec "@start /min c:\\ele\\irex\\between.bat" c:\\ele\\irex\\inbound\\*.pkt exec "@start /min c:\\ele\\irex\\between.bat" c:\\ele\\irex\\inbound\\*.[mwtfs][oehrau][0-9a-zA-Z]
It's working! The only problem is that my exec command is not running when inbound packets are encountered. It was before, but I broke it some how. I could just schedule between.bat to run hourly.
exec "@start /min c:\\ele\\irex\\between.bat" c:\\ele\\irex\\inbound\\*.pkt exec "@start /min c:\\ele\\irex\\between.bat" c:\\ele\\irex\\inbound\\*.[mwtfs][oehrau][0-9a-zA-Z]
Re: Mailer and front end... By: Shurato to deon on Thu Oct 03 2024
06:26 am
Howdy,
It's working! The only problem is that my exec command is not runningwhen
inbound packets are encountered. It was before, but I broke it somehow. I
could just schedule between.bat to run hourly.
exec "@start /min c:\\ele\\irex\\between.bat"c:\\ele\\irex\\inbound\\*.pkt
exec "@start /min c:\\ele\\irex\\between.bat" c:\\ele\\irex\\inbound\\*.[mwtfs][oehrau][0-9a-zA-Z]
Which config did you go with to get it to work? Might be useful to know
for somebody else...
Your binkd log output will be useful to figure out why the exec isnt working. I'm going to guess its a case issue - which was suggested before, ie: you'll need to match *.pkt and *.PKT, and *.mo0 and *.MO0, etc
Your binkd log output will be useful to figure out why the exec isnt working. I'm going to guess its a case issue - which was suggested before, ie: you'll need to match *.pkt and *.PKT, and *.mo0 and *.MO0, etc
I checked it from the bottom up for "exec" and the last one was run Oct 1st. No other entries. I have no idea why it's not running, the case checking is correct.
Re: Mailer and front end... By: Shurato to deon on Thu Oct 03 2024
02:10 pm
Howdy,
I checked it from the bottom up for "exec" and the last one was run Oct1st.
No other entries. I have no idea why it's not running, the casechecking is
correct.
If you provided a snippet from a session (where files were transferred), that would be helpful.
Not looking for the "exec" lines - looking for information about the received files so that we (I) can confirm your configuration looks appropriate.
You might need to up the debugging of binkd as well.
Re: Mailer and front end...+ 04 Oct 10:29:54 [4516] incoming session with 149.56.142.85
By: Shurato to deon on Thu Oct 03 2024 02:10 pm
Howdy,
I checked it from the bottom up for "exec" and the last one was run Oct1st.
No other entries. I have no idea why it's not running, the casechecking is
correct.
If you provided a snippet from a session (where files were transferred), that would be helpful.
Not looking for the "exec" lines - looking for information about the received files so that we (I) can confirm your configuration looks appropriate.
You might need to up the debugging of binkd as well.
- 04 Oct 10:29:54 [4516] receiving 0000ffab.fr3 (3748 byte(s), off 0)
+ 04 Oct 10:29:54 [4516] 0000ffab.fr3 -> c:\ele\irex\inbound\0000ffab.fr3
+ 04 Oct 10:29:54 [4516] rcvd: 0000ffab.fr3 (3748, 3748.00 CPS, 1337:3/100@tqwnet)
I'm looking for lowercase *.fr3.
exec "@start /min c:\\ele\\irex\\between.bat" *.pkt
- 04 Oct 10:29:54 [4516] receiving 0000ffab.fr3 (3748 byte(s), off
0) + 04 Oct 10:29:54 [4516] 0000ffab.fr3 ->
c:\ele\irex\inbound\0000ffab.fr3 + 04 Oct 10:29:54 [4516] rcvd:
0000ffab.fr3 (3748, 3748.00 CPS,
1337:3/100@tqwnet)
I'm looking for lowercase *.fr3.
OK, you said your exec line was this:
exec "@start /min c:\\ele\\irex\\between.bat" *.pkt
You probably need to have this
exec "@start /min c:\\ele\\irex\\between.bat" c:\\ele\\irex\\inbound\\*.pkt
And it wouldnt hurt to have [pP][kK][tT] as you cant assume all
mailers will send you lower case packets.
Re: Mailer and front end... By: Shurato to deon on Fri Oct 04 2024
10:35 am
Howdy,
- 04 Oct 10:29:54 [4516] receiving 0000ffab.fr3 (3748 byte(s), off 0)c:\ele\irex\inbound\0000ffab.fr3
+ 04 Oct 10:29:54 [4516] 0000ffab.fr3 ->
+ 04 Oct 10:29:54 [4516] rcvd: 0000ffab.fr3 (3748, 3748.00 CPS, 1337:3/100@tqwnet)
I'm looking for lowercase *.fr3.
OK, you said your exec line was this:
exec "@start /min c:\\ele\\irex\\between.bat" *.pkt
You probably need to have this
exec "@start /min c:\\ele\\irex\\between.bat"
c:\\ele\\irex\\inbound\\*.pkt
And it wouldnt hurt to have [pP][kK][tT] as you cant assume all mailers
will send you lower case packets.
exec "@start /min c:\\ele\\irex\\between.bat" c:\\ele\\irex\\inbound\\*.pkt exec "@start /min c:\\ele\\irex\\between.bat" c:\\ele\\irex\\inbound\\*.[mwtfs][oehrau][0-9a-zA-Z]
exec "@start /min c:\\ele\\irex\\between.bat"c:\\ele\\irex\\inbound\\*.pkt
exec "@start /min c:\\ele\\irex\\between.bat" c:\\ele\\irex\\inbound\\*.[mwtfs][oehrau][0-9a-zA-Z]
Is the above 2 lines in your config file? It looks like 3 lines due to the BBS word wrapping but that last line needs to be after the stuff on the second line.
And everything is lower case coming in. I could set it for upper as
well, but so far I'm only getting *.[mwtfs][oehrau][0-9a-zA-Z] in lower case according to the logs.
It's working! The only problem is that my exec command is not running when inbound packets are encountered. It was before, but I broke it some how.
I've got my delays set to 1h.
call-delay 1h
rescan-delay 1h
On 04 Oct 2024, Shurato said the following...
And everything is lower case coming in. I could set it for upper as well, but so far I'm only getting *.[mwtfs][oehrau][0-9a-zA-Z] inlower
case according to the logs.
This is what I have configured:
*.[STFWMstfwm][ouaherOUAHER][0-9A-Za-z] *.[pP][kK][tT]
When I first came back to the hobby I had one link and everything was coming in uppercase. As I connected with more people things started coming in either/or. Doesn't hurt to set it this way to future-proof yourself.
I also have another line for .tic files:
exec "/home/ubuntu/fido/filein.sh" *.[tT][iI][cC]
I'll set that up. I don't see it making exec commands run though, all
of my nodes are sending lower case file names right now.
Re: Mailer and front end... By: Shurato to deon on Thu Oct 03 2024
06:26 am
It's working! The only problem is that my exec command is not runningwhen
inbound packets are encountered. It was before, but I broke it somehow.
When you added the path portion, you added something which will never be a match to any inbound file.
Short version - Look at the example below and pay **VERY** close attention to the use of backslashes. The line wrapping is going to mangle the line:
exec "@start /min c:\\ele\\irex\\between.bat" c:\\\\ele\\\\irex\\\\inbound\\\\*.pkt
Pointlessly long version - The last parameter here is a regular
expression, not a filename mask. The backslash character is used as an escape character both when reading the configuration file and when performing the regex matching. So this original parameter in the BinkD config file:
c:\\ele\\irex\\inbound\\*.pkt
Gets escaped down to this when the config file is parsed:
c:\ele\irex\inbound\*.pkt
And when escaped the second time during the regex evalution, it becomes this:
c:eleirexinbound*.pkt
That is a literal string without any wildcards. You need the additional backslashes so the parameter gets passed to the regex function with the backslashes escaped.
\\\\ -> \\ -> \
Also, the regular expressions for the flag/exec parameters haven't been
case sensitive for a while now (20+ years) so there's no point accounting for upper and lower case in them...
Re: Mailer and front end... By: Shurato to Shurato on Thu Oct 03 2024
06:27 am
I've got my delays set to 1h.
call-delay 1h rescan-delay 1h
Why would you do this? Even for a super-busy mail hub a 1 hour rescan
delay would be quite excessive. A 1 hour call delay on top of that also makes little sense.
On 05 Oct 2024, Shurato said the following...
I'll set that up. I don't see it making exec commands run though,all
of my nodes are sending lower case file names right now.
Have you tried not putting the path in? e.g.
exec "@start /min c:\\ele\\irex\\between.bat" *.[pP][kK][tT] exec
"@start /min c:\\ele\\irex\\between.bat" *.[STFWMstfwm][ouaherOUAHER][0-9A-Za-z]
That's what I have setup on Windows/Telegard and it works here:
- 12 Jan 23:16:56 [7368] receiving a20eaa00.pkt (1794 byte(s), off 0)
+ 12 Jan 23:16:56 [7368] a20eaa00.pkt -> c:\telegard\echomail\in\a20eaa00.pkt 12 Jan 23:16:56 [7368] got
*.pkt, delayed starting @start /min c:\telegard\husky\mailin.bat +
12 Jan 23:16:368] rcvd: a20eaa00.pkt (1794, 1794.00 CPS, 1:12/0@fidonet)
+ 12 Jan 23:16:56 [7368] done (to 21:3/110@fsxnet, OK, S/R: 0/1 (0/1794 bytes)) 12 Jan 23:16:[368] Running @start /min
c:\telegard\husky\mailin.bat - 12 Jan 23:16:56 [7368] executing
`@start /min c:\telegard\husky\mailin.bat'
Also, are you running 1.1a-115?
C:\TELEGARD\BINKD>binkd.exe -vv Binkd 1.1a-115 (Jul 2 2022
18:13:31/Win32) Compilation flags: msvc, static, zlib, bzlib2,
perl, https, ntlm, amiga_4d_outbound, bwlim, ipv6, af_force.
Facilities: fts5004 ipv6
Jay
... What kind of exercise do lazy people do? Diddly-squats
--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64) * Origin: Northern
Realms (21:3/110)
On 05 Oct 2024, Shurato said the following...
I'll set that up. I don't see it making exec commands run though,all
of my nodes are sending lower case file names right now.
Have you tried not putting the path in? e.g.
exec "@start /min c:\\ele\\irex\\between.bat" *.[pP][kK][tT] exec
Also, the regular expressions for the flag/exec parameters haven't
been case sensitive for a while now (20+ years) so there's no point
accounting
for upper and lower case in them...
Thanks, I'll try that! People insisted on case sensitivity, so I added those contingencies.
Why would you do this? Even for a super-busy mail hub a 1 hour rescan
delay would be quite excessive. A 1 hour call delay on top of that
also makes little sense.
It was defaulting to a minute. What should I set it to?