I was a Sysop 'back in the day', running IM and Proboard, and now running Synchronet. First, this is a test, to make sure my messages are getting out. Secondly, I was wondering where I can find binkit.js? I've been looking on the internet, but can't find where to get it. Am I missing something?
I was a Sysop 'back in the day', running IM and Proboard, and now runni Synchronet. First, this is a test, to make sure my messages are getting out. Secondly, I was wondering where I can find binkit.js? I've been looking on the internet, but can't find where to get it. Am I missing something?
Binkit is at cvs.synchro.net under the exec folder as it has not been releas yet it is still a developement version. Good luck, I could never get it to work correctly and am still using Irex2 myself.
Thank you. I have been having some slight issues getting IRex to play
nice with Synchronet. I'll keep playing around with the settings and
see if I can tweek it.
Thank you. I have been having some slight issues getting IRex to play nice with Synchronet. I'll keep playing around with the settings and see if I can tweek it.
Once you get IRex working and all, I'd like to bend your ear for a moment. I
Steven,
I've got IRex running now. I'm only using the SMTP/POP3 and BinkP
options at the moment. I'll be working on get the FTP set up when I
have a need for it.
What kind of questions did you have about IRex?
Steven Sheeley wrote to Black Panther <=-
I'm currently running Taurus with Synchronet and, when I configured
IRex, I got it running but only for outbound BinkP connections to my
hubs, I couldn't get it to connect to my hubs when they 'called'.
Taurus is ok, but it's not been activatly maintained since 2009 and it
has 'issues'. It works, but it takes hand holding to keep it running
and I have major issues when doing BinkP outbound to Mystic systems.
Did you have to tweak anythin on IRex or was it straight forward?
I'm currently running Taurus with Synchronet and, when I configured IRex, I
Taurus is ok, but it's not been activatly maintained since 2009 and it has '
Did you have to tweak anythin on IRex or was it straight forward?
Steven Sheeley wrote to Black Panther <=-
I'm currently running Taurus with Synchronet and, when I configured
IRex, I got it running but only for outbound BinkP connections to my
hubs, I couldn't get it to connect to my hubs when they 'called'.
Taurus is ok, but it's not been activatly maintained since 2009 and it
has 'issues'. It works, but it takes hand holding to keep it running
and I have major issues when doing BinkP outbound to Mystic systems.
Did you have to tweak anythin on IRex or was it straight forward?
Did you have to tweak anythin on IRex or was it straight forward?
Why not use binkd? It's actively maintained, and I've found it to be
a rock solid mailer. That's what I use on my Synchronet board.
mark lewis wrote to Vk3jed <=-
binkd only provides for one FTN protocol and has limited capabilities
when compared to other FTN mailers...
binkd only provides for one FTN protocol and has limited capabilities
when compared to other FTN mailers...
Fair enough, though the question was about using binkp.
mark lewis wrote to Tony Langdon <=-
Fair enough, though the question was about using binkp.
i understood it as choosing between Taurus and IREX and what had to be done to IREX to get it working with synchronet...
Right now you have an issue with Taurus and a bad address in the cfg.
My system can't connect with you.
Steven Sheeley wrote to Black Panther <=-
Why not use binkd? It's actively maintained, and I've found it to be
a rock solid mailer. That's what I use on my Synchronet board.
Bad address? The only issues that I am aware of is when I poll
certain Mystic systems. I'ev gott wo hubs that run Mystic that I can
not connect to when I poll, but they can connect to me just fine. I
have one Mystic hub that works perfectly in both directions.
Why not use binkd? It's actively maintained, and I've found it
to be a rock solid mailer. That's what I use on my Synchronet
board.
I've toyed with the idea of using BinkD but haven't had a chance to
look into it yet. I have a 25 node license for IRex and I'd like to
use that, but, overall, what I want is something that works.
Steven Sheeley wrote to Vk3jed <=-
I've toyed with the idea of using BinkD but haven't had a chance to
look into it yet. I have a 25 node license for IRex and I'd like to
use that, but, overall, what I want is something that works.
Steven Sheeley wrote to Bill McGarrity <=-
Bad address? The only issues that I am aware of is when I poll certain Mystic systems. I'ev gott wo hubs that run Mystic that I can not
connect to when I poll, but they can connect to me just fine. I have
one Mystic hub that works perfectly in both directions.
Accession wrote to Steven Sheeley <=-
As for the Mystic systems, most likely the Mystic operator has their
end setup wrong. Especially if you are able to connect to one both
ways, and the other two only one way.
Steven Sheeley wrote to Bill McGarrity <=-
15 Nov 16 10:23, you wrote to me:
Right now you have an issue with Taurus and a bad address in the cfg.
My system can't connect with you.
Bad address? The only issues that I am aware of is when I poll certain Mystic systems. I'ev gott wo hubs that run Mystic that I can not
connect to when I poll, but they can connect to me just fine. I have
one Mystic hub that works perfectly in both directions.
08:05 [9500] VER Taurus/5.101/16.02.2009, 19:33 (Winter)/Win32
binkp/1.1
08:05 [9500] remote passed bad address: `1:275/97@fidonet,10:10/145@league10,316:36/10@whispnet,80:30 0,169:1/197@battlnet'
08:05 [9500] done (to 1:275/97@fidonet, failed, S/R: 0/0 (0/0 bytes)) 08:05 [9500] session closed, quitting...
What is the 80:30,169?
Hiya Steven..
08:05 [9500] outgoing session with infinity.synchro.net:24554 [75.109.30.219]
08:05 [9500] OPT LST UTF
08:05 [9500] OPT CRAM-MD5-55135765b255a7fc08e54a1b11e18545
08:05 [9500] Remote requests MD mode
08:05 [9500] SYS Split Infinity BBS, TCP/IP 1
08:05 [9500] ZYZ Steven Sheeley
08:05 [9500] LOC Rupert, WV
08:05 [9500] PHN infinity.synchro.net
08:05 [9500] NDL MO,CM,TCP,BND
08:05 [9500] TIME Wed, 16 Nov 2016 13:08:24 -0500
08:05 [9500] VER Taurus/5.101/16.02.2009, 19:33 (Winter)/Win32
binkp/1.1
08:05 [9500] remote passed bad address: `1:275/97@fidonet,10:10/145@league10,316:36/10@whispnet,80:30 0,169:1/197@battlnet'
08:05 [9500] done (to 1:275/97@fidonet, failed, S/R: 0/0 (0/0 bytes)) 08:05 [9500] session closed, quitting...
Accession wrote to Bill McGarrity <=-
On 16 Nov 16 08:07, Bill McGarrity wrote to Steven Sheeley:
08:05 [9500] VER Taurus/5.101/16.02.2009, 19:33 (Winter)/Win32
binkp/1.1
08:05 [9500] remote passed bad address: `1:275/97@fidonet,10:10/145@league10,316:36/10@whispnet,80:30 0,169:1/197@battlnet'
08:05 [9500] done (to 1:275/97@fidonet, failed, S/R: 0/0 (0/0 bytes)) 08:05 [9500] session closed, quitting...
What is the 80:30,169?
169:1/197 is indeed a valid address. It's the 80:300 that is not, and
most likely the cause of your connection problem.
Steven Sheeley wrote to Bill McGarrity <=-
16 Nov 16 08:07, you wrote to me:
Hiya Steven..
08:05 [9500] outgoing session with infinity.synchro.net:24554 [75.109.30.219]
08:05 [9500] OPT LST UTF
08:05 [9500] OPT CRAM-MD5-55135765b255a7fc08e54a1b11e18545
08:05 [9500] Remote requests MD mode
08:05 [9500] SYS Split Infinity BBS, TCP/IP 1
08:05 [9500] ZYZ Steven Sheeley
08:05 [9500] LOC Rupert, WV
08:05 [9500] PHN infinity.synchro.net
08:05 [9500] NDL MO,CM,TCP,BND
08:05 [9500] TIME Wed, 16 Nov 2016 13:08:24 -0500
08:05 [9500] VER Taurus/5.101/16.02.2009, 19:33 (Winter)/Win32
binkp/1.1
08:05 [9500] remote passed bad address: `1:275/97@fidonet,10:10/145@league10,316:36/10@whispnet,80:30 <---- 0,169:1/197@battlnet'
08:05 [9500] done (to 1:275/97@fidonet, failed, S/R: 0/0 (0/0 bytes)) 08:05 [9500] session closed, quitting...
ANd this is what taurus says:: 16-Nov-2016 12:13:36 Flags : 115200,TCP,BINKP
6-Nov-2016 12:13:35 Establishing BinkP transfer protocol
16-Nov-2016 12:13:36 M_NUL : OPT NDA EXTCMD CRYPT GZ
= 16-Nov-2016 12:13:36 Station : TequilaMockingbird Online
= 16-Nov-2016 12:13:36 Address : 1:266/404 316:973/2 618:100/24 46:1/159 24:24/1 24:24/0 24:100/0 24:100/1 24:120/0 24:120/1 :
16-Nov-2016 12:13:36 SysOp : Bill McGarrity from Toms River, New Jersey USA : 16-Nov-2016 12:13:36 Number : 69.248.146.68
= 16-Nov-2016 12:13:36 Time : Wed, 16 Nov 2016 12:10:34 -0500
* 16-Nov-2016 12:13:36 Err: Bad address
16-Nov-2016 12:13:36 Disconnect reason is fatal error
* 16-Nov-2016 12:13:36 Session aborted
16-Nov-2016 12:13:36 Session traf: in: 0 (0b) out: 0 (0b) [410b/378b]
16-Nov-2016 12:13:36 Session time: 00:00:01
16-Nov-2016 12:13:36 End
The 80 address on my system is listed as 80:304/0 as per the assignment from the hub. The 169 address is for Battlet net.
What is the 80:30,169?
169:1/197 is indeed a valid address. It's the 80:300 that is not,
and most likely the cause of your connection problem.
I understand that.... that's why I asked him what that address was. :)
08:05 [9500] remote passed bad address:
`1:275/97@fidonet,10:10/145@league10,316:36/10@whispnet,80:30
<---- 0,169:1/197@battlnet'
ANd this is what taurus says:
-0500 * 16-Nov-2016 12:13:36 Err: Bad address
16-Nov-2016 12:13:36 Disconnect reason is fatal error
The 80 address on my system is listed as 80:304/0 as per the
assignment from the hub. The 169 address is for Battlet net.
That's fine but it's bradcasting 80:300. There is no node # or domain associated with it. Look above where I placed the <----
Steven Sheeley wrote to Bill McGarrity <=-
Hiya Steve....
16 Nov 16 08:07, you wrote to me:
Hiya Steven..
08:05 [9500] outgoing session with infinity.synchro.net:24554
[75.109.30.219]
08:05 [9500] OPT LST UTF
08:05 [9500] OPT CRAM-MD5-55135765b255a7fc08e54a1b11e18545
08:05 [9500] Remote requests MD mode
08:05 [9500] SYS Split Infinity BBS, TCP/IP 1
08:05 [9500] ZYZ Steven Sheeley
08:05 [9500] LOC Rupert, WV
08:05 [9500] PHN infinity.synchro.net
08:05 [9500] NDL MO,CM,TCP,BND
08:05 [9500] TIME Wed, 16 Nov 2016 13:08:24 -0500
08:05 [9500] VER Taurus/5.101/16.02.2009, 19:33 (Winter)/Win32
binkp/1.1
08:05 [9500] remote passed bad address:
`1:275/97@fidonet,10:10/145@league10,316:36/10@whispnet,80:30
<---- 0,169:1/197@battlnet'
08:05 [9500] done (to 1:275/97@fidonet, failed, S/R: 0/0 (0/0
bytes))
08:05 [9500] session closed, quitting...
ANd this is what taurus says:
6-Nov-2016 12:13:35 Establishing BinkP transfer protocol: 16-Nov-2016 12:13:36 Flags : 115200,TCP,BINKP
16-Nov-2016 12:13:36 M_NUL : OPT NDA EXTCMD CRYPT GZ
= 16-Nov-2016 12:13:36 Station : TequilaMockingbird Online
= 16-Nov-2016 12:13:36 Address : 1:266/404 316:973/2
618:100/24
46:1/159 24:24/1 24:24/0 24:100/0 24:100/1 24:120/0 24:120/1 :
16-Nov-2016 12:13:36 SysOp : Bill McGarrity from Toms River,
New Jersey USA : 16-Nov-2016 12:13:36 Number : 69.248.146.68
: 16-Nov-2016 12:13:36 Mailer : binkd/1.1a-94/Win32 binkp/1.1
= 16-Nov-2016 12:13:36 Time : Wed, 16 Nov 2016 12:10:34
-0500 * 16-Nov-2016 12:13:36 Err: Bad address
16-Nov-2016 12:13:36 Disconnect reason is fatal error
* 16-Nov-2016 12:13:36 Session aborted
16-Nov-2016 12:13:36 Session traf: in: 0 (0b) out: 0 (0b)
[410b/378b]
16-Nov-2016 12:13:36 Session time: 00:00:01
16-Nov-2016 12:13:36 End
The 80 address on my system is listed as 80:304/0 as per the
assignment from the hub. The 169 address is for Battlet net.
That's fine but it's bradcasting 80:300. There is no node # or domain associated with it. Look above where I placed the <----
--
Bill
Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net:81
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live
... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
--- MultiMail/Win32 v0.50
Accession wrote to Bill McGarrity <=-
On 16 Nov 16 19:48, Bill McGarrity wrote to Accession:
What is the 80:30,169?
169:1/197 is indeed a valid address. It's the 80:300 that is not,
and most likely the cause of your connection problem.
I understand that.... that's why I asked him what that address was. :)
Sorry Bill. The way you wrote it above seemed (to me anyways) like you were considering that the entire bad address including the ",169" part, whereas the 169 is actually part of his Battlenet address. Was only
trying to clarify if indeed it was misread.
On another note, his end seems to say something about a bad password.
I've ran into this when trying to connect to the Argus family of
mailers as well. If you have CRAM-MD5 enabled with that system, you may want to try without it, as the MD5 checksum given by the Argus family mailers seems to have extra characters (blank spaces?) that you can't
see on your end which can cause the connection to fail as it doesn't
match up with yours. Figured I'd throw that out there in case you guys come to a standstill and can't figure it out after the bad address is fixed.
Steven Sheeley wrote to Bill McGarrity <=-
Hello Bill!
16 Nov 16 19:52, you wrote to me:
Steven Sheeley wrote to Bill McGarrity <=-
The 80 address on my system is listed as 80:304/0 as per the
assignment from the hub. The 169 address is for Battlet net.
That's fine but it's bradcasting 80:300. There is no node # or domain associated with it. Look above where I placed the <----
I appericate your help in this Bill but I can not find anythign in
Taurus that would link to a bad address. And that error is only when talking to your system, I don't have that issue with any others. At
least the "Bad Address" error in my logs. I'm not sure what to check
next TBH.
May want to read what Nick wrote in a previous message. Seems he's getting a similar message as well. Read his reasoning why with regard
to Argus mailers.
I've follwed your advice and I can connec to Nick's system just fine:
And I don't understand why I am getting a "Bad Addres" from your
system and not from his. TBH, I am not thrilled with Taurus, Radius
or Argus. Although they are Win32 GUI apps, I am inclined, at this
time, to try something different. As I've said before, I have a 50
Node license for IREX and will prolly be setting that up today and
testing it. Lastly, I may shift over to BinkD. Either way, I
think/Hope I can get this fixed so that my system is not falking out
when other connect.
Nicholas Boel wrote to Steven Sheeley <=-
Hello Steven,
On 18 Nov 16 08:31, Steven Sheeley wrote to Bill McGarrity:
I've follwed your advice and I can connec to Nick's system just fine:
And I don't understand why I am getting a "Bad Addres" from your
system and not from his. TBH, I am not thrilled with Taurus, Radius
or Argus. Although they are Win32 GUI apps, I am inclined, at this
time, to try something different. As I've said before, I have a 50
Node license for IREX and will prolly be setting that up today and
testing it. Lastly, I may shift over to BinkD. Either way, I
think/Hope I can get this fixed so that my system is not falking out
when other connect.
I think we may be on to something here. I took a look at my end's logs, and noticed you're only presenting your Agoranet AKA to me when you
poll here. So it seems you're hiding all your other AKAs for our connection.
Whatever you did in regards to our connection, you will most likely
have to do the same with Bill's as he's using the same mailer I am.
You're currently presenting all of your AKAs to him.
Whatever you did in regards to our connection, you will most
likely have to do the same with Bill's as he's using the same
mailer I am. You're currently presenting all of your AKAs to him.
Thank you Nick. When I saw his log to you I noticed that as well.
Was going to write him but you beat me to it.
I think we may be on to something here. I took a look at my end's
logs, and noticed you're only presenting your Agoranet AKA to me when
you poll here. So it seems you're hiding all your other AKAs for our connection.
Whatever you did in regards to our connection, you will most likely
have to do the same with Bill's as he's using the same mailer I am.
You're currently presenting all of your AKAs to him.
Whatever you did in regards to our connection, you will most
likely have to do the same with Bill's as he's using the same
mailer I am. You're currently presenting all of your AKAs to him.
Problem is, I can not find anything in Taurus that allows me to stop
the presenting ok AKAs to a connection. And, since the damn help file
is 90% Russian, I can't look there either. Which is why I am debating about dropping Taurus and moving over to IRex until such time and I
have enough knowledge to pick up the Abandonware that
Argus/Radius/Taurus has been come and release it as Northwind (Or
maybe a kewler name, :) ). \Bottom line is, I can not find the things
in Taurus to really troubleshoot this and I'm sorry.
FYI, Irex and Argus are probably two of the worst mailers still in use today. They were great in their heyday, but most of the newer
softwares out these days have to add a bunch of code to work around a bunch of those two mailer's faults. Irex moreso, since it's not
supported anymore. At least the source for the other one (or one of
it's sisters, Radius or Taurus) is out there. But still hasn't really
been fixed at all.
The only system I am still having issues with is the Necronomicon BBS which is my Net 80 hub.
18-Nov-2016 22:02:51 Begin v5.101/16.02.2009, 19:33 (Winter)
18-Nov-2016 22:02:51 Running under: Windows NT 6.1 (build: 7601,
Service Pack 1) ^ 18-Nov-2016 22:02:51 Connect To 73.219.74.147 #24554
18-Nov-2016 22:02:51 Establishing BinkP transfer protocol
18-Nov-2016 22:02:51 M_NUL : OPT CRAM-MD5-7c6e25ea242c4fa93099620ceabb1fd9 18-Nov-2016 22:02:51 Using
AKAs: 80:304/0 = 18-Nov-2016 22:02:52 Station : Necronomicon BBS = 18-Nov-2016 22:02:52 Address : 21:1/122 9:91/22 46:1/122 44:100/13 24:100/4 57:57/27 42:256/9 719:508/1 618:100/26 40:200/2 411:411/16 316:973/7 1:322/756 80:774/1 637:1/108 432:1/107 39:902/503 21:2/122 314:314/30
: 18-Nov-2016 22:02:52 Number : "necrobbs.strangled.net"
: 18-Nov-2016 22:02:52 Mailer : Mystic/1.12A31 binkp/1.0
18-Nov-2016 22:02:52 Disconnect reason is fatal error
! 18-Nov-2016 22:02:52 Session with 21:1/122 9:91/22 46:1/122
44:100/13 24:100/4 57:57/27 42:256/9 719:508/1 618:100/26 40:200/2 411:411/16 316:973/7 1:322/756 80:774/1 637:1/108 432:1/107 39:902/503 21:2/122 314:314/30 when dialled 80:774/0 - disconnecting *
18-Nov-2016 22:02:52 Session aborted 18-Nov-2016 22:02:52 Session
traf: in: 0 (0b) out: 0 (0b) [461b/657b] 18-Nov-2016 22:02:52 Session time: 00:00:01 18-Nov-2016 22:02:52 End
15 Nov 16 22:06, you wrote to Steven Sheeley:
actually, the sources for all three are available... the bad part is
it is delphi code and so not cross platform... stripping out and converting the winwhatever mess is a huge task
Looks there like you're trying to poll 80:774/0, but the address he's presenting is 80:774/1.
Looks there like you're trying to poll 80:774/0, but the address
he's presenting is 80:774/1.
Ok. Tried polling 80:74/1 and Taurus sits at the negotiation part,
doing not much of anything save trying to negotiate a BinkP
connection.
Hopefully the above was just a typo? That would be 774, and not 74.
Regards,
Nick
Hopefully the above was just a typo? That would be 774, and not
74.
Yep, a typo when I entered the message here. I polled 80:774/1
although, according to the document I received from him when I joined
the network, I am to be polling 80:774/0
Hello Steven,
Then it's possible he has his mailer setup wrong.
actually, the sources for all three are available... the bad part is
it is delphi code and so not cross platform... stripping out and
converting the winwhatever mess is a huge task
I have the source code for all three and have been playing a little
with Taurus. There are a few memory leaks and my knowledge of the FTN protocols are severely lacking but I'm spending time looking and
learning.
Free pascal and the Lazarus IDE do a very good job of converting
Delphi projects.
I've converted the Delphi code of Taurus into a FP/Lazarus project and
am almost to the point where it will compile. My main issue is that
Radius and Taurus are commented in Russian
and the help files are 90% Russian and have been abandoned
which makes it very hard to understand what and why of the coding.
Argus is better but it's severely out dated.
Then it's possible he has his mailer setup wrong.
Actually, there are a bunch of issues with the last copy of the
nodelist that I received for Retronet. Taurus only compiles the first
two parts and leaves the rest. I can browse the nodelist bit don't
even see my node inside Taurus, but it's there in the raw nodelist.
Currently, my hub in Agoranet is the only system that I can not
connect with so I'm tending to believe that I've gotten all of my
issues cleared up.
You're connecting to your Agoranet hub just fine (that's me). :)
Steven Sheeley wrote to Accession <=-
20 Nov 16 08:48, you wrote to me:
You're connecting to your Agoranet hub just fine (that's me). :)
Sorry, fingers got ahead of the brain (Happens quick frequently these days). I meant my Net 80 (Retronet) hub. I'm 80:304/0 and I should be connecting to 80:774/0 and I can't drops with a fatal error.
I still think it's an error in your cfg. It was howing me an aka of 80:304.0 with no domain.May want to delete that address completely
from your cfg file and re-enter it.
You're connecting to your Agoranet hub just fine (that's me). :)
Sorry, fingers got ahead of the brain (Happens quick frequently these days). I meant my Net 80 (Retronet) hub. I'm 80:304/0 and I should be connecting to 80:774/0 and I can't drops with a fatal error.
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495933:47:31 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,919 |