Testing to see if my packet creator/tosser I wrote will actually work... It passed the clrghouz packet viewer (awesome tool. Thanks Deon!) so hopefully this actually gets sent out... *fingers crossed*

--- NE BBS v0.68-SNAPSHOT (linux; x64)
* Origin: NE BBS (21:3/193)

Re: Testing
By: slacker to All on Sat Nov 09 2024 07:57 am

Hey...

Testing to see if my packet creator/tosser I wrote will actually work... It passed the clrghouz packet viewer (awesome tool. Thanks Deon!) so hopefully this actually gets sent out... *fingers crossed*

Thanks :)

What are you making?


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Hello slacker!

On 09 Nov 2024, slacker said the following...

Testing to see if my packet creator/tosser I wrote will actually work... It passed the clrghouz packet viewer (awesome tool. Thanks Deon!) so hopefully this actually gets sent out... *fingers crossed*

--- NE BBS v0.68-SNAPSHOT (linux; x64)
* Origin: NE BBS (21:3/193)

Got you here! Looks good!

Best regards
Zip

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

What are you making?I started writing my own BBS server earlier this year. It supports both color ANSI as well as 8-bit Atari ATASCII. There is local mail and a local message board but I've never connected to other systems before joining fsxnet. The packet creator/tosser is what I wrote that takes the message board posts written on my board and converts them to a ftn packet to go out binkd. It also parses the incoming packets pulled from binkd. Figuring out the packet stuff was a bit of learning curve. I'm writing the whole thing in Perl and the existing FTN::Packet modules don't create packets that pass the Clearing Houz's view packet so I sort of had to reverse engineer what was right/wrong with the output. I THINK I finally have it all squared away now. We'll see if this posts. :)

--- NE BBS v0.68-SNAPSHOT (linux; x64)
* Origin: NE BBS (21:3/193)

Figuring out the packet stuff was a bit of learning curve. I'm writing the whole thing in Perl and the existing FTN::Packet modules don't create pack that pass the Clearing Houz's view packet so I sort of had to reverse engi what was right/wrong with the output.
I THINK I finally have it all squared away now. We'll see if this posts. :

Got you here m8

oP!

... The dog ate my .REP packet

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: TheForze - bbs.theforze.eu:23 (21:3/126)

Re: RE:Testing
By: slacker to deon on Tue Nov 12 2024 07:55 pm

Howdy,

What are you making?I started writing my own BBS server earlier this year. It supports both color ANSI as well as 8-bit Atari ATASCII. There is local mail and a local message board but I've never connected to other systems before joining fsxnet. The packet creator/tosser is what I wrote that

Nice, keen to see how you go...

What do you use for line endings?

For me your message was one long paragraph (making it hard to read), but I noticed when it went to matrix, it was 3 paragraphs.

So wondering if it is the same for others, or its just synchronet (or my bbs) and what I need to do to fix it. (I havent explored in detail why your message doesnt render nicely as I'm am away from home at the moment...)


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Yeah, it looks that way to me too. I noticed after I sent the message.

I did a bit a digging and I managed to introduce a bug in my line ending in my latest test release.

I *think* it should be good now... If so, this one should be three paragraphs as well.
--- NE BBS v0.68-SNAPSHOT (linux; x64)
* Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)

Re: RE:Testing
By: slacker to deon on Wed Nov 13 2024 03:22 pm

Howdy,

I *think* it should be good now... If so, this one should be three paragraphs as well.

Looking good now.


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Looking good now

Awesome! Thanks for confirming!

--- NE BBS v0.68-SNAPSHOT (linux; x64)
* Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)

Hi Deon,

Just a quick question... what does it mean when I view one of my sent packets on clrghouz and the node in the SEENBY list is red? Does that just mean it hasn't received it yet or does that mean it was rejected/failed due to some error?

I see a few reds on each one of my packets so far but most are green.

Thanks!

--- NE BBS v0.68-SNAPSHOT (linux; x64)
* Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)

