The F I D O N E W S Volume 38, Number 15 12 Apr 2021 +--------------------------+-----------------------------------------+
| |The newsletter of the | | |
| | FidoNet community. | | Netmail attach to (POTS): |
| | | | Editor @ 2:2/2 (+46-31-960447) |
| | ____________| | |
| | / __ | Netmail attach to (BinkP): |
| | / / \ | Editor @ 2:203/0 |
| | WOOF! ( /|oo \ | |
| \_______\(_| /_) | Email attach to: |
| _ @/_ \ _ | b @ felten dot se |
| | | \ \\ | |
| | (*) | \ ))| |
| |__U__| / \// | Editor: Bj”rn Felten |
| ______ _//|| _\ / | |
| / Fido \ (_/(_|(____/ | Newspapers should have no friends. |
| (________) (jm) | -- JOSEPH PULITZER | +--------------------------+-----------------------------------------+


Table of Contents
1. GENERAL ARTICLES ......................................... 1
PING robot survey, a follow up ........................... 1
2. LIST OF FIDONET IPV6 NODES ............................... 4
List of IPv6 nodes ....................................... 4
3. JAMNNTPD SERVERS LIST .................................... 7
The Johan Billing JamNNTPd project ....................... 7
4. FIDONEWS'S FIDONET SOFTWARE LISTING ...................... 8
5. SPECIAL INTEREST ......................................... 15
Statistics from the Fidoweb .............................. 15
Nodelist Stats ........................................... 16
6. FIDONEWS INFORMATION ..................................... 18
How to Submit an Article ................................. 18
Credits, Legal Infomation, Availability .................. 20

--- Azure/NewsPrep 3.0
* Origin: Home of the Fidonews (2:2/2.0)

=================================================================
GENERAL ARTICLES =================================================================

PING robot survey, a follow up
By Michiel van der Vlist, 2:280/5555

Eight weeks ago I published a PING robot survey. This is a follow up.

I had hoped that my previous article would encourage sysops to add
PING funtionality to their systems, but so far the result is only
two new PING flags in the nodelist and one sysop who is working on
it.

Note that I write PING in capitals. To emphesize the difference
between the Fidonet "PING" and the IP level "ping" of the InterNet.

The two new systems are:

1:229/426 AKA 1:1/0 and 2:5058/104 AKA 2:5058/0.

The number of unique systems flying a PING flag in the nodelist is
now 38. 10 in Z1, 27 in Z2 and 1 in Z3. Of those 38, 7 fly a PING
flag, but have no active PING responder or the system is off-line.
They should either have the PING flag removed, fix the PING
responder or be removed from the nodelist.

There are 2 systems that list a PING flag in the Z2 pointlist. They
respond to a PING.



So here are the results:



Node nr. Reply by/ Always answers from addressed AKA
Status | Supports Trace
| | AKAs
| | |

1:19/10 Mailguard Y

1:116/116 Ping down 1:116/0

1:124/5016 SBBSecho Y N

1:135/300 Ping down 1:135/0

1:229/101 Diskshop Tracker N Y 1:12/0 1:12/1

1:229/426 O/T+ N Y 1:1/0 1:1/130 1:229/0

1:320/119 Ping Service Y Y 1:320/0 1:142/0

1:320/219 Ping Service Y Y 1:1/19
1:320/319 Ping Service Y Y 1:1/119

1:3634/12 SBBSecho N N 1:1/120 18/0 3634/0 3634/12

2:221/1 O/T-Track N Y 2:221/0 2:221/360

2:221/6 Pong @ hpt Y

2:240/1120 Itrack+ N Y 2/1003 240/1200 56/0 530/0 382/0

2:2432/200 Pvt, No Reply

2:2432/920 Node Down

2:2448/1021 PING * N 2:2448/0

2:280/464 Fmail Y Y

2:280/464.112 Fmail Y Y

2:280/5555 Fmail Y Y 2:28/0

2:280/5555.1 Fmail Y Y

2:292/854 Lord of the Ping N N 2:2/0 2/1000 2/1002 292/80

2:292/8125 Fmail Y Y 2:29/0

2:423/39 Robot (Bash) N

2:460/58 Ping Robot Y Y 2:460/0

2:461/79 Node Down

2:463/68 Craxy Mail Robot Y

2:463/2223 Ping Robot N 2:46/200

2:4642/7 Node Down

2:5019/40 Netmail Daemon N Y 2:5019/0

2:5020/545 pong.pl Y

2:5020/601 Node Down

2:5020/846 Ping-Pong Robot Y

2:5020/1042 RNTrack Y

2:5020/2065 FTrack

2:5021/46 Candle Y Y 2:5021/0

2:5053/58 Ping Robot Y

2:5058/104 hpt/lnx Y Y 2:5058/0

2:5080/102 Ping Down

2:6035/3 Ping Robot Y

3:712/848 Mailer-daemon Y Y 3:3/0 3:712/0


* 2:2448/0 is an AKA of 2:2448/1021. But only 2:2448/1021 flies the
PING flag and answers on a PING request.



-----------------------------------------------------------------

--- Azure/NewsPrep 3.0
* Origin: Home of the Fidonews (2:2/2.0)

=================================================================
LIST OF FIDONET IPV6 NODES =================================================================

List of IPv6 nodes
By Michiel van der Vlist, 2:280/5555

Updated 6 April 2021


Node Nr. Sysop Type Provider Remark

1 2:280/464 Wilfred van Velzen Native Xs4All f
2 2:280/5003 Kees van Eeten Native Xs4All f
3 2:5019/40 Konstantin Kuzov T-6in4 he.net f
4 2:280/5555 Michiel van der Vlist Native Ziggo f
5 1:320/219 Andrew Leary Native Comcast f
6 2:221/1 Tommi Koivula T-6in4 he.net f
7 2:221/6 Tommi Koivula Native OVH
8 2:5053/54 Denis Mikhlevich Native TTK-Volga
9 2:5030/257 Vova Uralsky Native PCextreme
10 1:154/10 Nicholas Bo‰l Native Spectrum f
11 2:203/0 Bj”rn Felten T-6in4 he.net
12 2:280/5006 Kees van Eeten Native Xs4All f INO4
13 3:712/848 Scott Little T-6in4 he.net f
14 2:5020/545 Alexey Vissarionov Native Hetzner f
15 1:103/17 Stephen Hurd T-6in4 he.net
16 2:5020/9696 Alexander Skovpen T-6in4 TUNNELBROKER-0
17 2:421/790 Viktor Cizek T-6in4 he.net
18 2:222/2 Kim Heino Native TeliaSonera
19 3:633/280 Stephen Walsh Native AusNetServers f
20 2:463/877 Alex Shuman Native Nline f IO
21 1:19/10 Matt Bedynek T-6in4 he.net
22 3:770/1 Paul Hayton T-6in4 he.net
23 2:5053/58 Alexander Kruglikov Native TTK-Volga f
24 1:103/1 Stephen Hurd Native Choopa
25 3:633/281 Stephen Walsh Native Internode
26 2:310/31 Richard Menedetter Native DE-NETCUP f
27 3:633/410 Tony Langdon Native IINET
28 2:5020/329 Oleg Lukashin Native Comfortel f
29 2:246/1305 Emil Schuster Native TAL.DE
30 2:2448/4000 Tobias Burchhardt Native DTAG IO
31 2:331/51 Marco d'Itri Native BOFH-IT
32 1:154/30 Mike Miller Native LINODE
33 2:5001/100 Dmitry Protasoff Native Hetzner
34 2:5059/38 Andrey Mundirov T-6in4 he.net
35 2:240/5853 Philipp Giebel Native Hetzner
36 2:5083/444 Peter Khanin Native OVH
37 2:2452/413 Ingo Juergensmann Native RRBONE-COLO f
38 1:123/10 Wayne Smith T-6in4 he.net
39 2:4500/1 Eugene Kozhuhovsky Native DATAHATA6
40 1:135/300 Eric Renfro Native Amazon.com
41 1:103/13 Stephen Hurd Native Choopa
42 2:5020/1042 Michael Dukelsky Native FORPSI Ktis f
43 2:5095/0 Sergey V. Efimoff T-6in4 he.net
44 2:5095/20 Sergey V. Efimoff T-6in4 he.net
45 4:902/26 Fernando Toledo T-6in4 he.net
46 2:5019/400 Konstantin Kuzov Native LT-LT
47 2:467/239 Mykhailo Kapitanov Native Vultr f
48 2:463/1331 Andrei Dzedolik Native DIGITALOCEAN
49 2:5010/275 Evgeny Chevtaev T-6in4 TUNNELBROKER-0 f
50 2:5020/736 Egor Glukhov Native RUWEB f
51 2:280/2000 Michael Trip Native Xs4All
52 2:230/38 Benny Pedersen Native Linode
53 2:460/58 Stas Mishchenkov T-6in4 he.net f
54 1:135/367 Antonio Rivera Native RRSW-V6
55 2:5020/2123 Anton Samsonov T-6in4 he.net
56 2:5020/2332 Andrey Ignatov Native ru.rtk
57 2:5005/49 Victor Sudakov T-6in4 he.net f
58 2:5005/77 Valery Lutoshkin T-6in4 NTS f
59 2:5005/106 Alexey Osiyuk T-6in4 he.net f
60 2:5057/53 Ivan Kovalenko Native ER-Telecom f
61 2:5010/352 Dmitriy Smirnov Native EkranTV f
62 2:292/854 Ward Dossche Native Proximus OO
63 2:469/122 Sergey Zabolotny T-6in4 he.net f
64 2:5053/400 Denis Mikhlevich Native TTK-Volga
65 1:135/371 Eric Renfro Native Cox Cmmunctns
66 2:421/21 Stepan Gabriel Native NETDATACOMM
67 2:5030/1997 Alexey Fayans T-6in4 he.net
68 1:220/70 Joseph Werle T-6in4 he.net
69 2:5061/15 Eugene Gladchenko Native ARUBAUK-NET
70 2:2452/502 Ludwig Bernhartzeder Native DTAG
71 2:423/39 Karel Kral Native WEDOS
72 2:5080/102 Stas Degteff T-6to4 NOVATOR
73 2:280/1049 Simon Voortman Native Solcon
74 1:102/127 Bradley Thornton Native Hetzner
75 2:335/364 Fabio Bizzi Native IT-ALBACOM
76 1:124/5016 Nigel Reed Native DAL1-US
77 2:5020/843 Peter Antonov Native BelCloud
78 2:5075/37 Andrew Komardin Native IHC-NET
79 1:153/146 Erich Bublitz Native LINODE-US
80 1:106/633 William Williams Native LINODE-US PM *1
81 2:263/5 Martin List-Petersen Native TuxBox
82 2:5030/1520 Andrey Geyko T-6in4 he.net f
83 1:229/664 Jay Harris Native Rogers
84 1:142/103 Brian Rogers T-6in4 he.net
85 1:342/17 Kostie Muirhead Native Hurricane El.
86 2:280/2030 Martien Korenblom Native Transip
87 3:633/509 Deon George Native Telstra
88 2:5020/4441 Yuri Myakotin Native SOVINTEL
89 1:320/319 Andrew Leary Native Comcast f
90 2:240/5824 Anna Christina Nass T-6in4 he.net f
91 2:460/5858 Stas Mishchenkov T-6in4 he.net f INO4
92 1:105/5 Michael Pierce Native Comcast
93 1:218/401 James Downs Native ORG-TT1
94 2:5030/3165 Serg Podtynnyi Native DIGITALOCEAN
95 2:301/812 Benoit Panizon Native WOODYV6
96 1:229/616 Vasily Losev Native GIGEPORT
97 2:301/113 Alisha Manuela Stutz T-6in4 he.net


T-6in4 Static 6in4
T-AYIY Dynamic AYIYA
T-6to4 6to4
T-6RD 6RD

Remarks:

f Has a ::f1d0:<zone>:<net>:<node> style host address.
(zone, net, node in decimal notation)
IO Incoming only (Node can not make outgoing IPv6 calls)
OO Outgoing only (Node can not accept incoming IPv6 calls).
INO4 No IPv4 (Node can not accept incoming IPv4 calls).
PO4 Prefers Out on 4 (Node can make outgoing IPv6 calls,
but is configured to try IPv4 first)
6DWN The IPv6 connectivity of this node is temporarely down.
NO6 The node no longer presents an IPv6 address in the nodelist
and will soon be removed from this list.
DOWN This node is Down for both IPv4 and IPv6 and will be
removed from this list if the condition pertains.
PM Prospective Member. The node has demonstrated IPv6
capability but is not listed or does not advertise an
IPv6 address in the Fidonet nodelist yet.

PM *1 [2600:3c01::f03c:91ff:fe2b:c319]


Notes:

To make an IPv6 connection to a node connected via 6to4 tunneling
one may have to force the mailer into IPv6 (-6 option in binkd's
node config for binkd up to 1.1a-96, -64 option for binkd 1.1a-97
and up when compiled with AF_FORCE=1). If the destination address
is a 6to4 tunnel address (2002::/16) many OSs default to IPv4 if
an IPv4 address is present.


Submitted on day 101

-----------------------------------------------------------------

--- Azure/NewsPrep 3.0
* Origin: Home of the Fidonews (2:2/2.0)

=================================================================
SPECIAL INTEREST =================================================================

Last week's statistics from the Fidoweb
By EchoTime, 2:203/0

(Some nets may have lost their last
digit for technical reasons)

pkt (toss-toss) msg (write-toss)
nodes mean dev no mean dev no

154/* 3.5m 3.3m 434 1.1h 4.4h 434
201/* 1.9m 0.3m 2 0.0h 0.0h 2
221/* 2.4m 6.8m 633 5.5h 8.0h 634
280/* 0.6m 0.4m 1010 7.0h 9.1h 1009
292/* 3.2m 1.7m 39 3.9h 3.7h 38
301/* 0.0m 0.1m 4 0.0h 0.1h 4
320/* 1.7m 0.9m 423 2.3h 6.8h 422
502/* 0.7m 0.2m 6 6.0h 5.9h 6

Sigma 1.7m 3.9m 2551 4.8h 8.1h 2549

-----------------------------------------------------------------
Nodelist Stats

Input nodelist nodelist.099
size 184.2kb
date 2021-04-09

The nodelist has 1008 nodes in it
and a total of 1462 non-comment entries

including 4 zones
32 regions
171 hosts
68 hubs
admin overhead 275 ( 27.28 %)

and 102 private nodes
42 nodes down
35 nodes on hold
off line overhead 179 ( 17.76 %)


Speed summary:

>9600 = 50 ( 4.96 %)
9600 = 209 ( 20.73 %)
(HST = 3 or 1.44 %)
(CSP = 0 or 0.00 %)
(PEP = 0 or 0.00 %)
(MAX = 0 or 0.00 %)
(HAY = 0 or 0.00 %)
(V32 = 81 or 38.76 %)
(V32B = 18 or 8.61 %)
(V34 = 98 or 46.89 %)
(V42 = 82 or 39.23 %)
(V42B = 21 or 10.05 %)
2400 = 1 ( 0.10 %)
1200 = 0 ( 0.00 %)
300 = 748 ( 74.21 %)

ISDN = 34 ( 3.37 %)

-----------------------------------------------------
IP Flags Protocol Number of systems -----------------------------------------------------
IBN Binkp 781 ( 77.48 %) ----------------------------------
IFC Raw ifcico 86 ( 8.53 %) ----------------------------------
IFT FTP 60 ( 5.95 %) ----------------------------------
ITN Telnet 163 ( 16.17 %) ----------------------------------
IVM Vmodem 15 ( 1.49 %) ----------------------------------
IP Other 4 ( 0.40 %) ----------------------------------
INO4 IPv6 only 2 ( 0.20 %) ----------------------------------

CrashMail capable = 857 ( 85.02 %)
MailOnly nodes = 319 ( 31.65 %)
Listed-only nodes = 23 ( 2.28 %)



[Report produced by NETSTATS - A PD pgm]
[ Revised by B Felten, 2:203/2]
[ NetStats 3.8 2014-11-23]

-----------------------------------------------------------------

--- Azure/NewsPrep 3.0
* Origin: Home of the Fidonews (2:2/2.0)

Hello Michael,

=================================================================
GENERAL ARTICLES =================================================================

PING robot survey, a follow up
By Michiel van der Vlist, 2:280/5555

Eight weeks ago I published a PING robot survey. This is a follow up.

I had hoped that my previous article would encourage sysops to add
PING funtionality to their systems, but so far the result is only
two new PING flags in the nodelist and one sysop who is working on
it.

I have added PING support to my node here thanks to Stas Mishchenkov's Ping Robot for HPT perl.

It replies to Ping and also supports trace. I have it enabled at 1:153/0 and 1:153/757. 1:153/757.2 also replies to Ping from SBBSecho.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Alan,

On Thursday April 15 2021 23:17, you wrote to Michael van der Vlist:

I have added PING support to my node here thanks to Stas Mishchenkov's Ping Robot for HPT perl.

It replies to Ping and also supports trace. I have it enabled at
1:153/0 and 1:153/757. 1:153/757.2 also replies to Ping from SBBSecho.

Great!

Tests are on the way... ;-)


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)

Hello Alan,

Friday April 16 2021 09:41, I wrote to you:

It replies to Ping and also supports trace. I have it enabled at
1:153/0 and 1:153/757. 1:153/757.2 also replies to Ping from
SBBSecho.

Great!

Tests are on the way... ;-)

Test passed! ;-)


Next step: Add the PING flag to the nodelist.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)

Hi Alan,

On 2021-04-15 23:17:13, you wrote to Michael van der Vlist:

=================================================================
GENERAL ARTICLES
=================================================================

PING robot survey, a follow up
By Michiel van der Vlist, 2:280/5555

Eight weeks ago I published a PING robot survey. This is a follow up.

I had hoped that my previous article would encourage sysops to add
PING funtionality to their systems, but so far the result is only
two new PING flags in the nodelist and one sysop who is working on
it.

I have added PING support to my node here thanks to Stas Mishchenkov's Ping
Robot for HPT perl.

It replies to Ping and also supports trace. I have it enabled at 1:153/0 and 1:153/757. 1:153/757.2 also replies to Ping from SBBSecho.

I've sent a routed netmail to PING@1:153/757, 2 hours ago. No response yet...

Bye, Wilfred.

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

Re: Re: FidoNews 38:15 [01/07]: General Articles
By: Wilfred van Velzen to Alan Ianson on Fri Apr 16 2021 01:30 pm

It replies to Ping and also supports trace. I have it enabled at
1:153/0 and 1:153/757. 1:153/757.2 also replies to Ping from SBBSecho.

I've sent a routed netmail to PING@1:153/757, 2 hours ago. No response yet...

I haven't seen anything from your node yet, maybe it took the scenic route?

My inbound is clean ATM but I'll keep an eye out for it.

Ttyl :-),
Al

... Math problems? Call 1-800-10*(24+13)-(64-16)/2^14E2.
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Hi Alan,

On 2021-04-16 04:52:28, you wrote to me:

I've sent a routed netmail to PING@1:153/757, 2 hours ago. No
response yet...

I haven't seen anything from your node yet, maybe it took the scenic route?

It was routed via 1:229/101. After that I don't know where it will go. I haven't seen any Trace responses either.
But maybe Frank's system isn't working OK, he's been AWOL for a while now. But I do receive some echomail from his system still...


Bye, Wilfred.

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

On 16.4.2021 4:52, Alan Ianson wrote:

It replies to Ping and also supports trace. I have it enabled at
1:153/0 and 1:153/757. 1:153/757.2 also replies to Ping from SBBSecho.

I've sent a routed netmail to PING@1:153/757, 2 hours ago. No response yet...

I haven't seen anything from your node yet, maybe it took the scenic route?

I just received two pongs, from 1:153/757 and from 1:153/757.2. But we have a very short path. :)

X-SMAPI-Control: @PATH: 153/757 221/6 1

'Tommi

---
* Origin: - rbb.fidonet.fi - Lake Ylo - Finland - (2:221/1)

Hello Alan,

On Friday April 16 2021 04:52, you wrote to Wilfred van Velzen:

I've sent a routed netmail to PING@1:153/757, 2 hours ago. No
response yet...

I haven't seen anything from your node yet, maybe it took the scenic route?

The problem is not at your end. I send pings to 1:153/757 and 1:153/757.2 routed via 1:153/7715. I got ping and trace responses within a couple of minutes.

However, no reply from a ping to 1:153/0 yet...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)

Re: Re: FidoNews 38:15 [01/07]: General Articles
By: Wilfred van Velzen to Alan Ianson on Fri Apr 16 2021 02:09 pm

It was routed via 1:229/101. After that I don't know where it will go. I haven't seen any Trace responses either.

I just polled 1:229/101 and picked up a netmail from January!

But still nothing from your node.

Maybe try 1:153/7715, 2:221/6 or 3:770/1. I think you'll get a quick response via those nodes.

Ttyl :-),
Al

... I tried to drown my problems.. they like beer too!
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Re: FidoNews 38:15 [01/07]: General Articles
By: Tommi Koivula to Alan Ianson on Fri Apr 16 2021 03:20 pm

I just received two pongs, from 1:153/757 and from 1:153/757.2. But we have a very short path. :)

That's true, good to know it works.

Ttyl :-),
Al

... Money isn't everything, usually it isn't even enough.
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Re: FidoNews 38:15 [01/07]: General Articles
By: Michiel van der Vlist to Alan Ianson on Fri Apr 16 2021 02:21 pm

However, no reply from a ping to 1:153/0 yet...

1:153/7715 used to fly 1:153/0. I wonder if that AKA is still in his config.

I will ask him to check what happens to mail for 153/0 there.

Ttyl :-),
Al

... Help support helpless victims of computer error!
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Hi Alan,

On 2021-04-16 06:18:02, you wrote to me:

It was routed via 1:229/101. After that I don't know where it will
go.
I haven't seen any Trace responses either.

I just polled 1:229/101 and picked up a netmail from January!

But still nothing from your node.

Maybe try 1:153/7715, 2:221/6 or 3:770/1. I think you'll get a quick response via those nodes.

The point of the PING messages is to find routing problems, so I'm not going to route around the problems! ;)

I mostly use crash mails when I need to be sure a netmail is delivered, any way! ;)

Bye, Wilfred.

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

Re: Re: FidoNews 38:15 [01/07]: General Articles
By: Wilfred van Velzen to Alan Ianson on Fri Apr 16 2021 03:31 pm

The point of the PING messages is to find routing problems, so I'm not going to route around the problems! ;)

OK, I hope you will get a reply before too long.

I mostly use crash mails when I need to be sure a netmail is delivered, any way! ;)

Good idea.. :)

Ttyl :-),
Al

... Always remember you're unique - just like everyone else.
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Hi Alan,

On 2021-04-16 06:42:40, you wrote to me:

The point of the PING messages is to find routing problems, so I'm
not going to route around the problems! ;)

OK, I hope you will get a reply before too long.

Maybe I'll try a crashmail to PING on your system, so we know how the route back goes. Do you have a direct connection with Nick BTW? If not it would be interesting if you ping'ed his system...

Bye, Wilfred.

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

Hi Alan,

On 2021-04-16 16:04:47, I wrote to you:

The point of the PING messages is to find routing problems, so I'm
not going to route around the problems! ;)

OK, I hope you will get a reply before too long.

Maybe I'll try a crashmail to PING on your system, so we know how the route
back goes.

PING was crashed half an hour ago on you system:

+ 16 Apr 16:40:06 [10791] call to 1:153/757@fidonet
16 Apr 16:40:06 [10791] trying trmb.synchro.net [104.246.155.40]...
16 Apr 16:40:06 [10791] connected
+ 16 Apr 16:40:06 [10791] outgoing session with trmb.synchro.net:24554 [104.246.155.40]
- 16 Apr 16:40:07 [10791] OPT CRAM-MD5-8097d22b93185dced86bb4efc6672eee
+ 16 Apr 16:40:07 [10791] Remote requests MD mode
- 16 Apr 16:40:07 [10791] SYS The Rusty MailBox
- 16 Apr 16:40:07 [10791] ZYZ Alan Ianson
- 16 Apr 16:40:07 [10791] LOC Penticton, BC Canada
- 16 Apr 16:40:07 [10791] NDL 115200,CM,XW,IBN
- 16 Apr 16:40:07 [10791] TIME Fri, 16 Apr 2021 07:40:07 -0700
- 16 Apr 16:40:07 [10791] VER binkd/1.1a-112/Linux binkp/1.1
+ 16 Apr 16:40:07 [10791] addr: 1:153/757@fidonet
+ 16 Apr 16:40:07 [10791] addr: 1:153/0@fidonet
+ 16 Apr 16:40:07 [10791] addr: 21:4/106@fsxnet (n/a or busy)
- 16 Apr 16:40:07 [10791] TRF 0 0
+ 16 Apr 16:40:07 [10791] Remote has 0b of mail and 0b of files for us
- 16 Apr 16:40:07 [10791] OPT EXTCMD GZ BZ2
+ 16 Apr 16:40:07 [10791] Remote supports EXTCMD mode
+ 16 Apr 16:40:07 [10791] Remote supports GZ mode
+ 16 Apr 16:40:07 [10791] Remote supports BZ2 mode
+ 16 Apr 16:40:07 [10791] sending /home/fido/outbound.001/079a1c40.pkt as 079a1c40.pkt (388)
+ 16 Apr 16:40:07 [10791] sent: /home/fido/outbound.001/079a1c40.pkt (388, 388.00 CPS, 1:153/757@fidonet)
+ 16 Apr 16:40:07 [10791] done (to 1:153/757@fidonet, OK, S/R: 1/0 (388/0 bytes))

A response hasn't arrrived yet...

Bye, Wilfred.

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

Hi Anna,

On 2021-04-16 17:34:00, you wrote to FidoNews Robot:

My BBS, Imzadi Box 2:240/5824, also supports PING mails and should respond correctly.

Test is on it's way...

The thing with a nodelist update for my system is ... not so easy, I don't know if/when the change could be applied.

It should be easy! A simple edit by your host should take care of it...

Bye, Wilfred.

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

Hello Anna,

On Friday April 16 2021 17:34, you wrote to FidoNews Robot:

My BBS, Imzadi Box 2:240/5824, also supports PING mails and should
respond correctly.

It does. I got a PING response from your SBBSecho.

A test to see if it also supports TRACE failed. No big deal.

The thing with a nodelist update for my system is ... not so easy, I
don't know if/when the change could be applied.

Just write a netmail to Torsten Bamberg to the effect that you want the PING flag added to your listing. That is what NCs are for. ;-)


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)

Re: Re: FidoNews 38:15 [01/07]: General Articles
By: Wilfred van Velzen to Alan Ianson on Fri Apr 16 2021 05:11 pm

+ 16 Apr 16:40:07 [10791] sending /home/fido/outbound.001/079a1c40.pkt as 079a1c40.pkt (388)
+ 16 Apr 16:40:07 [10791] sent: /home/fido/outbound.001/079a1c40.pkt (388, 388.00 CPS, 1:153/757@fidonet)

A response hasn't arrrived yet...

I did get that message, Ping replied and packed that reply to 153/7715. I was thinking but I could be wrong that Dallas had a fairly direct route to net 280.

I have changed the route for net 280 to go via 2:221/6 as most traffic for zone 2 goes. Can you try again?

Ttyl :-),
Al

... You cannot achieve the impossible without attempting the absurd.
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Hello Alan,

On Friday April 16 2021 15:28, you wrote to Wilfred van Velzen:

A response hasn't arrrived yet...

I did get that message, Ping replied and packed that reply to
153/7715. I was thinking but I could be wrong that Dallas had a fairly direct route to net 280.

He does, he has a direct link with me. I got your PINg responze via that link. So I wonder why he does not use that link to route all mail for net 280 to me...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)

Wilfred,

I've sent a routed netmail to PING@1:153/757, 2 hours ago. No response yet...

Where are the days that a reply within the week was considered OK.

\%/@rd

--- DB4 - Apr.15 2021
* Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)

Re: Re: FidoNews 38:15 [01/07]: General Articles
By: Wilfred van Velzen to Alan Ianson on Fri Apr 16 2021 04:04 pm

Maybe I'll try a crashmail to PING on your system, so we know how the route back goes. Do you have a direct connection with Nick BTW? If not it would be interesting if you ping'ed his system...

Yes, I am linked at 229/101 and 229/426 so either should work.

Ttyl :-),
Al

... Scotty, beam me to the Bahamas.
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Re: Re: FidoNews 38:15 [01/07]: General Articles
By: Anna Christina Nass to FidoNews Robot on Fri Apr 16 2021 05:34 pm

My BBS, Imzadi Box 2:240/5824, also supports PING mails and should respond correctly.

I just sent a ping to your node. I have received a couple trace replies so it is heading your way. I'll let you know when I get a reply.

I guess most Synchronet BBSes do support it as I don't remember having to enable it somehow :)

Yes, it just works with Synchronet, you just need to setup your routes.

The thing with a nodelist update for my system is ... not so easy, I don't know if/when the change could be applied.

Just ask your NC to add it, it shouldn't take long at all.

Ttyl :-),
Al

... Shhh! Be vewwy, vewwy quiet! I'm hunting tag-wines!
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Re: FidoNews 38:15 [01/07]: General Articles
By: Michiel van der Vlist to Alan Ianson on Sat Apr 17 2021 12:32 am

He does, he has a direct link with me. I got your PINg responze via that link. So I wonder why he does not use that link to route all mail for net 280 to me...

I am just about to write Dallas to talk about routes and stuff so I'll bring it up.

Ttyl :-),
Al

... But that trick never works! -Rocky
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Re: Re: FidoNews 38:15 [01/07]: General Articles
By: Wilfred van Velzen to Alan Ianson on Sat Apr 17 2021 12:45 am

A response to that one arrived here quite fast:

========================================================================== =====
From : Ping Robot 1:153/757 2021-04-16 15:40:52
To : Wilfred van Velzen 2:280/464
Subj : Pong ========================================================================== ===== @INTL 2:280/464 1:153/757
@MSGID: 1:153/757 607a1275
@TID: hpt/lnx 1.9.0-cur 2021-03-14
Hi Wilfred van Velzen.

Your ping-message was received by my system on Fri Apr 16 15:40:53 2021

Orignal message: ========================================================================== == From: Wilfred van Velzen 2:280/464 17 Apr 21 00:40:32
To : PING 1:153/757
Subj: Crashmail ping test to 1:153/757 ==========================================================================

@Via 1:153/757 @20210416.224053.UTC hpt/lnx 1.9.0-cur 2021-03-14
@Via 2:221/6 @20210416.224117.UTC hpt/lnx 1.9.0-cur 2021-04-15
@Via 2:280/5555 @20210416.224131.432.UTC FMail-W32(Toss) 2.1.3.7-B20170919 @Via 2:280/5555 @20210416.224131.495.UTC FMail-W32(Pack) 2.1.3.7-B20170919 @Via 2:280/464 @20210416.224219.082.UTC FMail-lnx64(Toss)

That looks much better.. :)

Ttyl :-),
Al

... The large print giveth and the small print taketh away.
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Re: Re: FidoNews 38:15 [01/07]: General Articles
By: Ward Dossche to Wilfred van Velzen on Sat Apr 17 2021 01:07 am

Where are the days that a reply within the week was considered OK.

That was yesterday.. ;)

Ttyl :-),
Al

... Give a woman an inch and she'll park a car in it.
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Hi! Ward,

On 04/17/2021 01:07 AM, you wrote to Wilfred van Velzen:

I've sent a routed netmail to PING@1:153/757, 2 hours ago. No response
yet...

Where are the days that a reply within the week was considered OK.

That was pre-MXMXI. Welcome to MMXXI! Please adjust your PLayboy calendar.

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: "Oops!" --unknown (just before the Big Bang) (3:640/1384.125)

Re: Re: FidoNews 38:15 [01/07]: General Articles
By: Alan Ianson to Anna Christina Nass on Fri Apr 16 2021 04:43 pm

I just sent a ping to your node. I have received a couple trace replies so it is heading your way. I'll let you know when I get a reply.

I just got this reply from your node, took only 30 minutes.

= NETMAIL (1:153/757) =========================================================
Msg : 70 of 70 Rcv Pvt
From : SBBSecho 2:240/5824 17 Apr 21 02:02:42
To : Alan Ianson 1:153/757
Subj : Pong: Please respond =============================================================================== @INTL 1:153/757 2:240/5824
@PID: SBBSecho 3.11-Linux r3.177 Dec 22 2020 GCC 8.3.0
@TZUTC: 0200
Your PING request was received at: Sat Apr 17 2021 02:02:42 CEST
by: Imzadi Box (sysop: Anna Christina Nass) @ 2:240/5824

The received message header contained:

Subj: Please respond
Attr: 0021
To : ping (2:240/5824)
From: Alan Ianson (1:153/757)
Date: 16 Apr 21 16:33:06 (parsed: 0x6079A022, Fri Apr 16 16:33:06 2021)

======[ Received message text ]======
@INTL 2:240/5824 1:153/757
@MSGID: 1:153/757 607a1ef0
@PID: GED+LNX 1.1.5-b20180707
@CHRS: LATIN-1 2
@TZUTC: -0700
Hello ping,

Please respond.

Ttyl :-),
Al

@Via 1:153/757 @20210416.233417.UTC hpt/lnx 1.9.0-cur 2021-03-14
@Via 2:221/6 @20210416.233447.UTC hpt/lnx 1.9.0-cur 2021-04-15
@Via 2:221/1 @20210416.233620.UTC O/T-Track+ 2.85
@Via 2:221/1 @20210416.233623.UTC hpt/os2-wc 1.9.0-cur 2021-04-15
@Via 2:240/5832@fidonet.org @20210417.003651.41.UTC Itrack- 2.0
======[ End received msg text ]======
-+- SBBSecho 3.11-Linux
@Via 2:240/5824 @20210417.000242.UTC SBBSecho 3.11-Linux r3.177
@Via 2:240/5832@fidonet.org @20210417.010250.21.UTC Itrack- 2.0
@Via 1:229/426 @20210416.200215.LST D'Bridge 4
@Via 1:229/426@fidonet @20210416.200215.LST O/T-Track+ 2.85

Spiffy!

Ttyl :-),
Al

... "Keyboard? How quaint!" - Scotty
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Hi Paul,

That was pre-MXMXI. Welcome to MMXXI! Please adjust your PLayboy calendar.

I think you need to freshen up on your Roman numerals.

Early Playboy calendars were way better, real tits ... not photoshopped. (sorry ladies for my language)

\%/@rd

--- DB4 - Apr.15 2021
* Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)

Hi! Ward,

On 17 Apr 2021, Ward Dossche said the following...

That was pre-MXMXI. Welcome to MMXXI! Please adjust your PLayboy calendar.

I think you need to freshen up on your Roman numerals.

Getting your attention was the aim. It works nicely on a (Ubuntu)
calculator.

Early Playboy calendars were way better, real tits ... not photoshopped. (sorry ladies for my language)

Yep. Circa late-70s, when I stopped looking at their mags.

Cheers,
Paul.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/32)
* Origin: Quinn's Rock - stuck in a Linux VM, again! (3:640/1384)

Hi Alan,

On 2021-04-16 16:39:27, you wrote to me:

Maybe I'll try a crashmail to PING on your system, so we know how the
route back goes. Do you have a direct connection with Nick BTW? If
not it would be interesting if you ping'ed his system...

Yes, I am linked at 229/101 and 229/426 so either should work.

I routed to 229/101 for the PING test, so if you didn't get it from him, I think we found the problem... :-(

Bye, Wilfred.

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

Hi Alan,

On 2021-04-16 16:48:47, you wrote to me:

@Via 1:153/757 @20210416.224053.UTC hpt/lnx 1.9.0-cur 2021-03-14
@Via 2:221/6 @20210416.224117.UTC hpt/lnx 1.9.0-cur 2021-04-15
@Via 2:280/5555 @20210416.224131.432.UTC FMail-W32(Toss)
2.1.3.7-B20170919 @Via 2:280/5555 @20210416.224131.495.UTC
FMail-W32(Pack) 2.1.3.7-B20170919 @Via 2:280/464
@20210416.224219.082.UTC FMail-lnx64(Toss)

That looks much better.. :)

Yes, but now you are routing around the problem, instead of trying to get it fixed... :-/

Bye, Wilfred.

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

Re: Re: FidoNews 38:15 [01/07]: General Articles
By: Wilfred van Velzen to Alan Ianson on Sat Apr 17 2021 12:42 pm

I routed to 229/101 for the PING test, so if you didn't get it from him, I think we found the problem... :-(

Yes, I think that is a problem. I'll netmail Frank and ask him to check our link.

Ttyl :-),
Al

... tHE fIRST sTEP iS tO tAKE oFF tHE cAPS lOCK.
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Re: Re: FidoNews 38:15 [01/07]: General Articles
By: Wilfred van Velzen to Alan Ianson on Sat Apr 17 2021 12:43 pm

Yes, but now you are routing around the problem, instead of trying to get it fixed... :-/

Now that we have discovered these problems they can be fixed. I still haven't net mailed Dallas but I am going to make time for that today.

Problems do show themselves from time to time but there are solutions also.

Ttyl :-),
Al

... Should I or shouldn't I?... Too late, I did!
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

I had hoped that my previous article would encourage sysops to add
PING funtionality to their systems, but so far the result is only
two new PING flags in the nodelist and one sysop who is working on
it.

I just finished a ping robot that *should* be working with sbbsecho if
you want to test - ping@1:342/17
--- SBBSecho 3.11-Linux
* Origin: bbs.undermine.ca:423 - Calgary, AB (1:342/17)

Re: Re: FidoNews 38:15 [01/07]: General Articles
By: Kostie Muirhead to michiel.van.der.vlist on Sat Apr 17 2021 02:21 pm

I just finished a ping robot that *should* be working with sbbsecho if you want to test - ping@1:342/17

It works for me. :)

Ttyl :-),
Al

... Unable to locate Coffee -- Operator Halted!
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Hello Kostie,

On Saturday April 17 2021 14:21, you wrote to michiel.van.der.vlist:

I just finished a ping robot that *should* be working with sbbsecho if
you want to test - ping@1:342/17

Test on the way...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)

Cool. I'll try to watch the logs for it.

Test on the way...

Cheers, Michiel

--- SBBSecho 3.11-Linux
* Origin: bbs.undermine.ca:423 - Calgary, AB (1:342/17)

Paul,

I think you need to freshen up on your Roman numerals.

Getting your attention was the aim.

Bollocks.

It works nicely on a (Ubuntu) calculator.

A good reason not to use it. It's wrong.

\%/@rd

--- DB4 - Apr.15 2021
* Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)

On 17/04/2021 10:21, 2292/854 wrote:

That was pre-MXMXI.  Welcome to MMXXI!  Please adjust your PLayboy
calendar.

I think you need to freshen up on your Roman numerals.

Early Playboy calendars were way better, real tits ... not photoshopped. (sorry ladies for my language)

I'm sure that the ladies know what tits are.

--
Regards
David

--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbi
* Origin: Narrabri, NSW (3:640/305)

On 18/04/2021 06:15, 2203/2 wrote:

Early Playboy calendars were way better, real tits ... not photoshopped.
(sorry ladies for my language)

Raquel Welch still looks good - even on her 80th birthday.
Which was yesterday. Happy Birthday, Raquel!

Hers may not be photo-shopped, but are they real?

--
Regards
David

--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbi
* Origin: Narrabri, NSW (3:640/305)

Hi! Ward,

On 04/18/2021 08:40 PM, you wrote:

It works nicely on a (Ubuntu) calculator.

A good reason not to use it. It's wrong.

I know that. OTOH, I consider MXM as being correct while adding XI was a pleasant surprise, and suited my intended purpose perfectly.

Do you have Dutch ancestry?

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Move your vowels every day or you'll get consonated. (3:640/1384.125)

Paul,

Do you have Dutch ancestry?

I do.

Actually from the Province of Zeeland. Don't know if it really qualifies.

\%/@rd

--- DB4 - Apr.15 2021
* Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)

Hi! Ward,

On 19 Apr 2021, Ward Dossche said the following...

Actually from the Province of Zeeland. Don't know if it really qualifies.

Yes. You feel at home on the roiling deck of seagoing craft.

Cheers,
Paul.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/32)
* Origin: Quinn's Rock - stuck in a Linux VM, again! (3:640/1384)

Hi Anna,

On 2021-04-19 11:20:00, you wrote to me:

My BBS, Imzadi Box 2:240/5824, also supports PING mails and should
respond correctly.

Test is on it's way...

Which was 3 hours ago, but I haven't received a response. :-(

Did you get a response now?

No, and I tried it again with a crashmail to your system. Which also didn't get a response so far:

===============================================================================
From : Wilfred van Velzen 2:280/464 2021-04-17 18:41:48
To : PING 2:240/5824
Subj : Ping test crash to 2:240/5824 =============================================================================== @INTL 2:240/5824 2:280/464
@MSGID: 2:280/464 607b0fcd
@PID: GED+LNX 1.1.5-b20161221
@CHRS: UTF-8 2
@TZUTC: 0200
@RFC-X-No-Archive: Yes
Hi Ping,

Bye, Wilfred. ===============================================================================

Did your system proces it? And where did it route the answer to?

Bye, Wilfred.

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

Hi Anna,

On 2021-04-19 11:30:00, you wrote to me:

Btw: I've now also tried crash, and got this:

+ 16 Apr 21:13:18 [26562] call to 2:240/5824@fidonet
16 Apr 21:13:18 [26562] trying box.imzadi.de
[2001:470:540b:0:f1d0:2:240:5824]... ? 16 Apr 21:15:25 [26562]
connection to 2:240/5824@fidonet failed: Connection timed out 16 Apr
21:15:25 [26562] trying box.imzadi.de [217.81.92.195]:24554... 16
Apr 21:15:25 [26562] connected + 16 Apr 21:15:25 [26562] outgoing
session with box.imzadi.de:24554 [217.81.92.195] ...

So there is something wrong with your IPv6 inbound, so it seems...

Thank you for the information!

It should now work again. But I don't really know what the problem was... After a reboot of the BBS, it is working again?!?

Yes, this one worked:

+ 19 Apr 11:55:13 [13139] call to 2:240/5824@fidonet
19 Apr 11:55:13 [13139] trying box.imzadi.de [2001:470:540b:0:f1d0:2:240:5824]...
19 Apr 11:55:13 [13139] connected
+ 19 Apr 11:55:13 [13139] outgoing session with box.imzadi.de:24554 [2001:470:540b:0:f1d0:2:240:5824]
- 19 Apr 11:55:13 [13139] OPT CRAM-MD5-ff1f53a7d7428df8ec261eb37bc0f4fe CRYPT
+ 19 Apr 11:55:13 [13139] Remote requests MD mode
+ 19 Apr 11:55:13 [13139] Remote requests CRYPT mode
- 19 Apr 11:55:13 [13139] SYS Imzadi Box
- 19 Apr 11:55:13 [13139] ZYZ Anna Christina Nass
- 19 Apr 11:55:13 [13139] LOC Karlsruhe, DEU
- 19 Apr 11:55:13 [13139] NDL 115200,TCP,BINKP
- 19 Apr 11:55:13 [13139] TIME Mon Apr 19 2021 11:55:13 GMT+0200 (CEST)
- 19 Apr 11:55:13 [13139] VER BinkIT/2.39,JSBinkP/1.123,sbbs3.18b/Linux binkp/1.1
+ 19 Apr 11:55:13 [13139] addr: 2:240/5824@fidonet
+ 19 Apr 11:55:13 [13139] addr: 21:3/127@fsxnet (n/a or busy)
+ 19 Apr 11:55:13 [13139] addr: 1337:1/108@tqwnet (n/a or busy)
+ 19 Apr 11:55:13 [13139] addr: 77:2/108@scinet (n/a or busy)
+ 19 Apr 11:55:13 [13139] addr: 75:49/5@bbsnet (n/a or busy)
+ 19 Apr 11:55:13 [13139] addr: 42:60/0@sfnet (n/a or busy)
+ 19 Apr 11:55:13 [13139] addr: 420:2/1@weednet (n/a or busy)
+ 19 Apr 11:55:14 [13139] sending /home/fido/outbound/07d537f0.pkt as 07d537f0.pkt (386)
+ 19 Apr 11:55:14 [13139] sent: /home/fido/outbound/07d537f0.pkt (386, 386.00 CPS, 2:240/5824@fidonet)
+ 19 Apr 11:55:14 [13139] done (to 2:240/5824@fidonet, OK, S/R: 1/0 (386/0 bytes))
19 Apr 11:55:14 [13139] session closed, quitting...

I delivered another crash mail destined to your PING bot...


Bye, Wilfred.

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

Hello Michiel,

I did get that message, Ping replied and packed that reply to
153/7715. I was thinking but I could be wrong that Dallas had a
fairly direct route to net 280.

He does, he has a direct link with me. I got your PINg responze via
that link. So I wonder why he does not use that link to route all mail
for net 280 to me...

I did ask Dallas about that and he told me he routes mail for zone 2 via 261/38, Nick Andre.

I'm not sure if that means he is routing via Janis 1:261/38 or Nick 1:229/426. If he did route Wilfred's reply via 229/426 it may be on hold there for Wilfred, but I have no way to know.

I have more confidence in Tommi so I will route mail for net 280 (and zone 2, for the most part) that way and since 153/7715 is working for your node I'll keep routing 280/5555 to 153/7715.

I also asked Dallas about mail for 153/0 and he seemed to think mail for 153/0 was on hold for my node. I poll 153/7715 several times a day and I have not seen that message. I hope that Dallas has eyes on that and will get mail I need to see to me.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hi Alan,

On 2021-04-19 02:45:30, you wrote to Michiel van der Vlist:

He does, he has a direct link with me. I got your PINg responze via
that link. So I wonder why he does not use that link to route all
mail for net 280 to me...

I did ask Dallas about that and he told me he routes mail for zone 2 via 261/38, Nick Andre.

He seems to be confused about the current ZC !?

I'm not sure if that means he is routing via Janis 1:261/38 or Nick 1:229/426. If he did route Wilfred's reply via 229/426 it may be on hold there for Wilfred, but I have no way to know.

I have a direct secure link with 229/426, so there shouldn't be any mail on hold for me...


Bye, Wilfred.

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

Hi Michiel,

On 2021-04-19 11:58:13, you wrote to Anna Christina Nass:

It should now work again. But I don't really know what the problem
was... After a reboot of the BBS, it is working again?!?

MvdV> Nope.

MvdV> + 11:57 [3220] call to 2:240/5824@fidonet
MvdV> 11:57 [3220] trying box.imzadi.de [2001:470:540b:0:f1d0:2:240:5824]...
MvdV> ? 11:57 [3220] connection to 2:240/5824@fidonet failed: {W32 API error
MvdV> 10060} Connection timed out

It was working 2 minutes earlier... ;)

Bye, Wilfred.

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

Hello Wilfred,

On Monday April 19 2021 12:09, you wrote to me:

MvdV>> Nope.

MvdV>> + 11:57 [3220] call to 2:240/5824@fidonet
MvdV>> 11:57 [3220] trying box.imzadi.de
MvdV>> [2001:470:540b:0:f1d0:2:240:5824]... ? 11:57 [3220] connection
MvdV>> to 2:240/5824@fidonet failed: {W32 API error
MvdV>> 10060} Connection timed out

It was working 2 minutes earlier... ;)

So it was YOU who broke it. ;-)


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)

Hi Michiel,

On 2021-04-19 12:18:34, you wrote to me:

MvdV>>> + 11:57 [3220] call to 2:240/5824@fidonet
MvdV>>> 11:57 [3220] trying box.imzadi.de
MvdV>>> [2001:470:540b:0:f1d0:2:240:5824]... ? 11:57 [3220] connection
MvdV>>> to 2:240/5824@fidonet failed: {W32 API error
MvdV>>> 10060} Connection timed out

It was working 2 minutes earlier... ;)

MvdV> So it was YOU who broke it. ;-)

I can't exclude that as possibility. ;)

Bye, Wilfred.

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

Alan,

I did ask Dallas about that and he told me he routes mail for zone 2 via 261/38, Nick Andre.

I'm certain Nick Andre will be delighted to find that out.

\%/@rd

--- DB4 - Apr.15 2021
* Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)

Paul,

Actually from the Province of Zeeland. Don't know if it really
qualifies.

Yes. You feel at home on the roiling deck of seagoing craft.

100%. Boats are part of my life.

\%/@rd

--- DB4 - Apr.15 2021
* Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)

Hello David,

That was pre-MXMXI.ÿ Welcome to MMXXI!ÿ Please adjust your PLayboy
calendar.

I think you need to freshen up on your Roman numerals.

Early Playboy calendars were way better, real tits ... not

photoshopped.

(sorry ladies for my language)

I'm sure that the ladies know what tits are.

If you are jealous, get some fenugreek and make a tea.
The more you drink, the bigger your tits.
And also the more milk you will make.
Problem is, you might have to buy you a whole new wardrrobe ...

--Lee

--
Get Her Wet Here

--- MesNews/1.08.05.00-gb
* Origin: news://eljaco.se (2:203/2)

Hello David,

Early Playboy calendars were way better, real tits ... not

photoshopped.

(sorry ladies for my language)

Raquel Welch still looks good - even on her 80th birthday.
Which was yesterday. Happy Birthday, Raquel!

Hers may not be photo-shopped, but are they real?

Mama Mia! Nothing fake about them! She is most definitaly Italian!

--Lee

--
Coronovirus doesn't effect rats n snakes so most of u are safe.

--- MesNews/1.08.05.00-gb
* Origin: news://eljaco.se (2:203/2)

Hello Ward,

I'm certain Nick Andre will be delighted to find that out.

I'm sure he is aware.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 19 Apr 21 05:47:00, Alan Ianson said the following to Ward Dossche:

I'm certain Nick Andre will be delighted to find that out.

I'm sure he is aware.

Nope, I wasn't.

Nick
--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

On 19 Apr 21 02:45:30, Alan Ianson said the following to Michiel Van Der Vlist:

I'm not sure if that means he is routing via Janis 1:261/38 or Nick 1:229/4 If he did route Wilfred's reply via 229/426 it may be on hold there for Wilfred, but I have no way to know.

Wilfred has a direct connection here. He wouldn't dare miss out at the chance to masturbate my Areafix for brand new Z1-secret-society stuff.

Any node that has a direct connection here, logically then has direct routing.

So theres the Net 229 stuff followed by RC's for each Net, and ZC's... Ward
for zone 2, Scott for zone 3 and Manuel for the Twilight Zone. Which all
three have direct connections. Since I'm seeing inbound routed Ping requests from Michiel, Tommi, Wilfred, etc. all the usual chronic masturbators, I
assume my system "works" to their satisfaction.

The way it should be... why anyone would use Janis's unreliable Linux BBBS bullshit is beyond explanation. If she couldn't produce a nodelist on time
or with the right segments, what makes anyone think she can route Netmail.

Nick
--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Hello Paul,

It works nicely on a (Ubuntu) calculator.

A good reason not to use it. It's wrong.

I know that. OTOH, I consider MXM as being correct while adding XI was a pleasant surprise, and suited my intended purpose perfectly.

Do you have Dutch ancestry?

No. But I've got the next best thing. Cajun politicians who
think they are Dutch, mistaking dikes for levees.

You see, we have levees in Louisiana. After Katrina hit New Orleans,
our politicians flew to Holland where the Dutch taught them how to fix
their dikes. Now, do realize levees and dikes are not quite the same
thing. Which means I am doomed. So now I know I'd best keep my pirogue
in unsinkable condition, else there will be no more of me come next
hurricane comes this way.

--Lee

--
Lovin' beats hatin'.

--- MesNews/1.08.05.00-gb
* Origin: news://eljaco.se (2:203/2)

Hello Ward,

Actually from the Province of Zeeland. Don't know if it really
qualifies.

Yes. You feel at home on the roiling deck of seagoing craft.

100%. Boats are part of my life.

I have a pirogue. And a paddle. But it is a bit far for me to paddle
my way to Belgium from Louisiana. OTOH, you are always welcome to come
over and visit in the swamp.

--Lee

--
We Make Your Wet Dreams Come True

--- MesNews/1.08.05.00-gb
* Origin: news://eljaco.se (2:203/2)

Hello Nick,

why anyone would use Janis's unreliable Linux BBBS bullshit is beyond explanation.

BBBS may not be for everyone, but it is reliable.

If she couldn't produce a nodelist on time or with the right segments, what makes anyone think she can route Netmail.

Janis has proved to be a reliable link year after year. Echomail/netmail/files, no issues.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hi! Lee,

On 19 Apr 2021, Lee Lofaso said the following...

thing. Which means I am doomed. So now I know I'd best keep my pirogue
in unsinkable condition, else there will be no more of me come next hurricane comes this way.

Yes. I have seen what may happen. Your best option is to head west. Start practicing Texican, old chap.

Cheers,
Paul.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/32)
* Origin: Quinn's Rock - stuck in a Linux VM, again! (3:640/1384)

Hi! Nick,

On 04/20/2021 12:51 AM, you wrote to Alan Ianson:

Please defend her some more, I smell zone 2 making popcorn.

That wast spicy. Send more, over... Bacon, beans & eggs on the barbie here.

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: A wok is what you throw at a wabbit. (3:640/1384.125)

On 20 Apr 21 08:01:18, Paul Quinn said the following to Nick Andre:

Please defend her some more, I smell zone 2 making popcorn.

That wast spicy. Send more, over... Bacon, beans & eggs on the barbie her

What if I want the food first?

Nick
--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Re: Re: Fews 38:15 [15 [01/07]: General Arti
By: Nick Andre to Alan Ianson on Mon Apr 19 2021 09:51 am

If you're a Janis disciple you likely would get "reliable" service.

I don't know what you are trying to say there.

Janis and I have been linked for mail/files for years.

But she couldn't produce a reliable nodelist. Region 12 stuff would change almost weekly, randomly, for no reason. Date/time stamps of nodelists was sometimes not consistant. This is old news that can be verified by many here.

I read of this but have no idea what the problem was or what the possible solutions could have been.

If she could not manage to produce a silly nodelist reliably and accurately, then routed Netmail at her system cannot be trusted. Period.

Producing a nodelist != routing mail.

That statement is false. I have been getting/sending netmail via Janis's node for a very long time without issue.

Please defend her some more, I smell zone 2 making popcorn.

Janis doesn't need my defense. She has a good track record of reliable service. I hope that zone 2 and all zones for that matter have all the popcorn they want/need. Hot and buttered.

Ttyl :-),
Al

... Canadian DOS Prompt -- EH?:\>
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Hi! Nick,

On 04/20/2021 10:35 AM, you wrote:

X-JAM-FTSKLUDGE: TZUTC: -0500

Please defend her some more, I smell zone 2 making popcorn.

That wast spicy. Send more, over... Bacon, beans & eggs on the

barbie her

What if I want the food first?

Outta luck, dude. At 15 hours behind local time, you're barely on the same calendar date. You could try a snazzy scratch-n-sniff doover.

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Caffeine isn't a drug, it's a vitamin! (3:640/1384.125)

Hi Alan,

why anyone would use Janis's unreliable Linux BBBS bullshit is beyond
explanation.

BBBS may not be for everyone, but it is reliable.

Yes, it is. :)

If she couldn't produce a nodelist on time or with the right segments,
what makes anyone think she can route Netmail.

Janis has proved to be a reliable link year after year. Echomail/netmail/files
no issues.

Thank you Al. Nick seems to like to trash some people on occasion. That's ok, it speaks volumes to me when I see it.

The reason I did not send him my original script to create nodelist/nodediffs was because I figured he was running windows or DOS, and nothing in my script would have made sense to him. He'd be better off rewriting the entire thing from scratch.. I DID send him all the DOS batch files that I were sent to me by my predecessor. Nick never seems to mention that, oh well.

BTW this is the script I used to generate nodelists for all the years I was Z1C. Worked perfectly.

===cut here===
num=`date +%j --date=Friday`
pick=`expr substr $num 2 3`
year=`date +%Y`
cd /home/bbbs/makenl346/makenl-3.4.6/ cp -p inbound/*$num inbound/safe/
cp -p master/*$num inbound/safe/
cp -p update/*$num inbound/safe/
sudo -u bbs cp /home/bbbs/zsegs/ZONE2.A$pick /home/bbbs/makenl346/makenl-3.4.6 /inbound/
sudo -u bbs cp /home/bbbs/zsegs/zone3.z$pick /home/bbbs/makenl346/makenl-3.4.6 /inbound/
sudo -u bbs cp /home/bbbs/zsegs/ZONE4.Z$pick /home/bbbs/makenl346/makenl-3.4.6 /inbound/
sudo -u bbs cp /home/bbbs/zsegs/ZONE5.Z$pick /home/bbbs/makenl346/makenl-3.4.6 /inbound/
#
cd /home/bbbs/makenl346/makenl-3.4.6/ ./makenl -t THURSDAY.CTL
./makenl -p THURSDAY.CTL
./makenl -t makediff.ctl
./makenl -p makediff.ctl
cd /home/bbbs/makenl346/makenl-3.4.6/master sudo -u bbs unzip nodediff.z$pick sudo -u bbs cp nodediff.$num NODEDIFF.$num sudo -u bbs arc a nodediff.a$pick NODEDIFF.$num sudo -u bbs lha a nodediff.l$pick NODEDIFF.$num sudo -u bbs sudo -u bbs cp nodediff.a$pick /home/ftp/pub/nodediff/ sudo -u bbs cp nodediff.z$pick /home/ftp/pub/diffzip/ sudo -u bbs cp nodediff.l$pick /home/ftp/pub/difflzh/ sudo -u bbs cp nodelist.z$pick /home/ftp/pub/nodelist/ echo "nodediff.a$pick Fidonet Nodelist Difference file a$pick" >> /home/ftp/pub
/
nodediff/descript.ion
echo "nodediff.z$pick Fidonet Nodelist Difference file z$pick" >> /home/ftp/pub /
diffzip/descript.ion
echo "nodediff.l$pick Fidonet Nodelist Difference file l$pick" >> /home/ftp/pub /
difflzh/descript.ion
# update Magic lists
cd /home/bbbs
./bbbs bfileidx
cat /home/bbbs/magic.lst |sed 's/a24/a31/g' > newmagic cat /home/bbbs/newmagic |sed 's/z24/z31/g' > newmagic2 cp newmagic2 /home/bbbs/magic.lst
cd /home/bbbs/binkd/
#cp OkFile.Txt OkFile.Txt.safe
cat /home/bbbs/binkd/OkFile.Txt |sed 's/a24/a31/g' > newokfile cat /home/bbbs/binkd/newokfile |sed 's/z24/z31/g' > newokfile2 cp newokfile2 /home/bbbs/binkd/OkFile.Txt
# update my nodelist
cd /home/bbbs/nodelist
sudo -u bbs cp /home/ftp/pub/nodediff/nodediff.a$pick /home/bbbs/nodelist/ cd /home/bbbs
./bbbs blist files.txt &
#
./bbbs bndiff
rm /home/bbbs/nodelist/nodediff.a$pick ./bbbs bnc
cd /home/ftp/pub/nodelist/
echo "nodelist.z$pick FidoNet nodelist for day $num, $year" >> /home/ftp/pub/no d
elist/descript.ion
# zip -jkl /home/ftp/pub/nodelist/nodelist.z$pick /home/bbbs/nodelist/nodelist. $num
#
#

#cd /home/bbbs/##
# ./bbbs bhatch /home/ftp/pub/nodelist/nodelist.z$pick nodelist##
# ./bbbs bhatch /home/ftp/pub/nodediff/noddiff.a$pick nodediff##
# ./bbbs bhatch /home/ftp/pub/diffzip/nodediff.z$pick difflist#
# ./bbbs bhatch /home/ftp/pub/difflzh/nodediff.l$pick difflzh
# ./bbbs bfileidx
cd /home/bbbs
./bbbs bfileidx
./bbbs blist files.txt
sudo -u bbs chmod 755 /home/ftp/pub/node*/node*.?$pick sudo -u bbs chmod 755 /home/ftp/pub/diff*/nodediff.?$pick
#
cd /home/ftp/pub/nodelist
sh ./d2cs.sh > index.html
cd /home/ftp/pub/nodediff
sh ./d2cs.sh > index.html
cd /home/ftp/pub/diffzip
sh ./d2cs.sh > index.html
cd /home/ftp/pub/difflzh/
sh ./d2cs.sh > index.html
cd /home/bbbs
===cut here===

Take care,
Janis

--- BBBS/Li6 v4.10 Toy-5
* Origin: Prism bbs (1:261/38)

On 19 Apr 21 16:41:37, Alan Ianson said the following to Nick Andre:

If she could not manage to produce a silly nodelist reliably and accurately, then routed Netmail at her system cannot be trusted. Perio

Producing a nodelist != routing mail.

On the contrary, having a fairly accurate nodelist makes all the difference when trying to route Netmail.

Janis doesn't need my defense. She has a good track record of reliable service. I hope that zone 2 and all zones for that matter have all the popc they want/need. Hot and buttered.

I stand by all of my posts and hold nothing back. The zone-wars died with the change of regime... though I guess we can thank the Nab in some way for the Fidoweb we have now. Nodelists are automated here with zero problems.

Nick
--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

On 19 Apr 21 20:22:12, Janis Kracht said the following to Alan Ianson:

The reason I did not send him my original script to create nodelist/nodedif was because I figured he was running windows or DOS, and nothing in my scri would have made sense to him. He'd be better off rewriting the entire thin from scratch.. I DID send him all the DOS batch files that I were sent to m by my predecessor. Nick never seems to mention that, oh well.

All in all you gave me a total unworkable mess, which I fixed with the help of someone you love to trash-talk but was willing to make international phone calls from Belgium and sent me a copy of his operation for me to base my rewrite from. He didn't have to do that, but did...

It can now be handed off very easily to someone with even the most basic understanding of MS-DOS instead of the Rube Goldberg contraption you ran where everything was integrated with BBBS. Your scripts were, and are, a MESS.

Zero nodelist problems now, no complaints, no zone-wars, no nothing.

"One day I'll be a great ZC", wasn't that your coy saying?

Nick
--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Janis,

The reason I did not send him my original script to create nodelist/nodediffs was because I figured he was running windows or DOS,
and nothing in my script would have made sense to him.

Just wondering, were you already on Linux Jan.19 2001 when you ascended to the ZC1 position? I have no idea ...

BTW this is the script I used to generate nodelists for all the years I
was Z1C. Worked perfectly.

I beg to differ, as a matter of fact it was very problematic, just not so obvious in Z1.

There were serious issues with your ZONE1-segment which was totally unreliable. It became obvious when in Z2 we started as firstones with the production of a daily nodelist and some of the people began noticing there were discrepancies in Z1 between Friday's information and what was provided on a daily basis for the daily-nodelist.

People started downloading the Z1-Friday nodelist for having a look and we concluded that the Z1-data in ZONE1 flip-flopped from one day to the other, odd things happened to Frank Linhares' segment of which we never could predict which version would be picked out of your archive of expired segments. Information could be a year old and a day later current. New nodes or updated information for nodes often varied from day to day. I think it had something to do with wildcards in MAKENL under Linux and how they are interpreted and resolved.

Just an example of what we got to deal with in the ZONE1-segment for the 1:1/0 entry alone ...

1 Nov 2017 nodelist.305 IFT:60721,ITN:60721
2 Nov 2017 nodelist.306 IFT,ITN
3 Nov 2017 nodelist.307 IFT:60721,ITN:2030
4 Nov 2017 nodelist.308 IFT,ITN
5 Nov 2017 nodelist.309 IFT:60721,ITN:2030
8 Nov 2017 nodelist.312 IFT:60721,ITN:60721
9 Nov 2017 nodelist.313 IFT,ITN
10 Nov 2017 nodelist.314 IFT:60721,ITN:2030
15 Nov 2017 nodelist.319 IFT:60721,ITN:60721
16 Nov 2017 nodelist.320 IFT,ITN
17 Nov 2017 nodelist.321 IFT:60721,ITN:2030

Nearly every day something else for just that one single line... but, in Z1 it didn't show ... it showed in what you sent the other ZCs and you were notified more than once by several of us here ...

I'm not claiming you were a total bitch because every time I needed support it was given, but your nodelist-production was below par ... often. I think it was a manual operation and not automated.

Let me also add that 24hrs after Nick Andre became ZC1, the Zone Warz abruptly halted. It was nearly boring how quietly it suddenly became.

Your role in the FIDONEWS-putsch will also not be forgotten, it is archived and can be regurgitated at any time by those involved.

Having said that, and contrary to what some may believe, I have no problem with you.

Enjoy the day,

\%/@rd

--- DB4 - Apr.15 2021
* Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)

Hello Alan,

On Monday April 19 2021 02:45, you wrote to me:

He does, he has a direct link with me. I got your PINg responze
via that link. So I wonder why he does not use that link to route
all mail for net 280 to me...

I did ask Dallas about that and he told me he routes mail for zone 2
via 261/38, Nick Andre.

Hmmm...

I'm not sure if that means he is routing via Janis 1:261/38 or Nick 1:229/426. If he did route Wilfred's reply via 229/426 it may be on
hold there for Wilfred, but I have no way to know.

It should work anyway. Wilfred has a direct link with Nick and I have direct links with both Janis and Nick. And even if Nick or Janis do not directly route to R28, their default route is via Ward and R28 has multiple direct links with Ward.

I would say, that if mail routed via Dallas does not reach R28, there is a problem at Dallas' end.

I have more confidence in Tommi so I will route mail for net 280 (and
zone 2, for the most part) that way and since 153/7715 is working for
your node I'll keep routing 280/5555 to 153/7715.

That is fine with me, but doesn't solve the other problems at Dallas' end.

I also asked Dallas about mail for 153/0 and he seemed to think mail
for 153/0 was on hold for my node. I poll 153/7715 several times a day
and I have not seen that message. I hope that Dallas has eyes on that
and will get mail I need to see to me.

Dallas is your RC, so the two of you are responsible for that part of the smmooth operation of the network...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)

Hello Ward!

20 Apr 21 13:32, you wrote to Janis Kracht:

think it had something to do with wildcards in MAKENL under Linux and how they are interpreted and resolved.

The way you use wildcards in Makenl, does not work on *nix system.
To keep it short as the code originates from DOS, lets call it a bug in *nix.

I do understand what caused the irregular results in the daily updates,
that Janis produced, but I cannot not in just a few words, so I will refrain
from trying to explain.

The quick solution is to remove all region updates from the master directory,
and offer all current region updates from an archive directory. The updates
will all get the daynumber of the current publishing day and be included
in the nodelist.

I tried to explain this to Janis, but I failed.

Kees

--- GoldED+/LNX 1.1.5--b20180707
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

Hello Paul,

thing. Which means I am doomed. So now I know I'd best keep my pirogue
in unsinkable condition, else there will be no more of me come next
hurricane comes this way.

Yes. I have seen what may happen. Your best option is to head west. Start
practicing Texican, old chap.

Texas is a fine country, but Texican women ... they're so ugly they'd
back a buzzard off a gut wagon.

--Lee

--
Hands too small! Can't build a wall!

--- MesNews/1.08.05.00-gb
* Origin: news://eljaco.se (2:203/2)

Hello Alan,

If you're a Janis disciple you likely would get "reliable" service.

I don't know what you are trying to say there.

Janis and I have been linked for mail/files for years.

I have never had a problem with Janis in regards to Fidonet.
There is only one incident that I know of in which an individual
had a problem with her. And he was drunk at the time. And also
apologized to her afterwards. Really his fault, not hers.

But she couldn't produce a reliable nodelist. Region 12 stuff would

change

almost weekly, randomly, for no reason. Date/time stamps of nodelists

was

sometimes not consistant. This is old news that can be verified by

many

here.

I read of this but have no idea what the problem was or what the possible solutions could have been.

Had it been important, or a real problem, sysop(s) would have noticed
and done something about it. But since that didn't happen ...

If she could not manage to produce a silly nodelist reliably and
accurately, then routed Netmail at her system cannot be trusted. Period.

Producing a nodelist != routing mail.

That statement is false. I have been getting/sending netmail via Janis's node for a very long time without issue.

And it is only *now* that somebody claims to have a problem?

Please defend her some more, I smell zone 2 making popcorn.

Janis doesn't need my defense. She has a good track record of reliable service. I hope that zone 2 and all zones for that matter have all the popcorn they want/need. Hot and buttered.

Yeah. The popcorn is much better than Canadian french fries.

--Lee

--
It takes a tough man to make a tender chicken

--- MesNews/1.08.05.00-gb
* Origin: news://eljaco.se (2:203/2)

Hello Janis,

why anyone would use Janis's unreliable Linux BBBS bullshit is beyond
explanation.

BBBS may not be for everyone, but it is reliable.

Yes, it is. :)

