Hi DM,ããI was looking at the header information provided for some of my FidoNetãmessages, via JavaScript, and it seems there are some pieces of informationãthat are not provided - For example, seen-by, via path, CHRS (character set?),ãand codepage. I've heard from other sysops that GoldEd+ shows that informationãfor the messages.. Would Synchronet be able to provide those fields in theãmessage headers in JavaScript?ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã

I was looking at the header information provided for some of my FidoNetã Ni> messages, via JavaScript, and it seems there are some pieces ofã Ni> information that are not provided - For example, seen-by, via path, CHRSã Ni> (character set?), and codepage. I've heard from other sysops that GoldEd+ã Ni> shows that information for the messages.. Would Synchronet be able toã Ni> provide those fields in the message headers in JavaScript?ããFor the record, as is your message reader, Golded's kludge lines areãtoggleable. Where Slyedit you're able to press "K" or "H" or whatever, Goldedãis ALT-V. The only difference is that Golded displays them right in the messageãas they were when the message arrived (and removes them with another ALT-V),ãrather than Slyedit displaying a separate page of only the kludges.ããRegards,ãNickãã---ã þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)ã

Re: Network messsage information missingã By: Accession to Nightfox on Sat Oct 17 2015 16:52:11ãã Ni>> I was looking at the header information provided for some of myã Ni>> FidoNet messages, via JavaScript, and it seems there are some piecesã Ni>> of information that are not provided - For example, seen-by, viaã Ni>> path, CHRS (character set?), and codepage. I've heard from otherã Ni>> sysops that GoldEd+ shows that information for the messages.. Wouldã Ni>> Synchronet be able to provide those fields in the message headers inã Ni>> JavaScript? ãã Ac> For the record, as is your message reader, Golded's kludge lines areã Ac> toggleable. Where Slyedit you're able to press "K" or "H" or whatever,ã Ac> Golded is ALT-V. The only difference is that Golded displays them right inã Ac> the message as they were when the message arrived (and removes them withã Ac> another ALT-V), rather than Slyedit displaying a separate page of only theã Ac> kludges. ããSlyEdit does not display kludge lines - That's my message reader that doesãthat.ãI was curious about this because there seem to be a few kludge line informationãfields that Synchronet doesn't seem to make available in JavaScript (but seemãto be accessible by GoldEd+).ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã

Re: Network messsage information missingã By: Nightfox to Digital Man on Sat Oct 17 2015 09:08 amãã > Hi DM,ã >ã > I was looking at the header information provided for some of my FidoNetã > messages, via JavaScript, and it seems there are some pieces of informationã > that are not provided - For example, seen-by, via path, CHRS (characterã > set?), and codepage. I've heard from other sysops that GoldEd+ shows thatã > information for the messages.. Would Synchronet be able to provide thoseã > fields in the message headers in JavaScript?ããIf the tosser is configured to not strip kludge lines, then they should be inãthe message headers already. You can use the (O)perator, (H)eaders command withãthe internal message reading interface or smbutil to view the header fields.ãMost of them a not really intended for display to users/readers.ãã digital manããSynchronet "Real Fact" #81:ãFlapuebarg unf vagreany ebg13 fhccbeg sbe fhcresvpvnyyl rapelcgvat grkg.ãNorco, CA WX: 67.7øF, 89.0% humidity, 5 mph SSE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

SlyEdit does not display kludge lines - That's my message reader that doesã Ni> that.ããLOL. I think you've witnessed that is not the first time I've mixed up the twoãnames. :)ããUsing the two together (DDMR and Slyedit) is basically like using oneãall-in-one package like Golded (but within the BBS). Probably why I keepãcalling one the other and vise versa.ãã Ni> I was curious about this because there seem to be a few kludge lineã Ni> information fields that Synchronet doesn't seem to make available inã Ni> JavaScript (but seem to be accessible by GoldEd+).ããDefinitely. Glad to see you ask about them. The more you can include to beãviewable, the more information can be seen about a message. I can't argue withãthat one bit. :)ããRegards,ãNickãã---ã þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)ã

If the tosser is configured to not strip kludge lines, then they should beã DM> in the message headers already. You can use the (O)perator, (H)eadersã DM> command with the internal message reading interface or smbutil to view theã DM> header fields. Most of them a not really intended for display toã DM> users/readers. ããWhile that's definitely an option. I think Nightfox is looking for a way to beãable to incorporate viewing them in his message reader. There's already anãoption while reading to hit a key and view the header information and kludgesã(for some that actually like to debug things). At the moment I don't think he'sãable to pull things like TZUTC, SEEN-BY, PATH, and possibly a few others.ããRegards,ãNickãã---ã þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)ã