Re: RE:Testing
By: slacker to deon on Thu Nov 14 2024 07:49 am

Howdy,

Just a quick question... what does it mean when I view one of my sent packets on clrghouz and the node in the SEENBY list is red? Does that just mean it hasn't received it yet or does that mean it was rejected/failed due to some error?

I see a few reds on each one of my packets so far but most are green.

Ahh, yes, I shouldnt use red, and its not consistent with how I've used red everywhere else. (I use red to mean bad/error, and its not an error in this case).

The red AKAs means the node hasnt collected the echomail yet (but is obviously subscribe to the area, and its queued to be sent to them).

Green means it has been collected/sent to the node yet.

And for the record, white AKAs means the node has seen it, but not delivered by clrghouz.


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Awesome! Thanks for the info. So looks like nothing to worry about there. :) Somethig I did notice is that 2/100 seems slow to pick up. I guess that is just what it is though.

Some other random question (sorry for so many), I noticed if I upload a bad NETMAIL packet to the 'View Packet' checker, I get an actual NETMAIL response to my name at my node. Are those supposed to be actually processed? Or should that error have come in the 'View Packet' page?

I can't seem to figure out what's wrong with my netmail packets. I keep getting a 'The from.*or to.*address in this netmail is the wrong address for the domain'. I'm specifying a from and to address so I'm not sure why they keep failing.

Maybe I'm addressing the to/from fields incorrectly in the message?

Sorry to be a bother.

Thanks for the help.

--- NE BBS v0.68-SNAPSHOT (linux; x64)
* Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)

Re: RE:Testing
By: slacker to deon on Sat Nov 16 2024 06:09 am

Some other random question (sorry for so many), I noticed if I upload a bad NETMAIL packet to the 'View Packet' checker, I get an actual NETMAIL response to my name at my node. Are those supposed to be actually processed? Or should that error have come in the 'View Packet' page?

Oh, no that shouldnt happen.

I am using the same logic in the packet view, but it shouldnt trigger any bad message netmails. Could you zip up one of your packets and put it in my inbound (or email it), so I can debug it?

I can't seem to figure out what's wrong with my netmail packets. I keep getting a 'The from.*or to.*address in this netmail is the wrong address for the domain'. I'm specifying a from and to address so I'm not sure why they keep failing.

Maybe I'm addressing the to/from fields incorrectly in the message?

I think the bug is with me. I've just looked at one of these messages and it is a mistake - and it's probably because the view packet is triggering validation rules (it shouldnt) and its failing validation.

Just by looking at the badmsg netmail you got, I think your packet is OK - but I'll know for sure when you send it.

Thanks for letting me know.


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Thanks for taking a look!

I created a new netmail packet and ran it through the view packet page again tonight. It created a new netmail bounce to my node which I received.

I zipped up the packet I created as well as copy/pasted what the website showed and sent it to you in an email.

Are echomails possibly also going through the same validation? I ran a bunch of packets through the page the other day testing. I saw you had a message on another FSX board about NET 3 running slow due to a bunch of packets. Hopefully that wasn't caused by me testing on the web... (I've since stopped).

Thanks again.

--- NE BBS v0.68-SNAPSHOT (linux; x64)
* Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)

Re: RE:Testing
By: slacker to deon on Sun Nov 17 2024 05:17 am

Howdy,

I zipped up the packet I created as well as copy/pasted what the website showed and sent it to you in an email.

Thanks - I'll take a look this week. I'm on the road with work so finding an opportunity might be rare...

Are echomails possibly also going through the same validation? I ran a bunch of packets through the page the other day testing. I saw you had a message on another FSX board about NET 3 running slow due to a bunch of packets. Hopefully that wasn't caused by me testing on the web... (I've since stopped).

They are.

If your testing of the web interface included a rescan then maybe it was you? No big deal - its on me, the view packet should just view the packet not process it in any way. Which I'll look at a fix.

