Haha... I hit (Q)uote, it barfed up the MSGID instead of the message
doh! Anyway, this post also serves as a test - did anyone see it? How
about the msgid and reply, they look ok????

Yep, the message I am replying to looks good kludge wise, and I do so it.. :)

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

Haha... I hit (Q)uote, it barfed up the MSGID instead of the message
doh! Anyway, this post also serves as a test - did anyone see it? How
about the msgid and reply, they look ok????

Ozz
--- ExchangeBBS FTN Tosser/JAM v1.19.04 (Beta 4.09)
* Origin: (1:1/123)

MSGID/REPLY are not required /unless/ your software supports FTS-0009... if >your software supports FTS-0009, it is expected to adhere to the protocols >defined within it...

The reason I ask, was a message came in on another FTN type network,
and my tosser processed but reported a message with no MSGID. Of
course, nothing says it has to be there, but, there are a few FTSC
documents which mention how to use it for dupe checking and reply
chaining. Which would break as soon as two different topics come in
with the same blank msgid, and thus blank reply.

Ozz
(Not policing, just trying to make sure I don't allow CRAP in/out!)
--- ExchangeBBS FTN Tosser/JAM v1.19.04 (Beta 4.09)
* Origin: (1:1/123)

For the life of me - I cannot find the FSTC document which states that
MSGID is a required field. Isn't it?

Thanks,
O.

--- ExchangeBBS NNTP Server v3.1/Linux64
* Origin: (1:1/123)

On 2019 Apr 29 10:48:10, you wrote to All:

For the life of me - I cannot find the FSTC document which states that MSGID is a required field. Isn't it?

MSGID/REPLY are not required /unless/ your software supports FTS-0009... if your software supports FTS-0009, it is expected to adhere to the protocols defined within it...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... I'm lost. I left a trail of crumbs, but somebody ate'em.
---
* Origin: (1:3634/12.73)