ping? <g>
--- SBBSecho 3.14-Win32
* Origin: The X-Bit BBS - x-bit.org - Forest Grove, Or (1:105/44)

Hi xbit,

On 2023-01-16 09:49:21, you wrote to All:

@MSGID: 144.fidonet_fidotest@1:105/44 282ac4b1
@PID: Synchronet 3.19b-Win32 master/a2a9dc027 Jan 2 2022 MSC 1928
@TZUTC: -0800
@TID: SBBSecho 3.14-Win32 master/a2a9dc027 Jan 2 2022 MSC 1928
@BBSID: XBITBBS
@CHRS: ASCII 1
@NOTE: SlyEdit 1.75 (2021-12-11) (ICE style)
ping? <g>

You're not in the nodelist, and your real name is broken. But other then that your message seems fine. ;-)

--- SBBSecho 3.14-Win32
* Origin: The X-Bit BBS - x-bit.org - Forest Grove, Or (1:105/44) SEEN-BY: 1/123 10/0 1 15/0 90/1 102/401 103/1 705 105/7 10 11 44 81 85 SEEN-BY: 105/500 106/201 120/340 123/131 124/5016 153/757 7715 154/10 SEEN-BY: 203/0 214/22 218/0 1 215 650 700 720 830 840 850 860 870 880 SEEN-BY: 218/900 221/0 226/30 227/114 229/110 111 112 113 114 200 206 SEEN-BY: 229/275 307 317 400 424 426 428 452 470 550 664 700 240/1120 SEEN-BY: 240/5832 266/512 280/464 5003 5555 282/1038 292/854 8125 301/1 SEEN-BY: 301/1 310/31 317/3 320/219 322/757 341/66 234 342/200 396/45 SEEN-BY: 423/120 460/58 633/280 712/848 770/1
@PATH: 105/44 81 229/426 218/700 103/705 280/464

Bye, Wilfred.

--- FMail-lnx64 2.1.5.2-B20230114
* Origin: FMail development HQ (2:280/464)

Re: Re: 1st test from 1:105/44
By: Wilfred van Velzen to xbit on Mon Jan 16 2023 07:08 pm

You're not in the nodelist, and your real name is broken. But other then that your message seems fine. ;-)

Thank you for the pong! Well, so far so "almost good" :)

Hope to be in the node list soon and I should now be posting with real names <g>.

What would be agood echo to post fido newbie Q&A's?
--- SBBSecho 3.14-Win32
* Origin: The X-Bit BBS - x-bit.org - Forest Grove, Or (1:105/44)

ping? <g>

@SEEN-BY: 1/123 10/0 1 15/0 90/1 102/401 103/1 705 105/7 10 11 44 81 85 500 @SEEN-BY: 106/201 120/340 123/131 124/5016 153/757 7715 154/10 203/0 214/22 @SEEN-BY: 218/0 1 215 650 700 720 830 840 850 860 870 880 900 221/0 226/30 @SEEN-BY: 227/114 229/110 111 112 113 114 200 206 275 307 317 400 424 426 428 @SEEN-BY: 229/452 470 550 664 700 240/1120 5832 266/512 280/464 5003 5555 @SEEN-BY: 282/1038 292/854 8125 301/1 310/31 317/3 320/219 322/757 341/66 234 @SEEN-BY: 342/200 396/45 423/120 460/58 633/280 712/848 770/1
@PATH: 105/44 81 229/426 218/700 103/705 280/464 153/757
@TZUTC: -0800
@MSGID: 144.fidonet_fidotest@1:105/44 282ac4b1
@PID: Synchronet 3.19b-Win32 master/a2a9dc027 Jan 2 2022 MSC 1928
@TID: SBBSecho 3.14-Win32 master/a2a9dc027 Jan 2 2022 MSC 1928
@BBSID: XBITBBS
@CHRS: ASCII 1
@NOTE: SlyEdit 1.75 (2021-12-11) (ICE style)

That's what I see here, looks good.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hi Rob,

On 2023-01-16 11:17:19, you wrote to me:

You're not in the nodelist, and your real name is broken. But other
then that your message seems fine. ;-)

Thank you for the pong! Well, so far so "almost good" :)

Hope to be in the node list soon and I should now be posting with real names <g>.

Yes. Thanks! ;)