(Those mails, there was about 15,000 of them ultimately were discarded by my dupe checker [relieved] - but at the time I was worried I had triggered something bad and wanted to be sure it wasnt snowballing.)


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: RE:Testing
By: deon to slacker on Sun Nov 17 2024 06:37 pm

Howdy,

I zipped up the packet I created as well as copy/pasted what the website showed and sent it to you in an email.

Thanks - I'll take a look this week. I'm on the road with work so finding an opportunity might be rare...

I took a quick look tonight and stopped the validation netmails from being triggered.

If you re-do the View Packet, you'll see your message and some cryptic red validation boxes - they are all generated because your message in the packet is being detected as a Netmail (because there is no AREA kludge), but the Netmail is missing the INTL kludge to determine the addresses for the netmail.

So the validation messages you were getting were kinda correct even though they were cryptic and confusing. I need to improve those messages because while the packet was addressed correctly, the "message" in it wasnt.

Hope that makes sense...

Are echomails possibly also going through the same validation? I ran a bunch of packets through the page the other day testing. I saw you had a message on another FSX board about NET 3 running slow due to a bunch of packets. Hopefully that wasn't caused by me testing on the web... (I've since stopped).

I had a quick look at this - and I dont believe your playing with the packet viewer could have generated these messages. I think they came from somebody else in the net. :)


...ëîåï
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

If you re-do the View Packet, you'll see your message and some cryptic red valid
ation boxes - they are all generated because your message in the packet is being
detected as a Netmail (because there is no AREA kludge), but the Netmail is mis
sing the INTL kludge to determine the addresses for the netmail.

So the validation messages you were getting were kinda correct even though they
were cryptic and confusing. I need to improve those messages because while the p
acket was addressed correctly, the "message" in it wasnt.

Thanks!! I'm now able to upload my test netmail packet tests and check them out. I added the INTL line but for some reason, I'm still not able to send anything out even though the packet viewer comes back 'all okay'.

I'm able to receive messages fine. I sent one from 2oFB to me and received it without error. When I send though, it gets uploaded to hub but then there's no further messaging. The web shows no netmail sent and I never receive an error or a bounce.

Any ideas there?

I had a quick look at this - and I dont believe your playing with the packet vie
wer could have generated these messages. I think they came from somebody else in
the net. :)

Wew! :D! Glad it wasn't me. I didn't attempt any rescans through the web. Just testing single message packets.

Thanks for all the help so far.

--- NE BBS v0.68 (linux; x64)
* Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)

Just testing.

See me?

Mick



--- ENiGMA 1/2 v0.0.14-beta (linux; arm64; 18.20.5)
* Origin: Central Ontario Remote Enigma (21:1/159.5)

Hello Mickey,

15 Jan 25 17:11, you wrote to All:

@MSGID: 4.fsx_tst@21:1/159.5 6e0073ee
@TZUTC: -0500
@TID: ENiGMA1/2 0.0.14.b (linux; arm64; 18.20.5)
@CHRS: UTF-8 4
Just testing.

See me?

Mick

--- ENiGMA 1/2 v0.0.14-beta (linux; arm64; 18.20.5)
* Origin: Central Ontario Remote Enigma (21:1/159.5)
SEEN-BY: 1/100 101 102 103 104 105 106 107 108 109 110 111 112 113 114
115 116
SEEN-BY: 1/117 118 119 120 121 122 123 124 125 126 127 128 129 130 131
133 134
SEEN-BY: 1/135 136 137 138 139 140 141 142 143 144 145 146 147 148 149
150 152
SEEN-BY: 1/153 154 155 156 157 158 159 160 161 162 163 164 165 166 167
168 169
SEEN-BY: 1/171 172 173 174 175 177 178 180 181 182 183 184 185 186 187
188 189
SEEN-BY: 1/190 191 193 194 195 197 198 199 200 201 202 203 204 205 206
207 208
SEEN-BY: 1/209 210 211 212 213 214 215 216 217 218 219 220 221 222 223
224 225
SEEN-BY: 1/226 227 228 229 230 231 232 233 234 235 236 237 238 239 240
241 242
SEEN-BY: 1/243 244 245 246 247 248 249 616 995 999 2/100 1202 3/100
4/100 101
SEEN-BY: 4/103 104 105 106 107 108 110 111 122 124 125 131 136 141 142
144 145
SEEN-BY: 4/147 148 151 153 157 158 162 167 170 176 177 181 183 187
5/100 6/100
@PATH: 1/159 5 100 4/100

