Subj : Re: Newsgroup replies to To : Digital Man From : Tharius Date : Thu Sep 01 2005 02:22 pm "Digital Man" wrote in message news:4316204C.9101.dove-hlp@vert.synchro.net... > > > > > > but they had a point) that my reader was posting replies to ALL > > > > > > > > locals and in dovenet just fine, with the TO field being the > > > > > > person > > > > > > responding to, however, my fidonet echomail is responding to ALL > > > > > > > "O, H" command from the reading message prompt. And your reply > > > > > message > > > > > in OE should have a "in-reply-to" header field which matches the > > > > > original messages "rfc822msgid" field. > The "in-reply-to" header field is part of teh NNTP article format. If you > look > at the details of message in Outlook Express (where it shows the NNTP > headers), > you should see it there. This "in-reply-to" NNTP header field gets > imported > into SMB has an "RFC822ReplyId" SMB header field. Yes, ok I've located it now. I had picked a sample thread where the problem is occouring : ----(1)---------------------- > > Original post : Sync 3.12a > > RFC822MsgID <430F2B83.1.fidobbsdoord@aceshigh.dyn.dhs.org> Posted via telnet, internal editor. -------------------------- Above is my original message, from me, to all, posted via telnet internal to Sync. The main difference between this echo and all my others is that this one has the toggle Fidonet Echomail set to yes. All other settings seem negigably different. -----(2, is reply to 1)--------------------- > > > > RFC822ReplyID <430F2B83.1.fidobbsdoord@aceshigh.dyn.dhs.org> > > Header of what message? How was this message posted? If it was posted via > NNTP, > then the need to check the original article header in OE and make sure it > has a > "message-id" header field. This above is the reply to my original message. It is from Shawn to me, but I have no knowledge how it was posted. This also occours with other softwares in other echos, this thread was just a sample. His software has correctly filled in the to and from, etc. Internally sync does not show a RFC822MsgID but does display the above replyID. The following message ID is as reported in OE after I've downloaded it from the BBS. (still no msgID as displayed by Sync, post download) Message-ID: <4310E279.2.fidobbsdoord@aceshigh.dyn.dhs.org> -------------------------- ----(3, is reply to 2)---------------------- > > My reply to the above message, via OE NNTP (displays as To ALL, no > > inbound > > msg id to match starts new?) > > > > RFC822ReplyID <4310E279.2.fidobbsdoord@aceshigh.dyn.dhs.org> > > > > RFC822MsgID <43111DB3.3.fidobbsdoord@aceshigh.dyn.dhs.org> This is now the RFC ID's as displayed by Synchronet after I've replied to the message (displayed in 2). This message is posted via OE's reply to group command. This message's to field displays as ALL when reviewed in ftn readers and sync. I observe a match between the replyID here and the Message-ID in the previous message, however, as previously noted, the message in (2) did not carry a RFC822MsgID when viewed from Sync's O,H display. (If this is relevant) -------------------------- > I'm not understanding what you're posting here. I hope this is more helpful. I had originally posted 5 messages in the thread, I've trimmed it down to 3 since from here in the pattern repeats. Incoming messages being read by me in OE do carry a Message-Id as observed in OE however do not carry a RFC822MsgID when observed in Sync. My outbounds, posted in OE carry all three id's. The things I'm wondering is : is OE assigning the message-id which then of course Sync has no record of? Or perhaps Sync's nntp is assigning the message-id but not updating the smb? Perhaps we're expecting sbbsecho to be assigning a rfc822msgId and it's not (since this is popping up in Fido echomail conferences)? > I don't know. Can check the aritcles in OE? Sorry if I'm not getting the right information to you DM, I'm learning as you're replying about the formats involved and how Sync works with them. I hope this message paints the picture a bit more clearly. --- þ Synchronet þ [aceshigh.dyn.dhs.org] - Come fly our friendly skies! .