On 19 Feb 2021 at 08:26p, Black Panther pondered and said...

On 20 Feb 2021, 03:53p, Avon said the following...

I'm trying to get BinkD to execute a script when files that have the following syntax arrive at 1/100

z21n*.*

I can't seem to crack it, any thoughts?

I'm not sure if you meant to post this in the test echo or not, but I'll reply here. ;)

What I'm doing in my binkd.cfg file, is something like:

exec "~/mystic/rcs/fsxnet/stats.sh" fsxnet.z??

It should work with:

exec "~/path/to/makenl/makenl.sh" z21n*.*

Thanks I did try the latter but found it did not work.

I do think the issue may be it simply does not like to deal with filenames?

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 20 Feb 2021 at 03:26p, deon pondered and said...

Re: BinkD exec
By: Avon to All on Sat Feb 20 2021 03:53 pm

I'm trying to get BinkD to execute a script when files that have the following syntax arrive at 1/100
z21n*.*

Yeah, I havent looked at the code to see why, but on file receipt binkd only matches on wildcard extensions:

eg: test.* z21.[abc]* etc

If you want binkd to match on wildcard names, you need to prefix it with
a full path.

So in your case,

exec "/usr/local/tools/myscript.sh" /fido/mailer/inbound/z21n*
Should work.

Thanks, going to test this now ... appreciate the tip.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 20 Feb 2021 at 09:21p, Avon pondered and said...

On 20 Feb 2021 at 03:26p, deon pondered and said...

So in your case,

exec "/usr/local/tools/myscript.sh" /fido/mailer/inbound/z21n*
Should work.

Thanks, going to test this now ... appreciate the tip.

+ 20 Feb 21:27:01 [10106] pwd protected session (MD5)
- 20 Feb 21:27:01 [10106] QSIZE 1 files 6,211 bytes
- 20 Feb 21:27:01 [10106] receiving z21n4.050 (6211 byte(s), off 0)
+ 20 Feb 21:27:01 [10106] z21n4.050 -> /hub/echomail/in/z21n4.050
20 Feb 21:27:01 [10106] got /hub/echomail/in/z21n*, delayed starting /hub/bats/process-z21segments.sh

success, thanks... I am now going to run some tests to see if I can get that segment accepted netmail sent to you Deon.

Dan's is flowing to his preferred NET 1 address but the one test I did for
your segment failed to send.. I may need to create some settings for your
node at 1/100 but you would think netmail routing would work..

Will keep you both posted.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 20 Feb 2021 at 09:33p, Avon pondered and said...

Will keep you both posted.

Looks like I needed to define a link for you in my links area and also then create a record in BinkD

Can you check this packet came in OK please :)

- 20 Feb 22:18:08 [11843] OPT CRAM-MD5-8189b7c7658334b77d14aa8f3e709191 CRYPT
+ 20 Feb 22:18:08 [11843] Remote requests MD mode
+ 20 Feb 22:18:08 [11843] Remote requests CRYPT mode
- 20 Feb 22:18:08 [11843] SYS Alterant
- 20 Feb 22:18:08 [11843] ZYZ Alter Ego
- 20 Feb 22:18:08 [11843] LOC Parkdale, VIC
- 20 Feb 22:18:08 [11843] NDL 115200,TCP,BINKP
- 20 Feb 22:18:08 [11843] TIME Sat Feb 20 2021 20:18:07 GMT+1100 (AEDT)
- 20 Feb 22:18:08 [11843] VER BinkIT/2.41,JSBinkP/4,sbbs3.18c/Linux binkp/1.1
+ 20 Feb 22:18:08 [11843] addr: 3:633/509@fidonet
+ 20 Feb 22:18:08 [11843] addr: 10:1/4@private (n/a or busy)
+ 20 Feb 22:18:08 [11843] addr: 21:2/116@fsxnet
+ 20 Feb 22:18:08 [11843] addr: 77:3/101@scinet (n/a or busy)
+ 20 Feb 22:18:08 [11843] addr: 80:774/87@retronet (n/a or busy)
+ 20 Feb 22:18:08 [11843] addr: 314:314/180@pinet (n/a or busy)
+ 20 Feb 22:18:08 [11843] addr: 1337:2/101@tqwnet (n/a or busy)
+ 20 Feb 22:18:08 [11843] addr: 44:61/1@dorenet (n/a or busy)
+ 20 Feb 22:18:08 [11843] addr: 618:510/2@micronet (n/a or busy)
+ 20 Feb 22:18:08 [11843] addr: 32:10/1@gamenet (n/a or busy)
+ 20 Feb 22:18:08 [11843] addr: 432:1/142@vkradio (n/a or busy)
+ 20 Feb 22:18:08 [11843] addr: 516:1/1@videotex (n/a or busy)
+ 20 Feb 22:18:08 [11843] addr: 24:24/2@sportnet (n/a or busy)
+ 20 Feb 22:18:08 [11843] addr: 637:1/104@happynet (n/a or busy)
+ 20 Feb 22:18:08 [11843] sending /hub/echomail/out.015/30d42600.sa0 as 30d42600.sa0 (426)
+ 20 Feb 22:18:09 [11843] sent: /hub/echomail/out.015/30d42600.sa0 (426,
426.00 CPS, 21:2/116@fsxnet)
+ 20 Feb 22:18:09 [11843] done (to 21:2/116@fsxnet, OK, S/R: 1/0 (426/0
bytes))
20 Feb 22:18:09 [11843] session closed, quitting...

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: BinkD exec
By: Avon to Deon on Sat Feb 20 2021 09:33 pm