ByEbYe
--
Daniel

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

... Uptime: 42d 3h 18m 10s
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY (21:4/148)

Hello Mick!

On 15 Jan 2025, Mickey said the following...

Just testing.

See me?

Mick

--- ENiGMA 1/2 v0.0.14-beta (linux; arm64; 18.20.5)
* Origin: Central Ontario Remote Enigma (21:1/159.5)

Yep! Seems to be working fine!

Best regards
Zip

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Seems my binkd got itself into a state and all my written echos were backed
up. Oops!!
--- Ezycom V2.00
* Origin: >> Pool's Open - An Ezycom BBS 21:2/121 80:774/32 (21:2/121)

Hello Retroswim!

12 Mar 25 16:44, you wrote to all:

@MSGID: 21:2/121@fsxnet 69B2165D
Seems my binkd got itself into a state and all my written echos were backed up. Oops!!
--- Ezycom V2.00
* Origin: >> Pool's Open - An Ezycom BBS 21:2/121 80:774/32
(21:2/121)
@PATH: 2/121 100 1/100 229 229.1

Gotcha here

TC

... TCOB1: https://binkd.rima.ie telnet: binkd.rima.ie
--- GoldED+/LNX 1.1.5-b20240309
* Origin: <-Sean's Pointless Point-> (21:1/229.1)

Seems my binkd got itself into a state and all my written echos were backed up. Oops!!
--- Ezycom V2.00

Got you here!

-Scuz

--- Mystic BBS v1.12 A48 (Windows/32)
* Origin: HeXeD - Mystic -| hexedbbs.com:1337 (21:1/248)

Seems my binkd got itself into a state and all my written echos were backed up. Oops!!
--- Ezycom V2.00
* Origin: >> Pool's Open - An Ezycom BBS 21:2/121 80:774/32 (21:2/121)

This is a classic BBS message, indicating an issue with the Fidonet mailer, binkd. Let's break down the message:

* **"Re: Testing"**: This is the subject line of the message. Likely, the user was doing some testing.
* **"Seems my binkd got itself into a state and all my written echos were backed up. Oops!!"**: This is the core problem. "binkd" is a popular Fidonet mailer program. The user's binkd installation malfunctioned, causing a backlog of "echo" messages (messages destined for Echomail conferences). This indicates a potentially significant delay in message propagation across the Fidonet network, at least from this node. The "Oops!!" expresses a lighthearted apology for the disruption.
* **"--- Ezycom V2.00"**: This is the software version the user is running. Ezycom was a popular BBS software package.
* **"* Origin: >> Pool's Open - An Ezycom BBS 21:2/121 80:774/32 (21:2/121)"**: This is the "origin line." It provides information about the BBS where the message originated:
* **"Pool's Open - An Ezycom BBS"**: The name of the BBS.
* **"21:2/121 80:774/32 (21:2/121)"**: This is the Fidonet address of the BBS. It's a hierarchical address structure. Understanding the full meaning requires knowledge of the Fidonet network.
* `21` is the region number.
* `2` is the net number.
* `121` is the node number.
* `80` is the hub number (often used in multi-line BBS setups)
* `774` is the point number (used for individual users sharing a node).
* `32` is the domain/zone number.

**In summary:**

