Test 1....2......3.....10.....HUT HUT!!



--- ENiGMA 1/2 v0.0.10-alpha (linux; x64; 10.15.3)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16)

Test 1....2......3.....10.....HUT HUT!!

Recieved here.. :)

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

Hi KrUpTiOn.

18 Apr 19 02:38, you wrote to All:

@MSGID: 9408.fidotest@1:226/16 7b2bb1c6
@TZUTC: -0400
@TID: ENiGMA1/2 0.0.10.a (linux; x64; 10.15.3)
@CHRS: UTF-8 4
Test 1....2......3.....10.....HUT HUT!!

Check!

--- ENiGMA 1/2 v0.0.10-alpha (linux; x64; 10.15.3)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16) SEEN-BY: 15/2 18/200 103/705 123/1970 154/10 203/0 221/0 1 6 360 226/16 17 SEEN-BY: 229/107 200 354 426 452 1014 240/1120 5832 249/206 307 317 400 SEEN-BY: 280/464 5003 5555 310/31 317/3 322/757 342/200 393/68 396/45 423/120 SEEN-BY: 712/848 770/1 2452/250 3828/7
@PATH: 226/16 229/426 280/464 221/1

'Tommi

--- GoldED+/LNX 1.1.5-b20180707
* Origin: rpi.rbb.bbs.fi (2:221/1)

Hi KrUpTiOn,

No real name...

On 2019-04-18 02:38:46, you wrote to All:

@MSGID: 9408.fidotest@1:226/16 7b2bb1c6
@TZUTC: -0400
@TID: ENiGMA1/2 0.0.10.a (linux; x64; 10.15.3)
@CHRS: UTF-8 4
Test 1....2......3.....10.....HUT HUT!!

--- ENiGMA 1/2 v0.0.10-alpha (linux; x64; 10.15.3)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16) SEEN-BY: 15/2 18/200 103/705 123/1970 154/10 203/0 221/0 226/16 17 229/107 SEEN-BY: 229/200 354 426 452 1014 240/5832 249/206 307 317 400 280/464 SEEN-BY: 280/5003 5555 310/31 317/3 322/757 342/200 393/68 396/45 423/120 SEEN-BY: 712/848 770/1 2452/250 3828/7
@PATH: 226/16 229/426 280/464

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi KrUpTiOn.

18 Apr 19 10:35:30, Wilfred van Velzen wrote to you:

Hi KrUpTiOn,

No real name...

And no connection...