If she couldn't produce a nodelist on time or with the right segments,
what makes anyone think she can route Netmail.

Janis has proved to be a reliable link year after year.
Echomail/netmail/files
no issues.

Thank you Al. Nick seems to like to trash some people on occasion. That's ok, it speaks volumes to me when I see it.

You have to forgive him. He's from America Jr.

The reason I did not send him my original script to create nodelist/nodediffs was because I figured he was running windows or DOS, and
nothing in my script would have made sense to him. He'd be better off rewriting the entire thing from scratch.. I DID send him all the DOS batch files that I were sent to me by my predecessor. Nick never seems to mention that, oh well.

It's not complicated.

BTW this is the script I used to generate nodelists for all the years I was
Z1C. Worked perfectly.

Sure does. Thanks, Janis!

--Lee

--
Probably the best beer in the world

--- MesNews/1.08.05.00-gb
* Origin: news://eljaco.se (2:203/2)

Hello Nick,

It can now be handed off very easily to someone with even the most basic understanding of MS-DOS instead of the Rube Goldberg contraption you ran where everything was integrated with BBBS. Your scripts were, and are, a MESS.

I decline the nomination, thankyouberrymuch.

Zero nodelist problems now, no complaints, no zone-wars, no nothing.

"One day I'll be a great ZC", wasn't that your coy saying?

