Subj : dosxnt
To   : Paul Williams
From : Jasen Betts
Date : Wed Sep 25 2002 07:36 am

Hi Paul.

22-Sep-02 23:32:39, Paul Williams wrote to Rob Swindell


 PW> Hi Rob Swindell, hope you are having a nice day

 PW> >>>MSGID numbers should be generated at the originatingsystem
 >>> Right. Unfortunately there's several programs that don't have
 >>> msgid
 PW> >>generation in them. Synchronet BBS being one still under
 PW> development >>that still doesn't. RS>SBBSecho v2.00 beta added
 PW> support for MSGID and REPLY kludge lines.

 PW> Might explain why I haven't seen it. There are some others in R19
 PW> using v2 but I guess not a new enough beta.

 PW> RS>@TZUTC: -800 RS>@MSGID: <123.80XXX@1:103/705> 3D8D2EA4
 PW> RS>@REPLY: 1:387/710 cf29e0b9 RS>@PID: SBBSecho v2.00-Win32 r1.63
 PW> Sep 18 2002 BCC 5.60

 PW> I went back and looked at the fts-0009 abt msgid's to make sure
 PW> and at least when compared to msgid's I see from other programs it
 PW> looks like the one from your beta needs a tweak.

 PW> The msgid I see above has extra stuff in the field that should
 PW> only have the originating address and not the echotag and...
 PW> whatever the 123. is for. It should look just like the reply
 PW> kludge.

that's not really a big problem, some systems put internet addresses in
their msgid... FTS-0009 isn't real clear on the matter.

 PW> Not real sure how termail will deal w/ using that for its reply
 PW> line but I do know that it breaks the nodelist lookup ability.

yeah? HMM termail (which will still have the same bugs next year as it did
last century) should be using the origin line to get a fidonet address,

 PW> Normally when I hit the lookup it will put the correct net segment
 PW> on the screen, but instead of getting the 103 segment it thinks
 PW> your posting from 1:387/123.80 and so gives me the local netseg
 PW> instead.

 -=> Bye <=-

---
 * Origin: Cleanliness is next to impossible. (3:640/531.42)

.