Re: Network messsage information missingã By: Digital Man to Nightfox on Sun Oct 18 2015 00:03:18ãã DM> If the tosser is configured to not strip kludge lines, then they should beã DM> in the message headers already.ããI had a look at the headers for one of my FidoNet messages, and although it hadãsome kludge line information such as the message ID, PID, etc., it didn't haveãseen-by, via, characters, or codepage (which I've heard GoldEd+ will display).ãã DM> You can use the (O)perator, (H)eadersã DM> command with the internal message reading interface or smbutil to view theã DM> header fields. Most of them a not really intended for display toã DM> users/readers. ããI understand - But it seems that a sysop might be interested in seeing suchãinformation. My reader only allows the sysop to view that information, similarãto Synchronet's built-in reader.ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã

Re: Network messsage information missingã By: Digital Man to Nightfox on Sun Oct 18 2015 00:03:18ãã DM> If the tosser is configured to not strip kludge lines, then they should beã DM> in the message headers already. You can use the (O)perator, (H)eadersã DM> command with the internal message reading interface or smbutil to view theã DM> header fields. Most of them a not really intended for display toã DM> users/readers. ããAlso, if that information is viewable from the internal reader, I think itãwould be useful if all the same information was available in JavaScript.ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã

Re: Network messsage information missingã By: Accession to Nightfox on Sun Oct 18 2015 09:35:30ãã Ni>> SlyEdit does not display kludge lines - That's my message readerã Ni>> that does that.ãã Ac> LOL. I think you've witnessed that is not the first time I've mixed up theã Ac> two names. :)ãã Ac> Using the two together (DDMR and Slyedit) is basically like using oneã Ac> all-in-one package like Golded (but within the BBS). Probably why I keepã Ac> calling one the other and vise versa.ãã:) I can understand that.ãI think GoldEd+ looks nice, but I was disappointed when I found that it doesn'tãseem to handle Synchronet's message group prefixes (and thus, it got confusedãwith a lot of my message areas). I suppose there might be a way around thatãthough - I suppose I'd just have to look/ask around.ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã

Re: Network messsage information missingã By: Accession to Digital Man on Sun Oct 18 2015 09:38:29ãã DM>> If the tosser is configured to not strip kludge lines, then theyã DM>> should be in the message headers already. You can use theã DM>> (O)perator, (H)eaders command with the internal message readingã DM>> interface or smbutil to view the header fields. Most of them a notã DM>> really intended for display to users/readers. ãã Ac> While that's definitely an option. I think Nightfox is looking for a wayã Ac> to be able to incorporate viewing them in his message reader. There'sã Ac> already an option while reading to hit a key and view the headerã Ac> information and kludges (for some that actually like to debug things). Atã Ac> the moment I don't think he's able to pull things like TZUTC, SEEN-BY,ã Ac> PATH, and possibly a few others. ããYep, that's what I was getting at.ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã

Re: Network messsage information missingã By: Nightfox to Digital Man on Sun Oct 18 2015 08:40:49ãã DM>> If the tosser is configured to not strip kludge lines, then theyã DM>> should be in the message headers already. You can use theã DM>> (O)perator, (H)eaders command with the internal message readingã DM>> interface or smbutil to view the header fields. Most of them a notã DM>> really intended for display to users/readers. ãã Ni> Also, if that information is viewable from the internal reader, I think itã Ni> would be useful if all the same information was available in JavaScript.ããI think I had some options set up in echocfg that may have been removing someãof the kludge lines, which might be why I wasn't seeing all of them. I hadã"Store PATH Lines in Message Base", "Store SEEN-BY Lines in Message Base", andã"Store Unknown Kludge LInes in Message Base" set to "No", and I had "Zone BlindãSEEN-BY and PATH Lines" set to Disabled. I'll enable those options and see ifãI will start getting more kludge lines in my message headers.ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã

Re: Network messsage information missingã By: Accession to Digital Man on Sun Oct 18 2015 09:38 amãã > DM> If the tosser is configured to not strip kludge lines, then they shouldã > DM> be in the message headers already. You can use the (O)perator,ã > DM> (H)eaders command with the internal message reading interface orã > DM> smbutil to view the header fields. Most of them a not really intendedã > DM> for display to users/readers.ã >ã > While that's definitely an option. I think Nightfox is looking for a way toã > be able to incorporate viewing them in his message reader. There's alreadyã > an option while reading to hit a key and view the header information andã > kludges (for some that actually like to debug things). At the moment I don'tã > think he's able to pull things like TZUTC, SEEN-BY, PATH, and possibly a fewã > others.ããThat might just be because the tosser is configured to strip them?ãã digital manããSynchronet "Real Fact" #16:ã"Vertrauen" (ver-trow-en) translates to "trust" in German, and was a band name.ãNorco, CA WX: 64.3øF, 91.0% humidity, 5 mph SE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Network messsage information missingã By: Nightfox to Digital Man on Sun Oct 18 2015 08:32 amãã > Re: Network messsage information missingã > By: Digital Man to Nightfox on Sun Oct 18 2015 00:03:18ã >ã > DM> If the tosser is configured to not strip kludge lines, then they shouldã > DM> be in the message headers already.ã >ã > I had a look at the headers for one of my FidoNet messages, and although itã > had some kludge line information such as the message ID, PID, etc., itã > didn't have seen-by, via, characters, or codepage (which I've heard GoldEd+ã > will display).ããLooked at the headers how? The only kludge lines that SBBSecho willã(optionally) strip are the PATH and SEEN-BYs. If the others aren't in the SMBãheaders, then they most likely just weren't in the originally imported FTNãmessage. Not every message has every possible kludge in it.ãã > DM> You can use the (O)perator, (H)eadersã > DM> command with the internal message reading interface or smbutil to viewã > DM> the header fields. Most of them a not really intended for display toã > DM> users/readers.ã >ã > I understand - But it seems that a sysop might be interested in seeing suchã > information. My reader only allows the sysop to view that information,ã > similar to Synchronet's built-in reader.ããI agree. That's why I have that option in the BBS. :-)ãã digital manããSynchronet "Real Fact" #80:ãVertrauen has had the FidoNet node number 1:103/705 since 1992.ãNorco, CA WX: 64.3øF, 91.0% humidity, 5 mph SE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Network messsage information missingã By: Nightfox to Digital Man on Sun Oct 18 2015 08:40 amãã > Re: Network messsage information missingã > By: Digital Man to Nightfox on Sun Oct 18 2015 00:03:18ã >ã > DM> If the tosser is configured to not strip kludge lines, then they shouldã > DM> be in the message headers already. You can use the (O)perator,ã > DM> (H)eaders command with the internal message reading interface orã > DM> smbutil to view the header fields. Most of them a not really intendedã > DM> for display to users/readers.ã >ã > Also, if that information is viewable from the internal reader, I think itã > would be useful if all the same information was available in JavaScript.ããAll the same information should be. Do have some reason to think its not?ãã digital manããSynchronet "Real Fact" #61:ãName of Synchronet PCMS compiler/language "Baja" was coined by Michael Swindell.ãNorco, CA WX: 64.3øF, 91.0% humidity, 5 mph SE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Network messsage information missingã By: Nightfox to Digital Man on Sun Oct 18 2015 03:57 pmãã > Re: Network messsage information missingã > By: Nightfox to Digital Man on Sun Oct 18 2015 08:40:49ã >ã > DM>> If the tosser is configured to not strip kludge lines, then theyã > DM>> should be in the message headers already. You can use theã > DM>> (O)perator, (H)eaders command with the internal message readingã > DM>> interface or smbutil to view the header fields. Most of them a notã > DM>> really intended for display to users/readers.ã >ã > Ni> Also, if that information is viewable from the internal reader, I thinkã > Ni> it would be useful if all the same information was available inã > Ni> JavaScript.ã >ã > I think I had some options set up in echocfg that may have been removingã > some of the kludge lines, which might be why I wasn't seeing all of them. Iã > had "Store PATH Lines in Message Base", "Store SEEN-BY Lines in Messageã > Base", and "Store Unknown Kludge LInes in Message Base" set to "No", and Iã > had "Zone Blind SEEN-BY and PATH Lines" set to Disabled. I'll enable thoseã > options and see if I will start getting more kludge lines in my messageã > headers.ããYes, I think you found the cause, though the "Zone Blind" option is notãrelated.ãã digital manããSynchronet "Real Fact" #38:ãSynchronet first supported Windows NT v6.x (a.k.a. Vista/Win7) w/v3.14a (2006).ãNorco, CA WX: 64.0øF, 91.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Network messsage information missingã By: Digital Man to Nightfox on Sun Oct 18 2015 23:49:58ãã >> I had a look at the headers for one of my FidoNet messages, andã >> although it had some kludge line information such as the message ID,ã >> PID, etc., it didn't have seen-by, via, characters, or codepage (whichã >> I've heard GoldEd+ will display).ãã DM> Looked at the headers how? The only kludge lines that SBBSecho willã DM> (optionally) strip are the PATH and SEEN-BYs. If the others aren't in theã DM> SMB headers, then they most likely just weren't in the originally importedã DM> FTN message. Not every message has every possible kludge in it.ããI had a look at the headers in JavaScript. For instance, if I have a messageãheader object called msgHdr, I did this:ãfor (var property in msgHdr)ã console.print(property + ": " + msgHdr[property] + "\r\n");ãconsole.pause();ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã

Re: Network messsage information missingã By: Nightfox to Digital Man on Mon Oct 19 2015 07:31 amãã > Re: Network messsage information missingã > By: Digital Man to Nightfox on Sun Oct 18 2015 23:49:58ã >ã > >> I had a look at the headers for one of my FidoNet messages, andã > >> although it had some kludge line information such as the message ID,ã > >> PID, etc., it didn't have seen-by, via, characters, or codepage (whichã > >> I've heard GoldEd+ will display).ã >ã > DM> Looked at the headers how? The only kludge lines that SBBSecho willã > DM> (optionally) strip are the PATH and SEEN-BYs. If the others aren't inã > DM> the SMB headers, then they most likely just weren't in the originallyã > DM> imported FTN message. Not every message has every possible kludge inã > DM> it.ã >ã > I had a look at the headers in JavaScript. For instance, if I have aã > message header object called msgHdr, I did this:ã > for (var property in msgHdr)ã > console.print(property + ": " + msgHdr[property] + "\r\n");ã > console.pause();ããI thought we resolved the reason you weren't seeing the header fields you wereãlooking for (they were being stripped by SBBSecho per your configurationãsettings). Is this still an open question?ãã digital manããSynchronet "Real Fact" #66:ãSEXYZ is as a 32-bit replacement for [F]DSZ, CE-XYZ and other protocol drivers.ãNorco, CA WX: 71.7øF, 58.0% humidity, 4 mph ESE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

I think GoldEd+ looks nice, but I was disappointed when I found that itã Ni> doesn't seem to handle Synchronet's message group prefixes (and thus, itã Ni> got confused with a lot of my message areas). I suppose there might be aã Ni> way around that though - I suppose I'd just have to look/ask around.ããIt does handle SMB, it's just not documented. I think you have to point theãconfiguration to the msgs.cnf file or something in those lines. That and if youãpack/renumber your message bases, Golded loses track of the last read pointersãand considers every message in the area as new again.ããIn other words, you'd have to tinker with Synchronet a bit to make it workãperfectly. You also can't actually use it from the BBS, so there's that too.ããRegards,ãNickãã---ã þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)ã

Re: Network messsage information missingã By: Accession to Nightfox on Mon Oct 19 2015 04:45 pmãã Ni>> I think GoldEd+ looks nice, but I was disappointed when I found thatã Ni>> it doesn't seem to handle Synchronet's message group prefixes (andã Ni>> thus, it got confused with a lot of my message areas). I supposeã Ni>> there might be a way around that though - I suppose I'd just have toã Ni>> look/ask around. ãã Ac> It does handle SMB, it's just not documented. I think you have to pointã Ac> the configuration to the msgs.cnf file or something in those lines. Thatã Ac> and if you pack/renumber your message bases, Golded loses track of theã Ac> last read pointers and considers every message in the area as new again.ãã Ac> In other words, you'd have to tinker with Synchronet a bit to make it workã Ac> perfectly. You also can't actually use it from the BBS, so there's thatã Ac> too. ããIt "Works", to some point. It fails with the msgs.cnf method almost completely,ãbut if you configure it manually, it works a bit better. I got my GoldEd+ãwokring with netmail and the email message bases, as I don't want to manuallyãconfigure it for everything.. That and it trashes permissions somehow. ããSo, definitely can't recommend letting it try to do the automated method of theãmsgs.cnf, as that screws a lot of things up. :)ãã)))[Psi-Jack -//- Decker]ãã... To eat is human; to digest divine.ãã---ã þ Synchronet þ Decker's Heaven -//- bbs.deckersheaven.comã