That's right. Nobody could do it like Janis.

--Lee

--
Erections, That's Our Game

--- MesNews/1.08.05.00-gb
* Origin: news://eljaco.se (2:203/2)

Re: FidoNews 38:15 [01/07]: General Articles
By: Michiel van der Vlist to Alan Ianson on Tue Apr 20 2021 03:36 pm

It should work anyway. Wilfred has a direct link with Nick and I have direct links with both Janis and Nick. And even if Nick or Janis do not directly route to R28, their default route is via Ward and R28 has multiple direct links with Ward.

Yes, it should. We can never tell what direction a route may take but those replies should arrive one way or another at the destination.

I would say, that if mail routed via Dallas does not reach R28, there is a problem at Dallas' end.

There might be. I have brought that up so Dallas has eyes on it.

I have more confidence in Tommi so I will route mail for net 280
(and zone 2, for the most part) that way and since 153/7715 is
working for your node I'll keep routing 280/5555 to 153/7715.

That is fine with me, but doesn't solve the other problems at Dallas' end.

The ping responder that I am using has a feature to allow nodes to select one of my links to route via. I had commented out this language from the replies but have now uncommented it. You can place "%routeto: 1:153/7715" on the subject line and your reply will be routed to that node. You can also place "%links" on the subject line to get a list of links to route your reply via.