=== Cut ===
18 Apr 12:34:20 [9474] creating a poll for 1:226/16@fidonet (`d' flavour)
18 Apr 12:34:20 [9474] clientmgr started
18 Apr 12:34:20 [9475] call to 1:226/16@fidonet
18 Apr 12:34:20 [9475] trying f16.n226.z1.binkp.net [98.124.199.3]...
18 Apr 12:34:21 [9475] connection to 1:226/16@fidonet failed: Connection refused
18 Apr 12:34:21 [9474] rc(9475)=0
18 Apr 12:34:21 [9474] the queue is empty, quitting...
=== Cut ===

'Tommi

... \\COW has been up for: 30 day(s), 14 hour(s), 20 minute(s), 4 second(s)
---
* Origin: 2001:470:1f15:cb0:f1d0:2:221:6 (2:221/6)

On 2019 Apr 18 02:38:46, you wrote to All:

@MSGID: 9408.fidotest@1:226/16 7b2bb1c6
@TZUTC: -0400
@TID: ENiGMA1/2 0.0.10.a (linux; x64; 10.15.3)
@CHRS: UTF-8 4
Test 1....2......3.....10.....HUT HUT!!

--- ENiGMA 1/2 v0.0.10-alpha (linux; x64; 10.15.3)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16) SEEN-BY: 15/2 18/200 103/705 123/1970 154/10 203/0 221/0 1 6 360 226/16 17 SEEN-BY: 229/107 200 354 426 452 1014 240/1120 5832 249/206 307 317 400 SEEN-BY: 280/464 5003 5555 310/31 317/3 320/119 219 322/757 342/200 393/68 SEEN-BY: 396/45 423/120 640/1321 1384 712/848 770/1 2452/250 3634/12

3828/7

SEEN-BY: 116/116 123/25 150 755 135/300 153/7715 154/10 261/38 3634/15 24 27
SEEN-BY: 3634/50 119 123/50 115 3634/12 0 18/0 123/0 1/120
@PATH: 226/16 229/426 280/464 221/1 640/1384 3634/12

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Birth: The first and direst of all disasters.
---
* Origin: (1:3634/12.73)

On 2019 Apr 18 12:40:06, you wrote to KrUpTiOn:

Hi KrUpTiOn,

No real name...

And no connection...

=== Cut ===
18 Apr 12:34:20 [9474] creating a poll for 1:226/16@fidonet (`d' flavour)

valid node number...

18 Apr 12:34:20 [9474] clientmgr started
18 Apr 12:34:20 [9475] call to 1:226/16@fidonet
18 Apr 12:34:20 [9475] trying f16.n226.z1.binkp.net [98.124.199.3]...

i get the same IP for the listed newfrontier.net... possbly they had their mailer down while doing work on it when you attempted your connection? is that UTC or local time stamps?

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Upgrades will continue until the hardware won't run it.
---
* Origin: (1:3634/12.73)

Hi mark,

On 2019-04-18 11:22:36, you wrote to Tommi Koivula:

18 Apr 12:34:20 [9474] clientmgr started
18 Apr 12:34:20 [9475] call to 1:226/16@fidonet
18 Apr 12:34:20 [9475] trying f16.n226.z1.binkp.net [98.124.199.3]...

i get the same IP for the listed newfrontier.net... possbly they had their mailer down while doing work on it when you attempted your connection? is that UTC or local time stamps?

Still the same:

+ 18 Apr 17:41:03 [30332] call to 1:226/16@fidonet
18 Apr 17:41:03 [30332] trying newfrontier.net [98.124.199.3]...
? 18 Apr 17:41:03 [30332] connection to 1:226/16@fidonet failed: Connection refused

(This is local time, which is UTC+2)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi mark.

18 Apr 19 11:22, you wrote to me:

No real name...

And no connection...

=== Cut ===
18 Apr 12:34:20 [9474] creating a poll for 1:226/16@fidonet (`d' flavour)

valid node number...

18 Apr 12:34:20 [9474] clientmgr started
18 Apr 12:34:20 [9475] call to 1:226/16@fidonet
18 Apr 12:34:20 [9475] trying f16.n226.z1.binkp.net [98.124.199.3]...

i get the same IP for the listed newfrontier.net... possbly they had their mailer down while doing work on it when you attempted your connection?

The .dlo is still there...

=== Cut ===
? 18 Apr 12:34:21 [9475] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 12:34:24 [9476] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 12:44:24 [10121] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 12:46:24 [10250] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 12:56:26 [10867] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 12:58:26 [10943] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 13:08:26 [11662] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 13:10:27 [11861] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 13:20:28 [12616] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 13:22:29 [12639] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 13:32:31 [13163] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 13:34:31 [13234] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 13:44:32 [13829] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 13:46:33 [13997] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 13:56:34 [22121] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 13:58:34 [22250] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 14:08:35 [23026] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 14:10:35 [23159] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 14:20:36 [23721] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 14:22:36 [23734] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 14:32:39 [24307] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 14:34:39 [24322] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 14:44:40 [24799] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 14:46:40 [24955] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 14:56:41 [25682] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 14:58:41 [25821] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 15:08:42 [26522] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 15:10:42 [26624] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 15:20:44 [26994] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 15:22:44 [27104] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 15:32:47 [27639] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 15:34:47 [27648] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 15:44:49 [27988] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 15:46:49 [28049] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 15:56:50 [28530] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 15:58:51 [28658] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 16:08:52 [29125] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 16:10:52 [29283] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 16:20:52 [29847] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 16:22:53 [29935] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 16:32:55 [30230] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 16:34:56 [30344] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 16:44:56 [30802] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 16:46:57 [30876] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 16:56:58 [31170] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 16:58:58 [31214] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 17:08:59 [31659] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 17:10:59 [31793] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 17:21:00 [32527] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 17:23:00 [32578] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 17:33:02 [541] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 17:35:03 [684] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 17:45:03 [1039] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 17:47:03 [1102] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 17:57:04 [1355] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 17:59:05 [1419] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 18:09:06 [1795] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 18:11:06 [1879] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 18:21:07 [2286] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 18:23:08 [2387] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 18:33:08 [3276] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 18:35:09 [3346] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 18:45:09 [3903] connection to 1:226/16@fidonet failed: Connection refused
? 18 Apr 18:47:10 [3991] connection to 1:226/16@fidonet failed: Connection refused
=== Cut ===

is
that UTC or local time stamps?

Local. It's now almost 7 pm finnish summertime.

'Tommi

--- GoldED+/LNX 1.1.5-b20180707
* Origin: nntps://news.fidonet.fi (2:221/1)

Hi Tommi,

On 2019-04-18 18:52:18, you wrote to mark lewis:

=== Cut ===
18 Apr 12:34:20 [9474] creating a poll for 1:226/16@fidonet (`d'
flavour)

valid node number...

18 Apr 12:34:20 [9474] clientmgr started
18 Apr 12:34:20 [9475] call to 1:226/16@fidonet
18 Apr 12:34:20 [9475] trying f16.n226.z1.binkp.net [98.124.199.3]...

i get the same IP for the listed newfrontier.net... possbly they had
their mailer down while doing work on it when you attempted your
connection?

The .dlo is still there...

And 2 days later it's still in my outbound...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi Wilfred.

20 Apr 19 18:13, you wrote to me:

Hi Tommi,

On 2019-04-18 18:52:18, you wrote to mark lewis:

=== Cut ===
18 Apr 12:34:20 [9474] creating a poll for 1:226/16@fidonet (`d'
flavour)

valid node number...

18 Apr 12:34:20 [9474] clientmgr started
18 Apr 12:34:20 [9475] call to 1:226/16@fidonet
18 Apr 12:34:20 [9475] trying f16.n226.z1.binkp.net [98.124.199.3]...

i get the same IP for the listed newfrontier.net... possbly they had
their mailer down while doing work on it when you attempted your
connection?

The .dlo is still there...

And 2 days later it's still in my outbound...

Yes. Still "doing work on it".

Sad.

'Tommi

--- GoldED+/LNX 1.1.5-b20180707
* Origin: ------------------------------------------------ (2:221/1)

Test 1....2......3.....10.....HUT HUT!!

Check!


Saludos.
Gaston Martres

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Zooropa BBS (4:900/108)

On Apr 20th 6:00 pm Gaston Martres said...

Test 1....2......3.....10.....HUT HUT!!

Check!

I NOW fixed my problem, I was trying to figure out how to display real names in
FidoNet in Enigma. :)



--- ENiGMA 1/2 v0.0.10-alpha (linux; x64; 10.15.2)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16)

Hi Tommi,

On 2019-04-20 19:28:20, you wrote to me:

18 Apr 12:34:20 [9474] clientmgr started
18 Apr 12:34:20 [9475] call to 1:226/16@fidonet
18 Apr 12:34:20 [9475] trying f16.n226.z1.binkp.net
[98.124.199.3]...

i get the same IP for the listed newfrontier.net... possbly they had
their mailer down while doing work on it when you attempted your
connection?

The .dlo is still there...

And 2 days later it's still in my outbound...

Yes. Still "doing work on it".

The files are still in my outbound... But I'm going to delete them.

Btw: His second system 1:226/17 is connectable:

+ 01 May 08:56:49 [13721] call to 1:226/17@fidonet
01 May 08:56:49 [13721] trying frontierbbs.net [76.188.66.199]:24556...
01 May 08:56:49 [13721] connected
+ 01 May 08:56:49 [13721] outgoing session with frontierbbs.net:24556 [76.188.66.199]
- 01 May 08:56:49 [13721] OPT CRAM-MD5-3163dff974502d29a534d58f01d67acb CRYPT
+ 01 May 08:56:49 [13721] Remote requests MD mode
+ 01 May 08:56:49 [13721] Remote requests CRYPT mode
- 01 May 08:56:49 [13721] SYS The New Frontier ][ BBS
- 01 May 08:56:49 [13721] ZYZ Charles Stephenson
- 01 May 08:56:49 [13721] LOC Akron, Ohio
- 01 May 08:56:49 [13721] NDL 115200,TCP,BINKP
- 01 May 08:56:49 [13721] TIME Wed May 01 2019 02:56:49 GMT-0400 (EDT)
- 01 May 08:56:49 [13721] VER BinkIT/2.17,JSBinkP/1.114,sbbs3.17c/Linux binkp/1.1
+ 01 May 08:56:49 [13721] addr: 1:226/17@fidonet
+ 01 May 08:56:49 [13721] addr: 21:2/105@fsxnet (n/a or busy)
+ 01 May 08:56:49 [13721] addr: 40:300/0@cybernet (n/a or busy)
+ 01 May 08:56:49 [13721] addr: 40:300/1@cybernet (n/a or busy)
+ 01 May 08:56:49 [13721] addr: 44:100/22@dorenet (n/a or busy)
+ 01 May 08:56:49 [13721] addr: 901:1/17@dixienet (n/a or busy)
+ 01 May 08:56:49 [13721] addr: 40:100/109@cybernet (n/a or busy)
+ 01 May 08:56:49 [13721] addr: 64:500/13@cnet (n/a or busy)
+ 01 May 08:56:49 [13721] addr: 411:411/38@combatnt (n/a or busy)
+ 01 May 08:56:49 [13721] addr: 40:100/22@cybernet (n/a or busy)
+ 01 May 08:56:49 [13721] done (to 1:226/17@fidonet, OK, S/R: 0/0 (0/0 bytes))
01 May 08:56:49 [13721] session closed, quitting...


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

On Wed, 1 May 2019 06:19:42 +0200
"Wilfred van Velzen -> Tommi Koivula" <2:280/464> wrote:

TK>>>>> 18 Apr 12:34:20 [9474] clientmgr started
TK>>>>> 18 Apr 12:34:20 [9475] call to 1:226/16@fidonet
TK>>>>> 18 Apr 12:34:20 [9475] trying f16.n226.z1.binkp.net
TK>>>>> [98.124.199.3]...

>>>> i get the same IP for the listed newfrontier.net... possbly they had
>>>> their mailer down while doing work on it when you attempted your
>>>> connection?

TK>>> The .dlo is still there...

>> And 2 days later it's still in my outbound...

TK> Yes. Still "doing work on it".

The files are still in my outbound... But I'm going to delete them.

Might be a good thing to do...

Btw: His second system 1:226/17 is connectable:

That doesn't help if mail goes to the other one. ;)

--
Tommi

--- Sylpheed 3.5.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
* Origin: smapinntpd/linux @ nntps://news.fidonet.fi (2:221/1)

On 2019 May 02 20:30:18, you wrote to Wilfred van Velzen:

Btw: His second system 1:226/17 is connectable:

That doesn't help if mail goes to the other one. ;)

it might if it is routed thru the connectable one and if they have routing working between their two systems...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Moderator.. Kinda like a Sysop, only more arrogant.
---
* Origin: (1:3634/12.73)

Hello, mark lewis
On 03/05/2019 3.09 you wrote:

On 2019 May 02 20:30:18, you wrote to Wilfred van Velzen:

Btw: His second system 1:226/17 is connectable:

That doesn't help if mail goes to the other one. ;)

it might if it is routed thru the connectable one and if they have
routing working between their two systems...

Crashmail does not work that way. It goes directly to the destination by the nodelist.

--
Tommi

--- HotdogEd/2.13.5 (Android; Google Android; rv:1) Hotdoged/1552284388000 Hotd
* Origin: - nntp://rbb.fidonet.fi - Lake Ylo - Finland - (2:221/360)

On 2019 May 03 05:46:26, you wrote to me:

Btw: His second system 1:226/17 is connectable:

That doesn't help if mail goes to the other one. ;)

it might if it is routed thru the connectable one and if they have
routing working between their two systems...

Crashmail does not work that way. It goes directly to the destination
by the nodelist.

of course but you can reroute it easily enough... either remove the crash bit (dynamic mailer) or rename the flo file...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... I brought you to a Remington party and what's my thanks?
---
* Origin: (1:3634/12.73)

On May 1st 3:47 am Wilfred van Velzen said...

12:34:20 [9475] call to 1:226/16@fidonet TK>>>>> 18 Apr 12:34:20 [9475] trying f16.n226.z1.binkp.net TK>>>>> [98.124.199.3]...

i get the same IP for the listed newfrontier.net... possbly they had >>>> their mailer down while doing work on it when you attempted your >>>> connection?

It's 'frontierbbs.net' 1:226/16 is the default Bink port. (BinkD) (BBS Name "The Amiga Frontier BBS) (frontierbbs.net:8888) "

1:226/17 - frontierbbs.net:24556/binkit

The .dlo is still there...

And 2 days later it's still in my outbound...

Yes. Still "doing work on it".

+ 01 May 08:56:49 [13721] call to 1:226/17@fidonet 01 May 08:56:49 [13721] trying frontierbbs.net [76.188.66.199]:24556... 01 May 08:56:49 [13721] connected + 01 May 08:56:49 [13721] outgoing session with frontierbbs.net:24556 [76.188.66.199] - 01 May 08:56:49 [13721] OPT CRAM-MD5-3163dff974502d29a534d58f01d67acb CRYPT + 01 May 08:56:49 [13721] Remote requests MD mode + 01 May 08:56:49 [13721] Remote requests CRYPT

You might have tried to connect while I was doing some upgrading. Both systems
have been running about 90% uptime over the last month. I might have been down 1 entire day, twice in the last 2 months. Both run around 6-7 days continuously
before I reboot to clear things up.



--- ENiGMA 1/2 v0.0.10-alpha (linux; x64; 10.15.2)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16)

03 May 19 19:23, KrUpTiOn wrote to Wilfred van Velzen:

The .dlo is still there...

And 2 days later it's still in my outbound...

Yes. Still "doing work on it".

+ 01 May 08:56:49 [13721] call to 1:226/17@fidonet 01 May 08:56:49
[13721] trying frontierbbs.net [76.188.66.199]:24556... 01 May 08:56:49
[13721] connected + 01 May 08:56:49 [13721] outgoing session with
frontierbbs.net:24556 [76.188.66.199] - 01 May 08:56:49 [13721] OPT
CRAM-MD5-3163dff974502d29a534d58f01d67acb CRYPT + 01 May 08:56:49 [13721]
Remote requests MD mode + 01 May 08:56:49 [13721] Remote requests CRYPT

You might have tried to connect while I was doing some upgrading. Both systems have been running about 90% uptime over the last month. I might have been down 1 entire day, twice in the last 2 months. Both run around 6-7 days continuously before I reboot to clear things up.

Well then you may have a firewall or something blocking our connections. It is still not working:

08:08 [1128] BEGIN, binkd/1.1a-99/CYGWIN_NT-6.1 -p -P 1:226/16 binkd.cfg
08:08 [1128] Cannot find domain for zone 1, assuming 'fidonet'
08:08 [1128] creating a poll for 1:226/16@fidonet (`d' flavour)
08:08 [1128] clientmgr started
08:08 [7172] call to 1:226/16@fidonet
08:08 [7172] trying newfrontier.net [98.124.199.3]...
08:08 [7172] connection to 1:226/16@fidonet failed: Connection refused
08:08 [1128] rc(7172)=0
08:08 [1128] the queue is empty, quitting...

'Tommi

---
* Origin: 2001:470:1f15:cb0:f1d0:2:221:1 (2:221/1)

Hi KrUpTiOn,

Real names please, Charles.

On 2019-05-03 19:23:40, you wrote to me:

It's 'frontierbbs.net' 1:226/16 is the default Bink port.

I only get a timeout there:

# telnet frontierbbs.net binkp
Trying 76.188.66.199...
telnet: connect to address 76.188.66.199: Connection timed out

Or if I use the hostname that's in the nodelist:

# telnet newfrontier.net binkp
Trying 98.124.199.3...
telnet: connect to address 98.124.199.3: Connection refused

You might have tried to connect while I was doing some upgrading. Both systems have been running about 90% uptime over the last month. I
might have been down 1 entire day, twice in the last 2 months. Both
run around 6-7 days continuously before I reboot to clear things up.

My system has been trying to connect there every 2 hours for about 2 weeks: Nothing.

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello There,

+ 01 May 08:56:49 [13721] call to 1:226/17@fidonet 01 May 08:56:49
[13721] trying frontierbbs.net [76.188.66.199]:24556... 01 May 08:56:49
[13721] connected + 01 May 08:56:49 [13721] outgoing session with
frontierbbs.net:24556 [76.188.66.199] - 01 May 08:56:49 [13721] OPT
CRAM-MD5-3163dff974502d29a534d58f01d67acb CRYPT + 01 May 08:56:49 [13721]
Remote requests MD mode + 01 May 08:56:49 [13721] Remote requests CRYPT

When I tried to connect on port 24554 just now I got:

telnet newfrontier.net binkp
Trying 98.124.199.3...
telnet: Unable to connect to remote host: Connection refused

If I try to telnet on port 23 I get:

telnet newfrontier.net
Trying 98.124.199.3...
telnet: Unable to connect to remote host: Connection refused

You might have tried to connect while I was doing some upgrading. Both system >have been running about 90% uptime over the last month. I might have been down
1 entire day, twice in the last 2 months. Both run around 6-7 days continuously before I reboot to clear things up.

If I ping newfrontier.net I get:

PING newfrontier.net (98.124.199.3) 56(84) bytes of data.
64 bytes from 98.124.199.3 (98.124.199.3): icmp_seq=1 ttl=244 time=72.9 ms 64 bytes from 98.124.199.3 (98.124.199.3): icmp_seq=2 ttl=244 time=73.3 ms

Jeff

--- BBBS/Li6 v4.10 Toy-4
* Origin: Fidoneet: The Ouija Board - Anoka, MN -bbs.ouijabrd.net (1:282/1031)

On May 4th 5:34 am Wilfred van Velzen said...

Hi KrUpTiOn,

Real names please, Charles.

Sorry about that. Enigma is still in alpha stage, I have to manually change all
the echo areas that require real names, but I thought I fixed this one already.
I had a simliar 'issue' in another echo, and I was pretty sure when I replied it showed my real name on my end. Lets see if this message does the same or if it's fixed.


On May 4th 5:34 am Wilfred van Velzen said...

On 2019-05-03 19:23:40, you wrote to me:

It's 'frontierbbs.net' 1:226/16 is the default Bink port.

I only get a timeout there:

# telnet frontierbbs.net binkp Trying 76.188.66.199... telnet: connect to address 76.188.66.199: Connection timed out

ahh, I will have to give you the updated stats on my BBS ip addresses. when I first gave them to andre, I was on my 'old' router, cable modem, computer, AND old domain. for about a week I was having issues with my internet provider, they gave me a new modem, rewired stuff. Then my 3 year old router got fried so
I bought a nighthawk. I'm pretty sure the info I gave to add to the nodelist was prolly 4-5 months old. I'll edit and resend 1:226/16 and 1:226/17's new information.



--- ENiGMA 1/2 v0.0.10-alpha (linux; x64; 10.15.2)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16)

On May 4th 1:35 am Tommi Koivula said...





On May 4th 1:35 am Tommi Koivula said...

6-7 days continuously before I reboot to clear things up.

Well then you may have a firewall or something blocking our connections. It is still not working:

08:08 [1128] BEGIN, binkd/1.1a-99/CYGWIN_NT-6.1 -p -P 1:226/16 binkd.cfg
08:08 [1128] Cannot find domain for zone 1, assuming 'fidonet' 08:08 [1128] creating a poll for 1:226/16@fidonet (`d' flavour) 08:08 [1128] clientmgr started 08:08 [7172] call to 1:226/16@fidonet 08:08 [7172] trying newfrontier.net [98.124.199.3]... 08:08 [7172] connection to

That is pretty weird. I'm getting mail for all my Echomail networks and hubs. I'll *hopefully* have some free time Thursday, or this weekend to take a look at things. I've been dealing with some health issues that put me in the hospital a few days, now that I'm out, I'm having to play catchup on 'real life' (Yes, I know adulting sucks!) lol

Not to mention I was expecting my new i7 laptop to be delivered over the weekend. my 'work' laptop I put it up for auction, and it sold the same day, which I didn't expect. It should be here today (or tomorrow at the latest) then
I can do SOME things while I'm out and abound adulting.



--- ENiGMA 1/2 v0.0.10-alpha (linux; x64; 10.15.2)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16)

On May 4th 9:35 pm Jeff Smith said...

telnet newfrontier.net binkp Trying 98.124.199.3... telnet: Unable to connect to remote host: Connection refused

If I try to telnet on port 23 I get:

telnet newfrontier.net Trying 98.124.199.3... telnet: Unable to connect

wrong domain, it's frontierbbs.net

The New Frontier ][ BBS telnet is: frontierbbs.net:23
The Amiga Frontier BBS telnet: frontierbbs.net:8888



--- ENiGMA 1/2 v0.0.10-alpha (linux; x64; 10.15.2)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16)

Hi KrUpTiOn,

On 2019-05-07 01:56:20, you wrote to me:

Hi KrUpTiOn,

Real names please, Charles.

Sorry about that. Enigma is still in alpha stage, I have to manually change all the echo areas that require real names, but I thought I
fixed this one already. I had a simliar 'issue' in another echo, and I
was pretty sure when I replied it showed my real name on my end. Lets
see if this message does the same or if it's fixed.

It's not "fixed"...

I only get a timeout there:

# telnet frontierbbs.net binkp Trying 76.188.66.199... telnet: connect
to address 76.188.66.199: Connection timed out

ahh, I will have to give you the updated stats on my BBS ip addresses. when I first gave them to andre, I was on my 'old' router, cable
modem, computer, AND old domain. for about a week I was having issues
with my internet provider, they gave me a new modem, rewired stuff.
Then my 3 year old router got fried so I bought a nighthawk. I'm
pretty sure the info I gave to add to the nodelist was prolly 4-5
months old. I'll edit and resend 1:226/16 and 1:226/17's new
information.

Ok... But you can't just change the A records for the domains, to point to the correct IP addresses? Then nothing has to change in the nodelist...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi KrUpTiOn,

On 2019-05-07 01:50:17, you wrote to Tommi Koivula:

Well then you may have a firewall or something blocking our
connections. It is still not working:

08:08 [1128] BEGIN, binkd/1.1a-99/CYGWIN_NT-6.1 -p -P 1:226/16
binkd.cfg
08:08 [1128] Cannot find domain for zone 1, assuming 'fidonet' 08:08
[1128] creating a poll for 1:226/16@fidonet (`d' flavour) 08:08
[1128] clientmgr started 08:08 [7172] call to 1:226/16@fidonet 08:08
[7172] trying newfrontier.net [98.124.199.3]... 08:08 [7172]
connection to

That is pretty weird. I'm getting mail for all my Echomail networks and hubs.

Maybe your system is polling to get the mail?

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi KrUpTiOn!

07 May 2019 01:56, from KrUpTiOn -> Wilfred van Velzen:

Real names please, Charles.

Sorry about that. Enigma is still in alpha stage, I have to manually change all the echo areas that require real names, but I thought I
fixed this one already. I had a simliar 'issue' in another echo, and I
was pretty sure when I replied it showed my real name on my end. Lets
see if this message does the same or if it's fixed.

Not fixed.

CU, Ricsi

... Question authority ... and the authorities will question you.
--- GoldED+/LNX
* Origin: Everyone meets their Waterloo at last! (2:310/31)

On May 7th 6:54 am Richard Menedetter said...

thought I fixed this one already. I had a simliar 'issue' in another echo, and I was pretty sure when I replied it showed my real name on my end. Lets see if this message does the same or if it's fixed.

Not fixed.

CU, Ricsi

Seeing if it's fixed now. It's showing my real name while posting this message



--- ENiGMA 1/2 v0.0.10-alpha (linux; x64; 10.15.2)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16)

On May 7th 4:49 am Wilfred van Velzen said...

fixed this one already. I had a simliar 'issue' in another echo, and

I

was pretty sure when I replied it showed my real name on my end. Lets
see if this message does the same or if it's fixed.

It's not "fixed"...

*This is a test to see if my realname is being used in this echo.*


It shows my real name for this message, now to see after it gets tossed and transported, to see if it's fixed

Thanks
Charles



--- ENiGMA 1/2 v0.0.10-alpha (linux; x64; 10.15.2)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16)

