• Network messsage information missing

    From Nightfox@VERT/DIGDIST to Digital Man on Saturday, October 17, 2015 09:08:40
    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
  • From Accession@VERT/PHARCYDE to Nightfox on Saturday, October 17, 2015 16:52:11
    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?

    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)
  • From Nightfox@VERT/DIGDIST to Accession on Saturday, October 17, 2015 23:12:42
    Re: Network messsage information missing
    By: Accession to Nightfox on Sat Oct 17 2015 16:52:11

    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?

    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.

    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
  • From Digital Man@VERT to Nightfox on Sunday, October 18, 2015 00:03:18
    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.7F, 89.0% humidity, 5 mph SSE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Accession@VERT/PHARCYDE to Nightfox on Sunday, October 18, 2015 09:35:30
    SlyEdit does not display kludge lines - That's my message reader that does 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.

    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+).

    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)
  • From Accession@VERT/PHARCYDE to Digital Man on Sunday, October 18, 2015 09:38:29
    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.

    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)
  • From Nightfox@VERT/DIGDIST to Digital Man on Sunday, October 18, 2015 08:32:38
    Re: Network messsage information missing
    By: Digital Man to Nightfox on Sun Oct 18 2015 00:03:18

    If the tosser is configured to not strip kludge lines, then they should 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).

    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.

    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
  • From Nightfox@VERT/DIGDIST to Digital Man on Sunday, October 18, 2015 08:40:49
    Re: Network messsage information missing
    By: Digital Man to Nightfox on Sun Oct 18 2015 00:03:18

    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.

    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
  • From Nightfox@VERT/DIGDIST to Accession on Sunday, October 18, 2015 08:44:47
    Re: Network messsage information missing
    By: Accession to Nightfox on Sun Oct 18 2015 09:35:30

    SlyEdit does not display kludge lines - That's my message reader
    that does 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.

    :) 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
  • From Nightfox@VERT/DIGDIST to Accession on Sunday, October 18, 2015 08:51:31
    Re: Network messsage information missing
    By: Accession to Digital Man on Sun Oct 18 2015 09:38:29

    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.

    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.

    Yep, that's what I was getting at.

    Nightfox

    ---
    Synchronet Digital Distortion: digitaldistortionbbs.com
  • From Nightfox@VERT/DIGDIST to Digital Man on Sunday, October 18, 2015 15:57:53
    Re: Network messsage information missing
    By: Nightfox to Digital Man on Sun Oct 18 2015 08:40:49

    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.

    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.

    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
  • From Digital Man@VERT to Accession on Sunday, October 18, 2015 23:48:13
    Re: Network messsage information missing
    By: Accession to Digital Man on Sun Oct 18 2015 09:38 am

    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.

    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.3F, 91.0% humidity, 5 mph SE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Nightfox on Sunday, October 18, 2015 23:49:58
    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

    If the tosser is configured to not strip kludge lines, then they should 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.

    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.

    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.3F, 91.0% humidity, 5 mph SE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Nightfox on Sunday, October 18, 2015 23:56:47
    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

    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.

    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.3F, 91.0% humidity, 5 mph SE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Nightfox on Monday, October 19, 2015 01:00:53
    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

    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.

    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.

    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.0F, 91.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Nightfox@VERT/DIGDIST to Digital Man on Monday, October 19, 2015 07:31:18
    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).

    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.

    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
  • From Digital Man@VERT to Nightfox on Monday, October 19, 2015 16:15:04
    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).

    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.

    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.7F, 58.0% humidity, 4 mph ESE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Accession@VERT/PHARCYDE to Nightfox on Monday, October 19, 2015 16:45:14
    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.

    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)
  • From Psi-Jack@VERT/DECKHEVN to Accession on Monday, October 19, 2015 23:27:33
    Re: Network messsage information missing
    By: Accession to Nightfox on Mon Oct 19 2015 04:45 pm

    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.

    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.

    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
  • From Nightfox@VERT/DIGDIST to Digital Man on Tuesday, October 20, 2015 07:52:32
    Re: Network messsage information missing
    By: Digital Man to Nightfox on Mon Oct 19 2015 16:15:04

    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?

    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
  • From Nightfox@VERT/DIGDIST to Accession on Tuesday, October 20, 2015 07:59:16
    Re: Network messsage information missing
    By: Accession to Nightfox on Mon Oct 19 2015 16:45:14

    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.

    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.

    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
  • From Accession@VERT/PHARCYDE to Psi-Jack on Tuesday, October 20, 2015 17:07:40
    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. :)

    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)
  • From Accession@VERT/PHARCYDE to Nightfox on Tuesday, October 20, 2015 17:13:24
    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.

    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?

    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.

    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)
  • From Nightfox@VERT/DIGDIST to Accession on Tuesday, October 20, 2015 17:11:10
    Re: Network messsage information missing
    By: Accession to Nightfox on Tue Oct 20 2015 17:13:24

    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.

    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?

    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+.

    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.

    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. :)

    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
  • From Digital Man@VERT to Nightfox on Wednesday, October 21, 2015 02:02:19
    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

    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?

    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.9F, 85.0% humidity, 2 mph NW wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Psi-Jack@VERT/DECKHEVN to Accession on Wednesday, October 21, 2015 10:36:35
    Re: Network messsage information missing
    By: Accession to Psi-Jack on Tue Oct 20 2015 05:07 pm

    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. :)

    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.

    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
  • From echicken@VERT/ECBBS to Nightfox on Wednesday, October 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");

    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
  • From tracker1@VERT/TRNTEST to echicken on Thursday, October 22, 2015 08:05:50
    ---
    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/
  • From echicken@VERT/ECBBS to tracker1 on Thursday, October 22, 2015 11:50:51
    Re: weird message formatting
    By: tracker1 to echicken on Thu Oct 22 2015 08:05:50

    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
  • From Nightfox@VERT/DIGDIST to echicken on Thursday, October 22, 2015 09:35:37
    ---
    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
  • From echicken@VERT/ECBBS to Nightfox on Thursday, October 22, 2015 13:51:15
    Re: weird message formatting
    By: Nightfox to echicken on Thu Oct 22 2015 09:35:37

    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.

    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
  • From Nightfox@VERT/DIGDIST to echicken on Saturday, October 24, 2015 17:18:52
    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");

    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.

    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
  • From Nightfox@VERT/DIGDIST to Digital Man on Saturday, October 24, 2015 17:49:42
    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.

    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,

    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
  • From Digital Man@VERT to Nightfox on Saturday, October 24, 2015 20:42:10
    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.

    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,

    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.7F, 29.0% humidity, 1 mph SE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Nightfox@VERT/DIGDIST to Digital Man on Sunday, October 25, 2015 16:39:36
    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?

    Yes, here: http://synchro.net/docs/smb.html#Header Field Types:

    But note that the values are given in hexadecimal.

    Thanks.

    Nightfox

    ---
    Synchronet Digital Distortion: digitaldistortionbbs.com