Joseph Larsen wrote to All on 11-22-17 20:49 <=-
Hi all,
I'm having problems with BinkP not launching the incoming/outgoing
script that tosses the echomail. Anyone have any idea why it's not launching?
I'm having problems with BinkP not launching the incoming/outgoing script that tosses the echomail. Anyone have any idea why it's not launching?
flag c:\\sbbs\\data\\fidoin.now *.pkt *.PKT
flag c:\\sbbs\\data\\fidoin.now *.[mMwWtTfFsS][oOeEhHrRaAuU][0-9a-zA-Z]
flag c:\\sbbs\\data\\fidoin.now *.pkt *.PKT
flag c:\\sbbs\\data\\fidoin.now
*.[mMwWtTfFsS][oOeEhHrRaAuU][0-9a-zA-Z]
Here's what I have:
flag toss!.now *.su? *.mo? *.tu? *.we? *.th? *.fr? *.sa? *.pkt
lag 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/dd/fido/runfido.sh /home/dd/fido/in.sec" /home/dd/fido/in.sec/*.[STFWMstfWM][ouaherOUAHER][0-9A-ZA-a] *.[pP][kK][tT]
Hi! Joseph (ignatius),
On 23 Nov 17 00:13, you wrote to Bill McGarrity:
flag c:\\sbbs\\data\\fidoin.now *.pkt *.PKT
flag c:\\sbbs\\data\\fidoin.now
*.[mMwWtTfFsS][oOeEhHrRaAuU][0-9a-zA-Z]
Here's what I have:
flag toss!.now *.su? *.mo? *.tu? *.we? *.th? *.fr? *.sa? *.pkt
lag 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/dd/fido/runfido.sh /home/dd/fido/in.sec" /home/dd/fido/in.sec/*.[STFWMstfWM][ouaherOUAHER][0-9A-ZA-a] *.[pP][kK][tT]
With binkD it's _not_ an "all or nothing" thing to process incoming. Y
Bill uses flags. I like to use exec, like so...
exec "/opt/ftn/fido/bin/tossmail.sh" *.su? *.mo? *.tu? *.we? *.th? *.f
If nothing works for you then maybe you may either have a permissions p
Cheers,
Paul.
... For a good time call 86753099 (Jenny)...
--- GoldED+/LNX 1.1.5-b20110213
* Origin: Quinn's Rock - Live from Paul's Xubuntu desktop! (3:640/1384
I'm having problems with BinkP not launching the incoming/outgoing
script that tosses the echomail. Anyone have any idea why it's not launching?
I'm having problems with BinkP not launching the
incoming/outgoing script that tosses the echomail. Anyone have
any idea why it's not launching?
Are you using the 'FLAG' suffix to create a semaphore that will tell
your tosser to process inbound mail?
Here's what I have:
flag toss!.now *.su? *.mo? *.tu? *.we? *.th? *.fr? *.sa? *.pkt
lag 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/dd/fido/runfido.sh /home/dd/fido/in.sec" /home/dd/fido/in.sec/*.[STFWMstfWM][ouaherOUAHER][0-9A-ZA-a] *.[pP][kK][tT]
Is that all one line?
I actually solved it. I (re)copied the binkd binary over, and for some strange reason it's actually working now. Strange. Anyway, thank you for your help. It's grately appreciated.
Joseph Larsen wrote to Bill McGarrity on 11-23-17 00:13 <=-
flag c:\\sbbs\\data\\fidoin.now *.pkt *.PKT
flag c:\\sbbs\\data\\fidoin.now *.[mMwWtTfFsS][oOeEhHrRaAuU][0-9a-zA-Z]
Here's what I have:
flag toss!.now *.su? *.mo? *.tu? *.we? *.th? *.fr? *.sa? *.pkt
lag 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/dd/fido/runfido.sh /home/dd/fido/in.sec" /home/dd/fido/in.sec/*.[STFWMstfWM][ouaherOUAHER][0-9A-ZA-a] *.[pP][kK][tT]
Nicholas Boel wrote to Bill McGarrity on 11-23-17 00:28 <=-
On Wed Nov 22 2017 17:13:00, Bill McGarrity wrote to Joseph Larsen:
I'm having problems with BinkP not launching the
incoming/outgoing script that tosses the echomail. Anyone have
any idea why it's not launching?
Are you using the 'FLAG' suffix to create a semaphore that will tell
your tosser to process inbound mail?
He's not running Synchronet. He isn't using semaphores. He should
probably be using an "exec" line, but he switches BBS softwares so much
I can't keep up with what he's doing on a regular basis. ;)
On your EXEC line, it seems you're telling where the secure folder is twice, once in the cfg under 'inbound' and once in your exec. Try it
this way and see what happens....
exec "/home/dd/fido/runfido.sh" *.[mMwWtTfFsS][oOeEhHrRaAuU][0-9a-zA-Z] exec "/home/dd/fido/runfido.sh" *.[pP][kK][tT]
No, it's two seperate lines. Yes, the cut & paste didn't work out
right. I failed to explain myself, the first line was actually
commented out. The "exec" line was uncommented.
Yes. It is for Daydream BBS. True, it has been a while since i've used Daydream as my BBS "for echomail."
I actually solved this issue, however. It seems that xinetd wasn't
parsing the (Daydream) configuration file properly. I had to do a "/etc/init.d/xinetd reload" before it actually started to work.
On your EXEC line, it seems you're telling where the secure folder is twice, once in the cfg under 'inbound' and once in your exec. Try it
this way and see what happens....
exec "/home/dd/fido/runfido.sh" *.[mMwWtTfFsS][oOeEhHrRaAuU][0-9a-zA-Z] exec "/home/dd/fido/runfido.sh" *.[pP][kK][tT]
He's not running Synchronet. He isn't using semaphores. He should
probably be using an "exec" line, but he switches BBS softwares
so much I can't keep up with what he's doing on a regular basis.
;)
I see that now from his message to me. I told him he really didn't
even need the FLAG option and told him to clean up his EXEC option commands. I simplified it for him.... hopefully.. :)
Have a Happy Thanksgiving Nick!!
exec "/home/dd/fido/runfido.sh"
*.[mMwWtTfFsS][oOeEhHrRaAuU][0-9a-zA-Z] exec
"/home/dd/fido/runfido.sh" *.[pP][kK][tT]
if one really wants it simple and doesn't want to have to figure out
the above quoted regex* one could have an entry for each inbound file
exec "/home/ftn/bin/hpt toss link" /home/ftn/in/secure/*.[Ss][Uu][0-9A-Za-z] exec "/home/ftn/bin/hpt toss link" /home/ftn/in/secure/*.[Mm][Oo][0-9A-Za-z] exec
"/home/ftn/bin/hpt toss link"
/home/ftn/in/secure/*.[Tt][Uu][0-9A-Za-z] exec "/home/ftn/bin/hpt toss link" /home/ftn/in/secure/*.[Ww][Ee][0-9A-Za-z] exec
"/home/ftn/bin/hpt toss link"
/home/ftn/in/secure/*.[Tt][Hh][0-9A-Za-z] exec "/home/ftn/bin/hpt toss link" /home/ftn/in/secure/*.[Ff][Rr][0-9A-Za-z] exec
"/home/ftn/bin/hpt toss link"
/home/ftn/in/secure/*.[Ss][Aa][0-9A-Za-z] exec "/home/ftn/bin/hpt toss link" /home/ftn/in/secure/*.[Pp][Kk][Tt] exec "/home/ftn/bin/hpt toss link" /home/ftn/in/secure/*.[Tt][Ii][Cc]
*the above quoted regex, seen in a lot of places, allows for more than
the desired FTN mail bundle extensions... this may not be a good thing
in some cases...
Isn't xinetd just the telnet handler that answers and passes the connec
exec "/home/dd/fido/runfido.sh"
*.[mMwWtTfFsS][oOeEhHrRaAuU][0-9a-zA-Z] exec
"/home/dd/fido/runfido.sh" *.[pP][kK][tT]
if one really wants it simple and doesn't want to have to figure out
the above quoted regex* one could have an entry for each inbound file
If someone has to "figure out the above quoted regex", they obviously would have to figure out the below quoted regex as well. ;)
*the above quoted regex, seen in a lot of places, allows for more
than the desired FTN mail bundle extensions... this may not be a good
thing in some cases...
Though this makes complete sense. However, anything received that the
mail processor doesn't understand, wouldn't be processed anyways.
Here's the /etc/xinet.d/telnet3 file:
service telnet3
disable = no
port = 26
socket_type = stream
protocol = tcp
user = dd
group = bbs
wait = no
server = /usr/sbin/in.telnetd
server_args = -n -h -L /home/dd/ddlogin
}
Notice the "group = bbs" line. I believe that's why it's working now.
I don't know why, but it is working. It was only after that I adjusted this file that it started working.
other than them being renamed by the toss when it figures out they're
not the proper format... the extension would be lost at that point... other than, hopefully, the tosser logs ;)
What did you adjust in that file, exactly? Did you just add "group = bb
What did you adjust in that file, exactly? Did you just add "group
= bb
Yes. That is correct. Again, I know it doesn't make any sense as to
why it's working, but it is now. After I added that line. Maybe i'm
just completely insane? :)
other than them being renamed by the toss when it figures out they're
not the proper format... the extension would be lost at that point...
other than, hopefully, the tosser logs ;)
Seems as though binkd ASSumes other tossers know how to create bundles with the proper extensions.
binkd doesn't care about the files' extensions, really... if i send "my_land.map" to you, binkd will trigger a mail toss because the .map extension matches the allowed .ma? so what i'm saying is that you
won't find my_land.map in your inbound because your tosser would have renamed it to my_land.bad... to further clarify, the long string
regexes that some use are too relaxed... they need to be more
strict...
don't be so FTN centric when thinking about these things... i've had
more than one set of files mangled in exactly this manner and that was long before binkd was even a gleam in its creator's eye... the
mangling i experianced was due to some files being named the same
except for the extension... when the tosser renamed the second one to .bad, it overwrote the first one... it took a week or two to figure
out what was happening with that file set and why... t'was a little on
the expensive side of the POTS bill, too...
exec "/home/dd/fido/runfido.sh"
*.[mMwWtTfFsS][oOeEhHrRaAuU][0-9a-zA-Z] exec
"/home/dd/fido/runfido.sh" *.[pP][kK][tT]
if one really wants it simple and doesn't want to have to figure out
the above quoted regex*
binkd doesn't care about the files' extensions, really... if i send
"my_land.map" to you, binkd will trigger a mail toss because the .map
extension matches the allowed .ma? so what i'm saying is that you
won't find my_land.map in your inbound because your tosser would have
renamed it to my_land.bad... to further clarify, the long string
regexes that some use are too relaxed... they need to be more
strict...
Tell that to the maintainers that continue with the long string regex
in the default binkd.conf-dist.
exec "/home/dd/fido/runfido.sh"
*.[mMwWtTfFsS][oOeEhHrRaAuU][0-9a-zA-Z]
exec "/home/dd/fido/runfido.sh" *.[pP][kK][tT]
if one really wants it simple and doesn't want to have to figure out
the above quoted regex*
Strictly speaking it is not a regex but a unix shell style pathname expansion.
Tell that to the maintainers that continue with the long string
regex in the default binkd.conf-dist.
we don't all have to follow the lead lemming(s) over the cliff, do we?
;)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,027 |
Nodes: | 17 (1 / 16) |
Uptime: | 62:55:32 |
Calls: | 502,335 |
Calls today: | 3 |
Files: | 100,779 |
D/L today: |
11,366 files (1,056M bytes) |
Messages: | 300,099 |