On May 7th 4:49 am Wilfred van Velzen said...

That is pretty weird. I'm getting mail for all my Echomail
networks and

hubs.

Maybe your system is polling to get the mail?

I posted from my other BBS, lastnight my correct ip address. I noticed the one in your logs was my old IP



--- ENiGMA 1/2 v0.0.10-alpha (linux; x64; 10.15.2)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16)

Hi KrUpTiOn,

On 2019-05-07 09:23:00, you wrote to Richard Menedetter:

On May 7th 6:54 am Richard Menedetter said...

thought I fixed this one already. I had a simliar 'issue' in

another

echo, and I was pretty sure when I replied it showed my real name

on

my end. Lets see if this message does the same or if it's fixed.

Not fixed.

CU, Ricsi

Seeing if it's fixed now. It's showing my real name while posting this message

This one still has KrUpTiOn, in the from field...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi KrUpTiOn,

On 2019-05-07 09:20:08, you wrote to me:

It's not "fixed"...

*This is a test to see if my realname is being used in this echo.*

It shows my real name for this message, now to see after it gets tossed

and

transported, to see if it's fixed

Nope...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi KrUpTiOn!

07 May 2019 09:23, from KrUpTiOn -> Richard Menedetter:

Seeing if it's fixed now. It's showing my real name while posting this message

Did not fix it.
It was sent with the name "KrUpTiOn"

CU, Ricsi

... Question authority ... and the authorities will question you.
--- GoldED+/LNX
* Origin: Don't steal - The government hates competition. (2:310/31)

On May 7th 12:54 pm Wilfred van Velzen said...

This one still has KrUpTiOn, in the from field...

I noticed it in all the echoes I have set to show real name. it shows the real name when I post in the 'from' header, but when it goes to save/send the message it reverts back to the user's nickname. I'm going to post this bug over
in the FSXNet Enigma Echo. This software is still in Alpha stage...

Regards,
Charles



--- ENiGMA 1/2 v0.0.10-alpha (linux; x64; 10.15.2)
* Origin: The Amiga Frontier BBS |frontierbbs.net:8888| OH (1:226/16)