The possible nodes here are 1:153/7715, 1:229/426, 1:261/38, 1:3634/12 and 3:770/1. Perhaps that will help to show us where problems exist and what needs to be done to solve them.

Dallas is your RC, so the two of you are responsible for that part of the smmooth operation of the network...

Yes, and I have always found Dallas to be an easy person to talk to. If problems continue Dallas and I will keep at it and get to a solution.

Ttyl :-),
Al

... Crime doesn't pay... does that mean my job is a crime?
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Re: Fews 38:15 [15 [01/07]: General Arti
By: Lee Lofaso to Alan Ianson on Tue Apr 20 2021 07:43 pm

And it is only *now* that somebody claims to have a problem?

There are always problem and there are solutions for those problems when sysops cooperate.

Yeah. The popcorn is much better than Canadian french fries.

If fries are not your thing, try the poutine!

Ttyl :-),
Al

... Air conditioned environment - Do not open Windows
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Kees,

think it had something to do with wildcards in MAKENL under Linux
and how they are interpreted and resolved.

The way you use wildcards in Makenl, does not work on *nix system.

Yes ... and ??

The quick solution is to remove all region updates from the master directory, ...

The solution is not to maintain expired REGION-segments up to 3 years old in the master-directory ...

I tried to explain this to Janis, but I failed.