What would be agood echo to post fido newbie Q&A's?

FN_SYSOP probably. Or 1 of the synchronet areas if they are specific to synchronet.

Bye, Wilfred.

--- FMail-lnx64 2.1.5.2-B20230114
* Origin: FMail development HQ (2:280/464)

Hi xbit!

16 Jan 2023 09:49, from xbit -> All:

@TZUTC: -0800
@MSGID: 144.fidonet_fidotest@1:105/44 282ac4b1
@PID: Synchronet 3.19b-Win32 master/a2a9dc027 Jan 2 2022 MSC 1928
@TID: SBBSecho 3.14-Win32 master/a2a9dc027 Jan 2 2022 MSC 1928
@CHRS: ASCII 1
@NOTE: SlyEdit 1.75 (2021-12-11) (ICE style)
ping? <g>
SEEN-BY: 1/123 10/0 1 15/0 90/1 102/401 103/1 705 105/7 10 11 44 81 85 SEEN-BY: 105/500 106/201 120/340 123/131 124/5016 153/757 7715 154/10 SEEN-BY: 203/0 214/22 218/0 1 215 650 700 720 830 840 850 860 870 880 SEEN-BY: 218/900 221/0 226/30 227/114 229/110 111 112 113 114 200 206 SEEN-BY: 229/275 307 317 400 424 426 428 452 470 550 664 700 240/1120 SEEN-BY: 240/5832 266/512 280/464 5003 5555 282/1038 292/854 8125
301/1
SEEN-BY: 301/1 310/31 317/3 320/219 322/757 341/66 234 342/200 396/45 SEEN-BY: 423/120 460/58 633/280 712/848 770/1
@PATH: 105/44 81 229/426 218/700 103/705 280/464

CU, Ricsi

... Some people stand for nothing because they fall for everything.
--- GoldED+/LNX
* Origin: Apes evolved from Creationists! (2:310/31)

Hello xbit,

16 Jan 23 09:49, you wrote to All:

@TZUTC: -0800
@MSGID: 144.fidonet_fidotest@1:105/44 282ac4b1
@PID: Synchronet 3.19b-Win32 master/a2a9dc027 Jan 2 2022 MSC 1928
@TID: SBBSecho 3.14-Win32 master/a2a9dc027 Jan 2 2022 MSC 1928
@BBSID: XBITBBS
@CHRS: ASCII 1
@NOTE: SlyEdit 1.75 (2021-12-11) (ICE style)
ping? <g>
--- SBBSecho 3.14-Win32
* Origin: The X-Bit BBS - x-bit.org - Forest Grove, Or (1:105/44)
SEEN-BY: 30/0 221/1 240/1120 1634 8002 8005 280/464 5003 291/111 301/1 313/41
SEEN-BY: 335/364 371/0 52 382/147 530/204 3634/12
@PATH: 105/44 81 229/426 153/7715 3634/12 240/1120 371/0

Regards,
--
dp

telnet://bbs.roonsbbs.hu:1212 <<=-

... 9:01pm up 21 days, 23:08:12, load: 76 processes, 278 threads.
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY (2:371/52)

Hello Rob,

On Monday January 16 2023 11:17, you wrote to Wilfred van Velzen:

Hope to be in the node list soon and I should now be posting with real names <g>.

Your real name is fine now and you are in the nodelist. I fail to make a connect however:

