Testing my fsxNet integration, hoping this reaches FSX_TST
---

On 10 Mar 2023, jcs said the following...

Testing my fsxNet integration, hoping this reaches FSX_TST
---

Got you here!

ogg
Sysop, Altair IV BBS, Lufkin, Texas USA
altairiv.ddns.net:2323

... 640K ought to be enough for anybody. -Bill Gates, 1981.

--- Mystic BBS v1.12 A49 2023/02/27 (Windows/64)
* Origin: Altair IV BBS (21:2/147)

Hello jcs!

On 10 Mar 2023, jcs said the following...

Testing my fsxNet integration, hoping this reaches FSX_TST
---

Got you here! Although I couldn't see any Origin: line.

Best regards
Zip

--- Mystic BBS v1.12 A49 2023/02/26 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Thanks Zip. This one should have an Origin line now.

I can't seem to find any spec that says whether the sending software
is supposed to prefix a reply subject with 'Re:' or whether the viewing software is.

---
* Origin: Kludge BBS | klud.ge (21:3/177)

On 10 Mar 2023, jcs said the following...

@INTL 21:3/100 21:3/177

I don't usually see the INTL kludge on echomail messages.


INTL, TOPT: Netmail routing control lines defined in FTS-0001. These
control lines should not appear in echomail as they impart "false"
information after the first "stop" due to the nature of echomail.

http://ftsc.org/docs/fsc-0068.001


Jay

... No one knows what's next, but everybody does it.

--- Mystic BBS v1.12 A49 2023/02/26 (Linux/64)
* Origin: Northern Realms (21:3/110)

On 10 Mar 2023, jcs said the following...

@MSGID: 21:3/177 f0004

^^^^^

The MSGID serial number is also generally 8 hexadecimal characters.


The serial number may be any eight character hexadecimal number, as long as it is unique - no two messages from a given system may have the same serial number within a three years. The manner in which this serial number is
generated is left to the implementor.

http://ftsc.org/docs/fts-0009.001


Jay

... Condense soup, not books!

--- Mystic BBS v1.12 A49 2023/02/26 (Linux/64)
* Origin: Northern Realms (21:3/110)

Hello jcs!

Thank you for your reply!

On 10 Mar 2023, jcs said the following...

Thanks Zip. This one should have an Origin line now.

Yep! Looks good:

* Origin: Kludge BBS | klud.ge (21:3/177)

I can't seem to find any spec that says whether the sending software
is supposed to prefix a reply subject with 'Re:' or whether the viewing software is.

I haven't seen any such spec either, but I believe the sending software is supposed to, if it wants to. I think the REPLY kludge (referring to a MSGID that the reply is a reply to) gives the real/formal information, e.g. for threaded viewing of conversations (depending on whether the reading/viewing software chooses to do anything with that information if present).

Best regards
Zip

--- Mystic BBS v1.12 A49 2023/02/26 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

On 10 Mar 2023, jcs said the following...

I can't seem to find any spec that says whether the sending software
is supposed to prefix a reply subject with 'Re:' or whether the viewing software is.

I wish instead of a RE: it would keep the original Subject and Have a flag somewhere instead. This way the initial fully intended Subject would remain intact throughout the conversation.

I know no one is developing it so can't happen.

|23|04Dr|16|12Claw
|16|14Sysop |12Noverdu |14BBS |20|15Radio|10@|14HTTP://Noverdu.com:88
|16|10 Standard ports for SSH/Telnet |04 WEB|14@|12HTTP://noverdu.com:808 |20|15Global Chat, Global Messaging and Games! |16|10Ditch the Unsocial Media

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Noverdu BBS (21:1/210)