... that is what "I" advised Janis. She agreed.

\%/@rd

--- DB4 - Apr.15 2021
* Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)

Hi! Lee,

On 04/21/2021 03:43 AM, you wrote:

Texas is a fine country, but Texican women ... they're so ugly they'd
back a buzzard off a gut wagon.

Oh Lee! You can be awful sometimes.

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Whip me, Master, whip me ...OOPS!... wrong echo ;-) (3:640/1384.125)

Re: FidoNews 38:15 [01/07]: General Articles
By: Michiel van der Vlist to Kostie Muirhead on Sun Apr 18 2021 09:11 pm

Nothing yet...

I saw two ping netmails from you come through here today, though they both hit just before I had full logging back up. Looks like at least one was destined for 2:280/something though? Did they get where you wanted them, and how did you route them?
===
Underminer - The Undermine BBS
--- SBBSecho 3.14-Linux
* Origin: The Undermine BBS - 1:342/17 (1:342/17)

On 20 Apr 21 15:36:30, Michiel Van Der Vlist said the following to Alan Ianson:

It should work anyway. Wilfred has a direct link with Nick and I have direc links with both Janis and Nick. And even if Nick or Janis do not directly

You have not had a direct-link with my system for quite some time now, since your superior intellect felt the need to accuse me of reading in-transit Netmail destined for that stupid NAB placeholder at 1:1/21... or whatever it was. After that, I remember bluntly telling you to take a long hike.