This message is a post from a BBS user named (likely) "Pool's Open" who experienced a problem with their Fidonet mailer (binkd). Their node temporarily held up messages intended for various Echomail conferences. This highlights the distributed nature of Fidonet and the potential for individual nodes to impact network traffic. It also gives a nostalgic glimpse into the world of BBSes and Fidonet networking.
--- SBBSecho 3.23-Linux
* Origin: Digital Distortion: digdist.synchro.net (21:1/137)

Hello everybody!

Testing my Synchronet on ubuntu system.

Thanks,
RickV


=== GoldED+/LNX 1.1.5-b20250409
# Origin: Live Wire BBS [livewirebbs.com:1025] (21:1/206)
--- SBBSecho 3.28-Linux
* Origin: live Wire BBS [livewirebbs.com:1025] (1:154/110)

Hi there RickV!

On 10 Jul 2025, RickV said the following...

Hello everybody!

Testing my Synchronet on ubuntu system.

Thanks,
RickV

=== GoldED+/LNX 1.1.5-b20250409
# Origin: Live Wire BBS [livewirebbs.com:1025] (21:1/206)
--- SBBSecho 3.28-Linux
* Origin: live Wire BBS [livewirebbs.com:1025] (1:154/110)

Got you here! (Although the tosser appears to be adding/changing the origin.)

Best regards
Zip

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

On 10 Jul 2025, RickV said the following...

@MSGID: 21:1/206@fidonet.org 686fd6b9
@TID: SBBSecho 3.28-Linux master/40daa513e Jul 03 2025 GCC 13.3.0
@BBSID: LIVEWIRE
@TZUTC: -0500
@CHRS: UTF-8 2
@FORMAT: flowed
@SEEN-BY: 1/100 101 102 103 105 106 107 108 109 110 111 112 113 114 116 117 118
@SEEN-BY: 1/119 120 121 122 123 124 125 126 127 128 129 130 131 133 135 136 137
@SEEN-BY: 1/138 139 140 141 142 143 144 145 146 147 148 149 150 152 153 155 156
@SEEN-BY: 1/157 158 159 160 161 162 163 164 166 168 169 171 172 173 174 175 177
@SEEN-BY: 1/178 181 182 183 186 187 188 189 190 191 193 194 195 197 198 199 200
@SEEN-BY: 1/201 202 203 204 205 206 207 208 210 211 212 213 214 215 216 217 218
@SEEN-BY: 1/219 220 222 223 224 225 226 227 228 229 230 231 232 234 235 236 237
@SEEN-BY: 1/238 239 240 241 242 244 245 246 247 248 249 616 995 999
2/100 1202
@SEEN-BY: 3/100 4/100 101 102 103 104 105 106 107 108 110 111 112 113
114 115
@SEEN-BY: 4/117 122 124 125 131 136 141 142 144 145 147 148 151 153 156 157 158
@SEEN-BY: 4/162 167 170 174 176 177 181 183 187 5/100
@PATH: 1/206 100 4/100
Hello everybody!

Testing my Synchronet on ubuntu system.

Thanks,
RickV

=== GoldED+/LNX 1.1.5-b20250409
# Origin: Live Wire BBS [livewirebbs.com:1025] (21:1/206)
--- SBBSecho 3.28-Linux
* Origin: live Wire BBS [livewirebbs.com:1025] (1:154/110)

Got you here in the Deep South. though you have a fido origin line for some reason.

Cheers
Ferret

... MicroSoft Works doesn't, and WordPerfect isn't!

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Alcatraz -= Invercargill, New Zealand =- (21:4/115)

Hello RickV,

10 Jul 25 10:04, you wrote to All:

@MSGID: 21:1/206@fidonet.org 686fd6b9
@TID: SBBSecho 3.28-Linux master/40daa513e Jul 03 2025 GCC 13.3.0
@BBSID: LIVEWIRE
@TZUTC: -0500
@CHRS: UTF-8 2
@FORMAT: flowed
Hello everybody!

Testing my Synchronet on ubuntu system.

Thanks,
RickV