Re: Network messsage information missingã By: Digital Man to Nightfox on Mon Oct 19 2015 16:15:04ãã DM> I thought we resolved the reason you weren't seeing the header fields youã DM> were looking for (they were being stripped by SBBSecho per yourã DM> configuration settings). Is this still an open question?ããWell, it seems that when I iterate through the header fields in JavaScript, I'mãnot seeing all the same information that Synchronet's built-in reader showsãwhen I have it display the header information. But I suppose I'll have toãinvestigate more to be sure.ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã

Re: Network messsage information missingã By: Accession to Nightfox on Mon Oct 19 2015 16:45:14ãã Ni>> I think GoldEd+ looks nice, but I was disappointed when I found thatã Ni>> it doesn't seem to handle Synchronet's message group prefixes (andã Ni>> thus, it got confused with a lot of my message areas). I supposeã Ni>> there might be a way around that though - I suppose I'd just have toã Ni>> look/ask around. ãã Ac> It does handle SMB, it's just not documented. I think you have to pointã Ac> the configuration to the msgs.cnf file or something in those lines. Thatã Ac> and if you pack/renumber your message bases, Golded loses track of theã Ac> last read pointers and considers every message in the area as new again.ãã Ac> In other words, you'd have to tinker with Synchronet a bit to make it workã Ac> perfectly. You also can't actually use it from the BBS, so there's thatã Ac> too. ããYeah, I did all that, and I did get it to work with Synchronet, to an extent.. ãI found that I had to remove the internal code prefixes in SCFG order to getãGoldEd+ to understand my message bases. For instance, in SCFG, I haveãSynchronet set up to prefix my Dove-Net internal codes with "DOVE_", so theã"General" area, which normally has an internal code of DOVE-GEN, becomesãDOVE_DOVE-GEN. GoldEd+ didn't deal with that very well - GoldEd+ would seeãthat the "General" area should have an internal code of "DOVE-GEN", and itãwasn't reading it correctly because it's actually "DOVE_DOVE-GEN" on my system.ããWhen I posted about this last time (several months ago), I remember someoneãsaying Synchronet added the internal code prefixes after GoldEd+ implementedãits Synchronet support, so it sounded like GoldEd+ simply has limitedãSynchronet support. I'm not sure if there's a good way around the issueãwithout GoldEd+ being updated.ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã

So, definitely can't recommend letting it try to do the automated methodã Ps> of the msgs.cnf, as that screws a lot of things up. :)ããOddly enough, the last time I tried it I had much more successful results,ãbesides the fact that I packed/renumbered my message areas with Synchronet,ãonly to find 5000 new messages in just about every message base. *shrug*ããEither way, I have had it working just fine using that method.. so I don't knowãwhat happened in your case that screwed a lot of things up.ããRegards,ãNickãã---ã þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)ã

Yeah, I did all that, and I did get it to work with Synchronet, to anã Ni> extent.. I found that I had to remove the internal code prefixes in SCFGã Ni> order to get GoldEd+ to understand my message bases. For instance, inã Ni> SCFG, I have Synchronet set up to prefix my Dove-Net internal codes withã Ni> "DOVE_", so the "General" area, which normally has an internal code ofã Ni> DOVE-GEN, becomes DOVE_DOVE-GEN. GoldEd+ didn't deal with that very well -ã Ni> GoldEd+ would see that the "General" area should have an internal code ofã Ni> "DOVE-GEN", and it wasn't reading it correctly because it's actuallyã Ni> "DOVE_DOVE-GEN" on my system. ããAh yes. I remember that one too, now. Then again, how and/or why would Golded+ãunderstand something that Synchronet does internally (prefixes are onlyãsomething for Synchronet itself. When messages in those echos get exported toãother systems, the prefix is dropped off of them, I believe).ããEither that, or the whole prefix things gets broken when msgs.cnf is read,ãwhich also wouldn't be a Golded+ problem, would it?ãã Ni> When I posted about this last time (several months ago), I rememberã Ni> someone saying Synchronet added the internal code prefixes after GoldEd+ã Ni> implemented its Synchronet support, so it sounded like GoldEd+ simply hasã Ni> limited Synchronet support. I'm not sure if there's a good way around theã Ni> issue without GoldEd+ being updated.ããOr it's possible msgs.cnf isn't giving that information to Golded+?ããI'm not sure if we ever got an answer on any of that (or if we actually askedãsomeone that would know). If we did, I don't remember. :)ããRegards,ãNickãã---ã þ Synchronet þ thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)ã