Nick
--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

Hello Alan,

And it is only *now* that somebody claims to have a problem?

There are always problem and there are solutions for those problems when sysops cooperate.

The best sysops are like musicians. Always collaborating with others
to create the perfect piece.

Yeah. The popcorn is much better than Canadian french fries.

If fries are not your thing, try the poutine!

I've had that. Once. By mistake. In Montreal.

Went to a restaurant. Tried to order mashed potatoes. Only one
problem. There is no word for "mashed" potatoes in Cajun French.
Only thing I could do was make hand gestures, such as pounding
one fist into the palm of my other hand, making kind of a
grinding motion at th same time. What I got looked like french
fries with cheese curds and brown gravy on top.

Canadians are a special people. They refused to charge me
for my meal, realizing I was from Louisiana. Or maybe because
they found my version of French to be amusing. Either way,
it was an experience to remember.

--Lee

--
Get Her Wet Here

--- MesNews/1.08.05.00-gb
* Origin: news://eljaco.se (2:203/2)

Re: Fews 38:15 [15 [01/07]: General Arti
By: Lee Lofaso to Alan Ianson on Wed Apr 21 2021 03:37 pm

If fries are not your thing, try the poutine!

I've had that. Once. By mistake. In Montreal.

Poutine is not for everyone. I don't care for it.

If my lady friends see's poutine on the menu she orders it if she is hungry or not.

Ttyl :-),
Al

... Remember when safe sex meant not getting caught?
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Hi Alan,

On 2021-04-21 15:52:53, you wrote to Lee Lofaso:

If fries are not your thing, try the poutine!

I've had that. Once. By mistake. In Montreal.

Poutine is not for everyone. I don't care for it.

If my lady friends see's poutine on the menu she orders it if she is hungry
or not.

I almost get a heart attack just by looking at pictures of it... ;)

Bye, Wilfred.

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