Dan's is flowing to his preferred NET 1 address but the one test I did for your segment failed to send.. I may need to create some settings for your node at 1/100 but you would think netmail routing would work..

If that netmail is crash it will go with the next pack. If it is not crash you will likely need a routefile statement in your route config along with the route directive.

If no routefile is defined then files will not be routed at all.

Ttyl :-),
Al

... I can't decide between EDLIN and Word for Windows...
--- SBBSecho 3.13-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 20 Feb 2021 at 01:00a, Al pondered and said...

If that netmail is crash it will go with the next pack. If it is not
crash you will likely need a routefile statement in your route config along with the route directive.

If no routefile is defined then files will not be routed at all.

I did try things like

route crash 21:2/100 21:2/116
route crash 21:2/100 21:2/*

but neither seemed to work... it was just packing it direct, hence the need
to set something up in BinkD.. but certainly without defining a link with the 2/116 aka it would not pack the message and just delete it.

[snip]

with no link defined.

7 Feb:20:2021:21:56:22 Msg packed with flavour 'crash': 21:1/1 -> 21:2/116
L Feb:20:2021:21:56:22 Msg #1 from 21:1/1 to 21:2/116 deleted
D Feb:20:2021:21:56:22 Statistics
D Feb:20:2021:21:56:22 areas: 2 msgs: 93
D Feb:20:2021:21:56:22 exported: 1
E Feb:20:2021:21:56:22 Areas summary:
E Feb:20:2021:21:56:22 netmail area NETMSG - 1 msgs

[snip]

with 2//16 defined as a link

M Feb:20:2021:22:10:33 pktFile /hub/echomail/out/temp/30d26900.pkt created
for [21:2/116]
7 Feb:20:2021:22:10:33 Msg packed with flavour 'crash': 21:1/1 -> 21:2/116
L Feb:20:2021:22:10:33 Msg #1 from 21:1/1 to 21:2/116 deleted
M Feb:20:2021:22:10:33 packFile /hub/echomail/out.015/30d26900.sa0 created
for [21:2/116 via 21:2/116]
O Feb:20:2021:22:10:33 toss.c:arcmail(): opened '/hub/echomail/out.015/00020074.clo' ("a+" mode)

Question.. if this is just a confirmation of segment being processed netmail why would I need the routefile line?

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: BinkD exec
By: Avon to Deon on Sat Feb 20 2021 10:20 pm

Looks like I needed to define a link for you in my links area and also then create a record in BinkD
Can you check this packet came in OK please :)

Got it :)

...ëîåï

... Never marry a man who hates his mother because he'll end up hating you.
--- SBBSecho 3.12-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: BinkD exec
By: Avon to Al on Sat Feb 20 2021 10:26 pm

but neither seemed to work... it was just packing it direct, hence the need

...ëîåï
--- SBBSecho 3.12-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: BinkD exec
By: Avon to Al on Sat Feb 20 2021 10:26 pm

but neither seemed to work... it was just packing it direct, hence the need

Did you try without the CRASH on the notify line in makenl?

I havent tried that myself, but I would think that would generate a non crash netmail, which should then be routed normally.

...ëîåï

... A man's only as old as the woman he feels.
--- SBBSecho 3.12-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: BinkD exec
By: Avon to Al on Sat Feb 20 2021 10:26 pm

I did try things like

route crash 21:2/100 21:2/116
route crash 21:2/100 21:2/*

but neither seemed to work... it was just packing it direct, hence the need to set something up in BinkD.. but certainly without defining a link with the 2/116 aka it would not pack the message and just delete it.

Crash can mean different things to different tossers. Crash should mean send it now following our routing rules. I think in the case of HPT crash means send it now directly.

If a message has the crash bit that is what will happen. I use it rarely. I almost always send netmail without it, and in that case the route file defines what happens with netmail.

with no link defined.

7 Feb:20:2021:21:56:22 Msg packed with flavour 'crash': 21:1/1 -> 21:2/116 L Feb:20:2021:21:56:22 Msg #1 from 21:1/1 to 21:2/116 deleted
D Feb:20:2021:21:56:22 Statistics
D Feb:20:2021:21:56:22 areas: 2 msgs: 93
D Feb:20:2021:21:56:22 exported: 1
E Feb:20:2021:21:56:22 Areas summary:
E Feb:20:2021:21:56:22 netmail area NETMSG - 1 msgs

[snip]

with 2//16 defined as a link

M Feb:20:2021:22:10:33 pktFile /hub/echomail/out/temp/30d26900.pkt created for [21:2/116]
7 Feb:20:2021:22:10:33 Msg packed with flavour 'crash': 21:1/1 -> 21:2/116 L Feb:20:2021:22:10:33 Msg #1 from 21:1/1 to 21:2/116 deleted
M Feb:20:2021:22:10:33 packFile /hub/echomail/out.015/30d26900.sa0 created for [21:2/116 via 21:2/116]
O Feb:20:2021:22:10:33 toss.c:arcmail(): opened '/hub/echomail/out.015/00020074.clo' ("a+" mode)

Setting the crash bit changes things, the route file doesn't come into play.

One other note, when sending netmail directly to an unlinked node it is best (I think) not to archive it. It is going to arrive in the nodes unsecure inbound and some tossers like hpt won't unarchive mail in the unsecure inbound. They will import .pkt files so if it arrives that way it will get tossed.

Question.. if this is just a confirmation of segment being processed netmail why would I need the routefile line?

My mistake, I thought this was a file routing issue, but it isn't so that won't be needed. Come to think of it, I don't think think there is a routefile statement in my config at all and it is unlikely to be needed.

Ttyl :-),
Al

... Junk - stuff we throw away. Stuff - junk we keep.
--- SBBSecho 3.13-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 20 Feb 2021 at 09:20p, deon pondered and said...

Got it :)

Cool, that's progress..

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 20 Feb 2021 at 09:26p, deon pondered and said...

Did you try without the CRASH on the notify line in makenl?

I havent tried that myself, but I would think that would generate a non crash netmail, which should then be routed normally.

No not yet, I'll poke and prod some more to understand what is happening and what I can get away with. Ideally it would be routed netmail to your NET 2 address via 2/100 ... I'll keep at it.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 20 Feb 2021 at 02:20a, Al pondered and said...

Crash can mean different things to different tossers. Crash should mean send it

now following our routing rules. I think in the case of HPT crash means send it

now directly.

If a message has the crash bit that is what will happen. I use it
rarely. I almost always send netmail without it, and in that case the route file defines what happens with netmail.

Thanks, yep I'll test without this flag and report back.

One other note, when sending netmail directly to an unlinked node it is best (I

think) not to archive it. It is going to arrive in the nodes unsecure inbound and some tossers like hpt won't unarchive mail in the unsecure inbound. They will import .pkt files so if it arrives that way it will
get tossed.

I wonder how best to set such things up? So many packets pass through here
it's a benefit to me to keep it tidy and archived for assorted nodes when processing packets...

My mistake, I thought this was a file routing issue, but it isn't so
that won't

all good :)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: BinkD exec
By: Avon to Al on Sun Feb 21 2021 10:09 am

Thanks, yep I'll test without this flag and report back.

I've I'm following what you are trying to do I think that will work, if it's not crash you can just route it to 2/100.

I wonder how best to set such things up? So many packets pass through here it's a benefit to me to keep it tidy and archived for assorted nodes when processing packets...

It's ok to do that for your links, that'll all go into their protected inbound. It's only the unprotected nodes that will get your mail in their unprotected inbound.

Even if that happens, a lot of tossers will toss that mail. In some cases though it'll wait there til somebody see's it.

Technically that's their problem, not yours.. :)

Ttyl :-),
Al

... All wiyht. Rho sritched mg kegtops awound?
--- SBBSecho 3.13-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)