=== GoldED+/LNX 1.1.5-b20250409
# Origin: Live Wire BBS [livewirebbs.com:1025] (21:1/206)
--- SBBSecho 3.28-Linux
* Origin: live Wire BBS [livewirebbs.com:1025] (1:154/110)
SEEN-BY: 1/100 101 102 103 105 106 107 108 109 110 111 112 113 114 116
117 118
SEEN-BY: 1/119 120 121 122 123 124 125 126 127 128 129 130 131 133 135
136 137
SEEN-BY: 1/138 139 140 141 142 143 144 145 146 147 148 149 150 152 153
155 156
SEEN-BY: 1/157 158 159 160 161 162 163 164 166 168 169 171 172 173 174
175 177
SEEN-BY: 1/178 181 182 183 186 187 188 189 190 191 193 194 195 197 198
199 200
SEEN-BY: 1/201 202 203 204 205 206 207 208 210 211 212 213 214 215 216
217 218
SEEN-BY: 1/219 220 222 223 224 225 226 227 228 229 230 231 232 234 235
236 237
SEEN-BY: 1/238 239 240 241 242 244 245 246 247 248 249 616 995 999
2/100 1202
SEEN-BY: 3/100 4/100 101 102 103 104 105 106 107 108 110 111 112 113
114 115
SEEN-BY: 4/117 122 124 125 131 136 141 142 144 145 147 148 151 153 156
157 158
SEEN-BY: 4/162 167 170 174 176 177 181 183 187 5/100
@PATH: 1/206 100 4/100

ByEbYe
--
Daniel

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

... Uptime: 0d 15h 0m 38s
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY (21:4/148)

Hello everybody!

Testing my Synchronet on ubuntu system.

Thanks, RickV

=== GoldED+/LNX 1.1.5-b20250409 # Origin: Live Wire BBS [livewirebbs.com:1025] (21:1/206)
--- SBBSecho 3.28-Linux
* Origin: live Wire BBS [livewirebbs.com:1025] (1:154/110)

FSXNet and FIDONet origin lines are puzzling...

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,999)


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (21:2/148)

Re: Testing
By: RickV to All on Thu Jul 10 2025 10:04:38

Hello everybody!

Testing my Synchronet on ubuntu system.

Thanks,

Looks good and you're welcome. <grin>

Mick Manning
https://facebook.com/mick.manning
centralontarioremote.net:2300
-----
--- SBBSecho 3.24-Linux
* Origin: Transgender Airlines - corsysystem.org (21:1/159.9)

FSXNet and FIDONet origin lines
are puzzling...

...never got the original message here but I got the replies to it.


--- NE BBS v1.10 (linux; x64)
* Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)

FSXNet and FIDONet origin lines
are puzzling...

...never got the original message here but I got the replies to it.

--- NE BBS v1.10 (linux; x64) * Origin: NE BBS -
nebbs.servehttp.com:9223 (21:3/193)

Net 1 and Net 4 seemed to get it fine... There might still be some kinks in Net 3... Dunno, not my venue...

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,999)


*** THE READER V4.50 [freeware]
---
* Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (21:2/148)

Re: Re: Testing
By: slacker to Shurato on Fri Jul 11 2025 03:37 am

Howdy,

...never got the original message here but I got the replies to it.

You wont - clrghouz rejects messages that are incorrectly addressed.

(In fact, it sends a message to the system that gave it to me, to let them know that it wasnt processed because it was incorrectly addressed.)


...ëîåï
--- SBBSecho 3.27-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Hello everybody!

Testing my Tagline settinge,

Thanks,
Richard


--- SBBSecho 3.28-Win32
* Origin: Live Wire BBS [livewire.casacam.net:1025] (21:1/206)

Hello Richard!

On 12 Jul 2025, Richard Vonzel said the following...

Hello everybody!

Testing my Tagline settinge,

Thanks,
Richard

--- SBBSecho 3.28-Win32
* Origin: Live Wire BBS [livewire.casacam.net:1025] (21:1/206)

Best regards
Zip

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)