12:23 [1124] creating a poll for 1:105/44@fidonet (`d' flavour)
12:23 [1124] clientmgr started
+ 12:23 [2880] call to 1:105/44@fidonet
12:23 [2880] trying x-bit.org [50.109.246.145]:24556...
? 12:24 [2880] connection to 1:105/44@fidonet failed: {W32 API error
10060} Connection timed out
12:24 [1124] the queue is empty, quitting...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Meten is weten, testen is verpesten (2:280/5555)

20 Jan 2023 12:24, Michiel van der Vlist wrote to you:

Your real name is fine now and you are in the nodelist. I fail to make
a connect however:

I tried some minutes ago and connected successfully.

Welcome!

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234)

Hello Carlos,

On Friday January 20 2023 13:21, you wrote to Rob McGee:

20 Jan 2023 12:24, Michiel van der Vlist wrote to you:

Your real name is fine now and you are in the nodelist. I fail to
make a connect however:

I tried some minutes ago and connected successfully.

Odd, I still get a time out.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Meten is weten, testen is verpesten (2:280/5555)

Re: 1st test from 1:105/44
By: Michiel van der Vlist to Rob McGee on Fri Jan 20 2023 12:24 pm

Your real name is fine now and you are in the nodelist. I fail to make a connect however:

Good news that I'm in the node list, woop! Thanks to Rick for all the help getting it going.

As for the connection, its open and packets are flowing with my hub. But I do have your geo location blocked. When i was first setting up my Spitfire BBS using NetSerial a year ago i was getting a number of bots from that location and it was crashing Spitfire so I may have got overly aggressive.

I just put a few IP's on a whitelist so perhaps its working now?
--- SBBSecho 3.14-Win32
* Origin: The X-Bit BBS - x-bit.org - Forest Grove, Or (1:105/44)

Hi Michiel,

On 2023-01-20 13:34:07, you wrote to Carlos Navarro:

Your real name is fine now and you are in the nodelist. I fail to
make a connect however:

I tried some minutes ago and connected successfully.

MvdV> Odd, I still get a time out.

The same here. There is nothing on the IP, can't even ping it...


Bye, Wilfred.

--- FMail-lnx64 2.1.5.2-B20230114
* Origin: FMail development HQ (2:280/464)

Re: 1st test from 1:105/44
By: Carlos Navarro to Rob McGee on Fri Jan 20 2023 01:21 pm

I tried some minutes ago and connected successfully.
Welcome!

Awesome, and thank you!
--- SBBSecho 3.14-Win32
* Origin: The X-Bit BBS - x-bit.org - Forest Grove, Or (1:105/44)

Hello Rob,

On Friday January 20 2023 04:36, you wrote to me:

As for the connection, its open and packets are flowing with my hub.
But I do have your geo location blocked. When i was first setting up
my Spitfire BBS using NetSerial a year ago i was getting a number of
bots from that location and it was crashing Spitfire so I may have got overly aggressive.

I just put a few IP's on a whitelist so perhaps its working now?

Yes, I can connect now:

+ 13:58 [3224] call to 1:105/44@fidonet
13:58 [3224] trying x-bit.org [50.109.246.145]:24556...
13:58 [3224] connected
+ 13:58 [3224] outgoing session with x-bit.org:24556 [50.109.246.145]
- 13:58 [3224] OPT CRAM-MD5-975f228524d39604555adff619da654b CRYPT
+ 13:58 [3224] Remote requests MD mode
+ 13:58 [3224] Remote requests CRYPT mode
- 13:58 [3224] SYS The X-BIT BBS
- 13:58 [3224] ZYZ Rob McGee
- 13:58 [3224] LOC Portland, Oregon
- 13:58 [3224] NDL 115200,TCP,BINKP
- 13:58 [3224] TIME Fri Jan 20 2023 04:58:06 GMT-0800 (Pacific Standard Time)
- 13:58 [3224] VER BinkIT/2.41,JSBinkP/4,sbbs3.19b/Win32 binkp/1.1
+ 13:58 [3224] addr: 1:105/44@fidonet
+ 13:58 [3224] done (to 1:105/44@fidonet, OK, S/R: 0/0 (0/0 bytes))
13:58 [3224] session closed, quitting...
13:58 [2700] the queue is empty, quitting...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Meten is weten, testen is verpesten (2:280/5555)

Hi Rob,

On 2023-01-20 13:58:44, Michiel van der Vlist wrote to you:

I just put a few IP's on a whitelist so perhaps its working now?

MvdV> Yes, I can connect now:

MvdV> + 13:58 [3224] call to 1:105/44@fidonet
MvdV> 13:58 [3224] trying x-bit.org [50.109.246.145]:24556...
MvdV> 13:58 [3224] connected

I still can't. :-( ;-)

To do it right all fidonet nodes (and points) should be able to deliver crashmail. As you can't know all their IP adresses, it would be best if at least your binkp port is open to the world...

Bye, Wilfred.

--- FMail-lnx64 2.1.5.2-B20230114
* Origin: FMail development HQ (2:280/464)

Re: Re: 1st test from 1:105/44
By: Wilfred van Velzen to Rob McGee on Fri Jan 20 2023 02:09 pm

I just put a few IP's on a whitelist so perhaps its working now?

To do it right all fidonet nodes (and points) should be able to deliver crashmail. As you can't know all their IP adresses, it would be best if at least your binkp port is open to the world...

Good call <g>. That would be quite a bit of work for everyone if I asked for all nodes to please send me your static <g>.

Working now on allowing my binkp port.
--- SBBSecho 3.14-Win32
* Origin: The X-Bit BBS - x-bit.org - Forest Grove, Or (1:105/44)

Hello Wilfred!

** On Friday 20.01.23 - 14:09, Wilfred van Velzen wrote to Rob McGee:

I just put a few IP's on a whitelist so perhaps its working now?

MvdV> Yes, I can connect now:

MvdV> + 13:58 [3224] call to 1:105/44@fidonet
MvdV> 13:58 [3224] trying x-bit.org [50.109.246.145]:24556...
MvdV> 13:58 [3224] connected

I still can't. :-( ;-)

To do it right all fidonet nodes (and points) should be able to deliver crashmail. As you can't know all their IP adresses, it would be best if at least your binkp port is open to the world...

Worked for me..

= 08:51:21 CONNECT
08:51:21 OPT CRAM-MD5-7a9d0d508877a68ca842dd7058fc3e73 CRYPT
08:51:22 SYS The X-BIT BBS
08:51:22 ZYZ Rob McGee
08:51:22 LOC Portland, Oregon
08:51:22 NDL 115200,TCP,BINKP
08:51:22 TIME Fri Jan 20 2023 05:51:21 GMT-0800 (Pacific Standard Time)
08:51:22 VER BinkIT/2.41,JSBinkP/4,sbbs3.19b/Win32 binkp/1.1
08:51:23 non-secure
* 08:51:24 Sent 20085120.PKT, 324b
= 08:51:25 hangup
- 08:51:25 exiting

--
../|ug

--- OpenXP 5.0.51
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)

Hi August,

On 2023-01-20 08:53:00, you wrote to me:

I just put a few IP's on a whitelist so perhaps its working now?

MvdV> Yes, I can connect now:

MvdV> + 13:58 [3224] call to 1:105/44@fidonet
MvdV> 13:58 [3224] trying x-bit.org [50.109.246.145]:24556...
MvdV> 13:58 [3224] connected

I still can't. :-( ;-)

To do it right all fidonet nodes (and points) should be able to
deliver crashmail. As you can't know all their IP adresses, it would
be best if at least your binkp port is open to the world...

Worked for me..

= 08:51:21 CONNECT

Apparently you're in trusted territory... ;-)

Bye, Wilfred.

--- FMail-lnx64 2.1.5.2-B20230114
* Origin: FMail development HQ (2:280/464)

Hi Rob,

On 2023-01-20 05:39:46, you wrote to me:

To do it right all fidonet nodes (and points) should be able to
deliver crashmail. As you can't know all their IP adresses, it would
be best if at least your binkp port is open to the world...

Good call <g>. That would be quite a bit of work for everyone if I asked for all nodes to please send me your static <g>.

Working now on allowing my binkp port.

I can now connect on your 24556 port!

Bye, Wilfred.

--- FMail-lnx64 2.1.5.2-B20230114
* Origin: FMail development HQ (2:280/464)

Re: Re: 1st test from 1:105/44
By: Wilfred van Velzen to August Abolins on Fri Jan 20 2023 03:04 pm

Worked for me..
= 08:51:21 CONNECT

Apparently you're in trusted territory... ;-)
Bye, Wilfred.

Is it still a no go for you? I pushed a rule whitelisting my binkp.
--- SBBSecho 3.14-Win32
* Origin: The X-Bit BBS - x-bit.org - Forest Grove, Or (1:105/44)

Hi Rob,

On 2023-01-20 06:18:24, you wrote to me:

Worked for me..
= 08:51:21 CONNECT

Apparently you're in trusted territory... ;-)
Bye, Wilfred.

Is it still a no go for you? I pushed a rule whitelisting my binkp.

Yep it works now for me, see my previous message...

Bye, Wilfred.

--- FMail-lnx64 2.1.5.2-B20230114
* Origin: FMail development HQ (2:280/464)

Re: 1st test from 1:105/44
By: August Abolins to Wilfred van Velzen on Fri Jan 20 2023 08:53 am

Worked for me..

I got the crash but when i replied I received the following:

BINKPOLL JSBinkP/4 callout to 2:221/1.58@fidonet started
BINKPOLL Connecting to 2:221/1.58@fidonet at p58.f1.n221.z2.binkp.net:24554 BINKPOLL Connection to p58.f1.n221.z2.binkp.net:24554 failed (Error: No such host is known.)
--- SBBSecho 3.14-Win32
* Origin: The X-Bit BBS - x-bit.org - Forest Grove, Or (1:105/44)

Re: Re: 1st test from 1:105/44
By: Wilfred van Velzen to Rob McGee on Fri Jan 20 2023 03:11 pm

Working now on allowing my binkp port.

I can now connect on your 24556 port!

Very nice! I was blocking all people with the name "wilfred" on the firewall ;) fixed <g>.
--- SBBSecho 3.14-Win32
* Origin: The X-Bit BBS - x-bit.org - Forest Grove, Or (1:105/44)

Re: Re: 1st test from 1:105/44
By: Wilfred van Velzen to Rob McGee on Fri Jan 20 2023 03:27 pm

Is it still a no go for you? I pushed a rule whitelisting my
binkp.

Yep it works now for me, see my previous message...

Got it.. thanks for all the help team.
--- SBBSecho 3.14-Win32
* Origin: The X-Bit BBS - x-bit.org - Forest Grove, Or (1:105/44)

Re: Re: 1st test from 1:105/44
By: Wilfred van Velzen to Rob McGee on Fri Jan 20 2023 02:09 pm

To do it right all fidonet nodes (and points) should be able to deliver crashmail. As you can't know all their IP adresses, it would be best if at least your binkp port is open to the world...

This gave me a good idea.. I'm now allowing my binkp port as well as tcp/23 for telnet access to my synchronet and fido bbs. The reason I got so aggressive with geo blocking is because of my Spitfire BBS that would crash when pushed with bots.

That said, Synchronet is much more stable when it comes to that so I can open up the telnet port to it.. just not tcp/2323 for Spitfire and netserial. One can still access Spitfire from inside x-bit using the *telgate app that's setup for it.

Thanks again all for the help with testing. Happy weekend!
--- SBBSecho 3.14-Win32
* Origin: The X-Bit BBS - x-bit.org - Forest Grove, Or (1:105/44)

Hi Rob,

On 2023-01-20 07:30:42, you wrote to me:

I'm now allowing my binkp port as well as tcp/23 for telnet access to
my synchronet and fido bbs. The reason I got so aggressive with geo blocking is because of my Spitfire BBS that would crash when pushed
with bots.

I wouldn't run telnet on the default port. It's not a real security measure, but it helps to keep your log file not blowing up! ;-)

Bye, Wilfred.

--- FMail-lnx64 2.1.5.2-B20230114
* Origin: FMail development HQ (2:280/464)

Re: 1st test from 1:105/44
By: August Abolins to Wilfred van Velzen on Fri Jan 20 2023 08:53 am

Worked for me..

I got the crash but when i replied I received the following:

BINKPOLL JSBinkP/4 callout to 2:221/1.58@fidonet started
BINKPOLL Connecting to 2:221/1.58@fidonet at p58.f1.n221.z2.binkp.net:24554 BINKPOLL Connection to p58.f1.n221.z2.binkp.net:24554 failed (Error: No such host is known.)

that's probably because a point is not usually accessible directly like that ;)

--- AfterShock/Android 1.6.8
* Origin: Mobile Blackberry Q10 (4:920/1.58)

Re: 1st test from 1:105/44
By: August Abolins to Rob McGee on Fri Jan 20 2023 10:47 am

that's probably because a point is not usually accessible directly like that ;)

Good point.. still "re"learning.
--- SBBSecho 3.14-Win32
* Origin: The X-Bit BBS - x-bit.org - Forest Grove, Or (1:105/44)

Hello Rob!

that's probably because a point is not usually accessible
directly like that ;)

Good point.. still "re"learning.

But, a crashmail reply to my Boss system ought to work.

--
../|ug

--- OpenXP 5.0.51
* Origin: The ONLY point that matters --> . <-- (1:153/757.21)