Yeap, fresh new Linux BBS written in C. First time post to real Echomail area.

System time is UTC, and character encoding is UTF-8. (well at least it
supposed to be)
---
* Origin: -={ The Digital Post }=- (1:266/625.0)

06 Jun 26 17:18:30 Scott Street (1:266/625) wrote:

==== begin of the message ====
@PID: SeaNet BBS v0.02-dev-31-g48346e3(release)
@MSGID: 1:266/625 6a24566667e12160
@TZUTC: +0000
@CHRS: UTF-8 4
@TID: hpt/lnx 1.9 2024-03-02
Yeap, fresh new Linux BBS written in C. First time post to real Echomail area.

System time is UTC, and character encoding is UTF-8. (well at least it
supposed to be)
---
+ Origin: -={ The Digital Post }=- (1:266/625.0)
SEEN+BY: 1/19 100 16/0 19/36 37 105/81 106/201 123/130 124/5009 128/187 129/12 SEEN+BY: 129/14 102 125 160 165 134/101 142/104 799 153/7715 154/110 201/0 SEEN+BY: 203/0 218/700 221/0 1 6 226/30 227/114 229/110 112 200 206 300 307 SEEN+BY: 229/317 400 426 428 452 470 664 700 705 240/1120 5832 261/1 20 266/75 SEEN+BY: 266/325 512 618 625 630 267/152 154 280/464 5003 5555 291/111 292/854 SEEN+BY: 301/1 320/119 219 319 2119 322/757 762 325/304 342/19 200 396/45 SEEN+BY: 423/81 460/58 633/280 712/848 902/26 5075/35
@PATH: 266/625 512 229/426 320/219 221/1
==== end of the message ====

---
* Origin: RBB Test Robot @ FIDOTEST (2:221/360)

Yeap, fresh new Linux BBS written in C. First time post to real Echomail area.

I think it worked


--- Platinum Xpress/Win/WINServer v10.0b25
* Origin: Joe's WildCat BBS -= Telnet 2300 , HTTP 80 =- (1:342/200)

Hi Scott,

On 2026-06-06 17:18:30, you wrote to All:

@MSGID: 1:266/625 6a24566667e12160
@PID: SeaNet BBS v0.02-dev-31-g48346e3(release)
@TZUTC: +0000

That is probably not right...

@CHRS: UTF-8 4
@TID: hpt/lnx 1.9 2024-03-02
Yeap, fresh new Linux BBS written in C. First time post to real Echomail
area.

System time is UTC, and character encoding is UTF-8. (well at least it supposed to be)
---
* Origin: -={ The Digital Post }=- (1:266/625.0)
SEEN-BY: 1/19 100 16/0 19/36 37 103/705 105/81 106/201 123/130 124/5009 SEEN-BY: 124/5016 128/187 129/12 14 102 125 160 165 134/101 142/104 SEEN-BY: 142/799 153/757 7715 154/10 30 110 201/0 203/0 218/700 221/0 SEEN-BY: 221/1 6 226/30 227/114 229/110 112 200 206 300 307 317 400 SEEN-BY: 229/426 428 452 470 664 700 705 240/1120 5832 261/1 20 263/1 SEEN-BY: 266/75 325 512 618 625 630 267/152 154 280/464 1043 5003 5006 SEEN-BY: 280/5555 291/111 292/854 8125 301/1 310/31 320/119 219 319 SEEN-BY: 320/2119 322/757 762 325/304 341/66 234 342/19 200 396/45 423/81 SEEN-BY: 423/120 460/58 633/280 712/848 770/1 902/26 5020/400 5075/35 @PATH: 266/625 512 229/426 320/219 221/1 280/464

Bye, Wilfred.

--- FMail-lnx64 2.3.4.1-B20260520
* Origin: FMail development HQ (2:280/464)

On 6/6/2026 1:18 PM, Scott Street wrote to All:

@PID: SeaNet BBS v0.02-dev-31-g48346e3(release)
@MSGID: 1:266/625 6a24566667e12160
@TZUTC: +0000
@CHRS: UTF-8 4
@TID: hpt/lnx 1.9 2024-03-02
Yeap, fresh new Linux BBS written in C. First time post to real Echomail area.

System time is UTC, and character encoding is UTF-8. (well at least it supposed to be)
---
* Origin: -={ The Digital Post }=- (1:266/625.0)

looks great here!!!

--- Platinum Xpress/Win/WINServer v10.0b40
* Origin: Over the Brink : Grand Island, NY - brinkbbs.org (1:261/20)

On 6/6/2026 6:13 PM, Wilfred van Velzen wrote to Scott Street:

@TID: FMail-lnx64 2.3.4.1-B20260520
@RFC-X-No-Archive: Yes
@TZUTC: 0200
@CHRS: CP850 2
@PID: GED+LNX 1.1.5-b20240604
@MSGID: 2:280/464 6a249bb5
@REPLY: 1:266/625 6a24566667e12160
Hi Scott,

On 2026-06-06 17:18:30, you wrote to All:

@MSGID: 1:266/625 6a24566667e12160
@PID: SeaNet BBS v0.02-dev-31-g48346e3(release)
@TZUTC: +0000

That is probably not right...

Picky, picky. At least it's a decent start.
--- Platinum Xpress/Win/WINServer v10.0b40
* Origin: Over the Brink : Grand Island, NY - brinkbbs.org (1:261/20)

Hi Scott.

06 Jun 26 17:18:30, Scott Street wrote to All:

@MSGID: 1:266/625 6a24566667e12160
@PID: SeaNet BBS v0.02-dev-31-g48346e3(release)
@TZUTC: +0000

^
You should remove that "+".

@CHRS: UTF-8 4
@TID: hpt/lnx 1.9 2024-03-02
Yeap, fresh new Linux BBS written in C. First time post to real Echomail area.

System time is UTC, and character encoding is UTF-8. (well at least it supposed to be)
---
* Origin: -={ The Digital Post }=- (1:266/625.0)

'Tommi

--- FMail-W64 2.3.4.1-B20260521
* Origin: FPoint One (2:221/1.1)

06 Jun 2026 17:18, you wrote to All:

@MSGID: 1:266/625 6a24566667e12160

^^^^^^^^^^^^^^^^

The serialno field must be 8 chars long according to FTS-0009.

Yeap, fresh new Linux BBS written in C. First time post to real Echomail area.

+1

System time is UTC, and character encoding is UTF-8. (well at least it supposed to be)

The CHRS kludge is ok. If you wish, you can try posting some unicode chars so that we can check this...

Carlos

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

Hello Scott,

06 Jun 26 17:18, you wrote to All:

@PID: SeaNet BBS v0.02-dev-31-g48346e3(release)
@MSGID: 1:266/625 6a24566667e12160
@TZUTC: +0000
@CHRS: UTF-8 4
@TID: hpt/lnx 1.9 2024-03-02
Yeap, fresh new Linux BBS written in C. First time post to real Echomail area.

System time is UTC, and character encoding is UTF-8. (well at least it supposed to be)
---
* Origin: -={ The Digital Post }=- (1:266/625.0)
SEEN-BY: 1/19 100 16/0 19/36 37 30/0 105/81 106/201 123/130 124/5009 128/187
SEEN-BY: 129/12 14 102 125 160 165 134/101 142/104 799 153/7715
154/110 201/0
SEEN-BY: 203/0 218/700 221/0 1 6 226/30 227/114 229/110 112 200 206
300 307
SEEN-BY: 229/317 400 426 428 452 470 664 700 705 240/502 1120 1634
5832 8002
SEEN-BY: 240/8005 8010 8050 261/1 20 266/75 325 512 618 625 630
267/152 154
SEEN-BY: 280/464 5003 5555 291/111 292/854 301/1 313/41 320/119 219
319 2119
SEEN-BY: 322/757 762 325/304 335/364 342/19 200 371/0 52 382/200
396/45
SEEN-BY: 423/81 460/58 492/0 530/204 550/278 633/280 712/848 902/26 5075/35
@PATH: 266/625 512 229/426 320/219 221/1 240/1120 371/0

ByEbYe
--
Daniel

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

... Uptime: 9d 11h 40m 55s
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY (2:371/52)

@MSGID: 1:266/625 6a24566667e12160

^^^^^^^^^^^^^^^^

The serialno field must be 8 chars long according to FTS-0009.

Thanks Carlos, I overlooked this detail in that spec. I've read it so many times, I can't believe I missed that sentence in the middle of all the double-quote babble. <grins>

I'll have to give MSGID generation some thought. UNIX time would be easy and just ignore the 1 second duration that a "duplicate" MSGID might be generated; I'm not ok with that. Especially given a RasPi could easily support several hundred concurrent users.

Which makes me ask the next question, why is it constrained? and why 32bit? Does anyone know? it is just legacy?

If it was 64bit (16 hex characters) I could use UNIX nanotime and generate the serial number within the message base lock cycle. It would be impossible to generate dups that way. Or use the method I have coded already that uses 32b UNIX time and CRC32 of the message text.

Sorry, letting the programmer in me ramble on... bad idea.

---
* Origin: <=-[ The Digital Post ]-=> (1:266/625)