Re: Network messsage information missingã By: Accession to Nightfox on Tue Oct 20 2015 17:13:24ãã Ni>> instance, in SCFG, I have Synchronet set up to prefix my Dove-Netã Ni>> internal codes with "DOVE_", so the "General" area, which normallyã Ni>> has an internal code of DOVE-GEN, becomes DOVE_DOVE-GEN. GoldEd+ã Ni>> didn't deal with that very well - GoldEd+ would see that theã Ni>> "General" area should have an internal code of "DOVE-GEN", and itã Ni>> wasn't reading it correctly because it's actually "DOVE_DOVE-GEN" onã Ni>> my system. ãã Ac> Ah yes. I remember that one too, now. Then again, how and/or why wouldã Ac> Golded+ understand something that Synchronet does internally (prefixes areã Ac> only something for Synchronet itself. When messages in those echos getã Ac> exported to other systems, the prefix is dropped off of them, I believe).ãã Ac> Either that, or the whole prefix things gets broken when msgs.cnf is read,ã Ac> which also wouldn't be a Golded+ problem, would it?ããWell, it has to do with the filenames. The filenames used for the messagebaseãfiles in Synchronet correspond directly to the internal codes, so using myãabove example, the Dove-Net General area on my BBS is stored in filenames suchãas DOVE_DOVE-GEN.xyz (where "xyz" is the filename extension - There are a fewãfiles for each message area). So, GoldEd+ would have to know about thoseãfilenames. Since GoldEd+ wasn't recognizing the group prefixes, GoldEd was notãreading from the correct filenames. Thus, GoldEd+ was not showing any messagesãfor any of my configured message areas. GoldEd+ would somehow have to know howãSynchronet names its messagebase files, so I'd think this is somewhat of aãGoldEd+ issue (lacking complete support for Synchronet message bases). If notãa GoldEd+ issue, I'm not sure where else the issue would be. Synchronet itselfãhandles its own messagebase files just fine, and I'm not sure if it would beãSynchronet's responsibility to cater to GoldEd+.ãã Ni>> When I posted about this last time (several months ago), I rememberã Ni>> someone saying Synchronet added the internal code prefixes afterã Ni>> GoldEd+ implemented its Synchronet support, so it sounded likeã Ni>> GoldEd+ simply has limited Synchronet support. I'm not sure ifã Ni>> there's a good way around the issue without GoldEd+ being updated.ãã Ac> Or it's possible msgs.cnf isn't giving that information to Golded+?ãã Ac> I'm not sure if we ever got an answer on any of that (or if we actuallyã Ac> asked someone that would know). If we did, I don't remember. :)ããYeah, I'm not sure if we did. I don't know enough about GoldEd+ to knowãwhether msgs.cnf is able to specify enough information about Synchronet'sãmessagebase files to GoldEd+.ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã

Re: Network messsage information missingã By: Nightfox to Digital Man on Tue Oct 20 2015 07:52 amãã > Re: Network messsage information missingã > By: Digital Man to Nightfox on Mon Oct 19 2015 16:15:04ã >ã > DM> I thought we resolved the reason you weren't seeing the header fieldsã > DM> you were looking for (they were being stripped by SBBSecho per yourã > DM> configuration settings). Is this still an open question?ã >ã > Well, it seems that when I iterate through the header fields in JavaScript,ã > I'm not seeing all the same information that Synchronet's built-in readerã > shows when I have it display the header information. But I suppose I'llã > have to investigate more to be sure.ããAll of the header fields should be available via JS. If you have an example ofãthe discrepencies, please share. It's always possible that there is a bugãsomewhere, but we've had other JS-methods of displaying the header fieldsã(event the old runemaster/WebUI has that ability) and scripts which convertãthem (e.g. to NNTP equivalents) and I've never noticed a problem with it. Ifãyou do continue to see a problem, please let me know. Thanks,ãã digital manããSynchronet "Real Fact" #68:ãYou can purchase the BBS Documentary DVD set at http://bbsdocumentary.com/order/ãNorco, CA WX: 61.9øF, 85.0% humidity, 2 mph NW wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Network messsage information missingã By: Accession to Psi-Jack on Tue Oct 20 2015 05:07 pmãã Ps>> So, definitely can't recommend letting it try to do the automatedã Ps>> method of the msgs.cnf, as that screws a lot of things up. :)ãã Ac> Oddly enough, the last time I tried it I had much more successful results,ã Ac> besides the fact that I packed/renumbered my message areas withã Ac> Synchronet, only to find 5000 new messages in just about every messageã Ac> base. *shrug* ãã Ac> Either way, I have had it working just fine using that method.. so I don'tã Ac> know what happened in your case that screwed a lot of things up.ããHeh yeah, I don't fully remember now, I just remember the outcome that I neverãwant to see again. So, now I happily use DDMsgReader and SlyEdit for Synchronetãwhich makes life that much better for me overall.ããI have GoldEd+ setup on my new dedicated binkd hub, but I only really useãgolded for the netmail and double-checking certain things I'm doing, likeãautomated posts for stats and such. ãã)))[Psi-Jack -//- Decker]ãã... Take what you can use and let the rest go by.ãã---ã þ Synchronet þ Decker's Heaven -//- bbs.deckersheaven.comã

I had a look at the headers in JavaScript. For instance, if I have a message header object called msgHdr, I did this:
for (var property in msgHdr)
console.print(property + ": " + msgHdr[property] + "\r\n");

You might try 'console.print(JSON.stringify(msgHdr));' to get a bit more depth. The header has a 'field_list' property which (the docs suggest anyway) is an array of objects each with '.type' and '.data' properties. Iterating over top-level properties would miss this (or just show [Object object] or somesuch as the value for this property.)

Of course, I don't know what you'll find in that array, but it might be a place where any unaccounted-for header fields get stuffed into.

---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230ãã---ã þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comã

---ã> echicken ããJust curious, is there something wrong with the editor you are using? Itãseems your starting line is any number of spaces in for each paragraph, justãcurious if that is intentional?ãã-- ãMichael J. Ryanãtracker1(at)gmail.comã+o Roughneck BBSãã---ã þ Synchronet þ RoughneckBBS - http://www.roughneckbbs.com/ã

Re: weird message formattingã By: tracker1 to echicken on Thu Oct 22 2015 08:05:50ãã tr> Just curious, is there something wrong with the editor you are using? ItããProbably.ãã---ãechickenãelectronic chicken bbs - bbs.electronicchicken.com - 416-273-7230ã þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comã

---ã > > echicken ãã > Just curious, is there something wrong with the editor you are using? Itã > seems your starting line is any number of spaces in for each paragraph, ãjustã > curious if that is intentional?ããI've also noticed odd formatting issues with your messages while using theãolder (Runemaster?) web interface - It's like your text is right-justified.ãHowever it looks okay when reading in the telnet terminal.ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã

Re: weird message formattingã By: Nightfox to echicken on Thu Oct 22 2015 09:35:37ãã Ni> I've also noticed odd formatting issues with your messages while using theã Ni> older (Runemaster?) web interface - It's like your text isã Ni> right-justified. However it looks okay when reading in the telnetã Ni> terminal. ããWell, that's descriptive at least (thanks.) Just took a look on Vert, and itãlooks like LFs without CRs, so that gives me something to look into.ãã(I have no idea what tracker1 was trying to describe, but no matter - I'llãavoid posting the same way until I feel like sorting it out.)ãã---ãechickenãelectronic chicken bbs - bbs.electronicchicken.com - 416-273-7230ã þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.comã

Re: Network messsage information missingã By: echicken to Nightfox on Wed Oct 21 2015 13:36:27ãã >> I had a look at the headers in JavaScript. For instance, if I have aã >> message header object called msgHdr, I did this: for (var property inã >> msgHdr) console.print(property + ": " + msgHdr[property] + "\r\n");ãã ec> You might try 'console.print(JSON.stringify(msgHdr));' to get a bit moreã ec> depth. The header has a 'field_list' property which (the docs suggestã ec> anyway) is an array of objects each with '.type' and '.data' properties.ã ec> Iterating over top-level properties would miss this (or just show [Objectã ec> object] or somesuch as the value for this property.) ãã ec> Of course, I don't know what you'll find in that array, but it might be aã ec> place where any unaccounted-for header fields get stuffed into. ããThanks for the tip.ãI had discovered field_list, and I had updated my script to iterate through itãwhen it encountered field_list. JSON.stringify works too.ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã

Re: Network messsage information missingã By: Digital Man to Nightfox on Wed Oct 21 2015 02:02:19ãã >> Well, it seems that when I iterate through the header fields inã >> JavaScript, I'm not seeing all the same information that Synchronet'sã >> built-in reader shows when I have it display the header information. ã >> But I suppose I'll have to investigate more to be sure.ãã DM> All of the header fields should be available via JS. If you have anã DM> example of the discrepencies, please share. It's always possible thatã DM> there is a bug somewhere, but we've had other JS-methods of displaying theã DM> header fields (event the old runemaster/WebUI has that ability) andã DM> scripts which convert them (e.g. to NNTP equivalents) and I've neverã DM> noticed a problem with it. If you do continue to see a problem, please letã DM> me know. Thanks, ããI've looked into it a bit more, and I think I understand it a bit better. Itãlooks like the field_list array in the header is meant to contain otherãarbitrary message header data. It looks like the 'type' property of eachãobject in field_list is a number, and the .data property is the information forãthat field. Is there any documentation that lists the field types in theãfield_list and the numbers that they correspond to? It looks like 162 is FTNãseen-by and 163 is FTN path, but I've also seen 176 for some messages, and I'mãnot sure what that represents, or what other types might exist.ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã

Re: Network messsage information missingã By: Nightfox to Digital Man on Sat Oct 24 2015 05:49 pmãã > Subject: Network messsage information missingã > @MSGID: <562C2726.2022.dove_sync_js@digitaldistortionbbs.com>ã > @REPLY: <5627549B.2032.sync-js@vert.synchro.net>ã > @TZ: c1e0ã > Re: Network messsage information missingã > By: Digital Man to Nightfox on Wed Oct 21 2015 02:02:19ã >ã > >> Well, it seems that when I iterate through the header fields inã > >> JavaScript, I'm not seeing all the same information that Synchronet'sã > >> built-in reader shows when I have it display the header information.ã > >> But I suppose I'll have to investigate more to be sure.ã >ã > DM> All of the header fields should be available via JS. If you have anã > DM> example of the discrepencies, please share. It's always possible thatã > DM> there is a bug somewhere, but we've had other JS-methods of displayingã > DM> the header fields (event the old runemaster/WebUI has that ability) andã > DM> scripts which convert them (e.g. to NNTP equivalents) and I've neverã > DM> noticed a problem with it. If you do continue to see a problem, pleaseã > DM> let me know. Thanks,ã >ã > I've looked into it a bit more, and I think I understand it a bit better.ã > It looks like the field_list array in the header is meant to contain otherã > arbitrary message header data. It looks like the 'type' property of eachã > object in field_list is a number, and the .data property is the informationã > for that field. Is there any documentation that lists the field types inã > the field_list and the numbers that they correspond to?ããYes, here: http://synchro.net/docs/smb.html#Header Field Types:ããBut note that the values are given in hexadecimal.ãã > It looks like 162ã > is FTN seen-by and 163 is FTN path, but I've also seen 176 for someã > messages, and I'm not sure what that represents, or what other types mightã > exist.ããYes, load/822header.js and load/newsutil.js contain a couple of references toãspecific header field types that aren't other-wise represented as JS propertiesãof the message header.ãã digital manããSynchronet "Real Fact" #60:ãHow to get Synchronet technical support: http://wiki.synchro.net/howto:supportãNorco, CA WX: 77.7øF, 29.0% humidity, 1 mph SE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Network messsage information missingã By: Digital Man to Nightfox on Sat Oct 24 2015 20:42:10ãã >> better. It looks like the field_list array in the header is meant toã >> contain other arbitrary message header data. It looks like the 'type'ã >> property of each object in field_list is a number, and the .dataã >> property is the information for that field. Is there anyã >> documentation that lists the field types in the field_list and theã >> numbers that they correspond to? ãã DM> Yes, here: http://synchro.net/docs/smb.html#Header Field Types:ãã DM> But note that the values are given in hexadecimal.ããThanks.ããNightfoxãã---ã þ Synchronet þ Digital Distortion: digitaldistortionbbs.comã