I may have posted this in the Facebook group, but could not
recall if I posted it here.
In messages I've posted, it shows the date and time of the
message, with the correct local time, but it notes "UTC",
which is WRONG.
In messages I've posted, it shows the date and time of the
message, with the correct local time, but it notes "UTC",
which is WRONG.
Set your local time zone in SCFG->System. Messages posted after that change will have that time zone recorded in the message header.
Rob,
In messages I've posted, it shows the date and time of the
message, with the correct local time, but it notes "UTC",
which is WRONG.
Set your local time zone in SCFG->System. Messages posted after that change will have that time zone recorded in the message header.
I did that yesterday, and it didn't seem to take. I'll look at this
with the replies I upload.
This message, along with the previous message you posted (that I quoted above) both have a time zone in the message header as "CDT":
Re: Re: Message Base Glitch
By: Digital Man to Daryl Stout on
Wed Sep 23 2020 09:34 pm
Rob,
This message, along with the previous message you posted (that I quoted above) both have a time zone in the message header as "CDT":
Well, it's showing up here as UTC...and I'm not logging in from the host console.
Well, it's showing up here as UTC...and I'm not logging in from the host console.
Can you provide more details? There are *many* ways in Synchronet to
view a message header. I can't guess which way you are using.
Rob,
Well, it's showing up here as UTC...and I'm not logging in from the host console.
Can you provide more details? There are *many* ways in Synchronet to view a message header. I can't guess which way you are using.
Well, the time shows up correctly...but instead of CDT, it shows UTC instead. Everything else is correct.
Re: Re: Message Base Glitch
By: Daryl Stout to Digital Man on Thu Sep 24 2020 05:44 pm
Rob,
Well, it's showing up here as UTC...and I'm not logging in from the host console.
Can you provide more details? There are *many* ways in Synchronet to view a message header. I can't guess which way you are using.
Well, the time shows up correctly...but instead of CDT, it shows UTC instead. Everything else is correct.
There are many ways in Synchronet to view a message header. I'm assuming you're referring to the terminal server which you are using via Telnet, SSH, or RLogin. Are you using a custom or 3rd party message reader module? Or a custom message header? Are you using msglist.js or the old scrolling message scan? I can't guess the answers to these questions.
There are many ways in Synchronet to view a message header. I'm assuming you're referring to the terminal server which you are using via Telnet, SSH, or RLogin. Are you using a custom or 3rd party message reader module? Or a custom message header? Are you using msglist.js or the old scrolling message scan? I can't guess the answers to these questions.
Trying to get the bottom of your report, I logged onto your BBS as
Guest and here's what I noticed:
1. You don't have msglist.js installed (which is fine, it's just
another tool that possibly could help to identify the cause of your problem).
2. *All* the messages in your Local group, most of which were posted before SBBS v3.18 was a thing, were displayed as having been written in UTC.
3. When I downloaded a QWK packet with a HEADERS.DAT file, *all* of
those same messages are shown to have a time zone of "c168" (which is
CDT, UTC-5). So the message bases are fine, the messages were posted correctly.
So again, I ask, are you using a custom message header?
Well, the time shows up correctly...but instead of CDT, it shows UTC instead. Everything else is correct.
There are many ways in Synchronet to view a message header. I'm
assuming you're referring to the terminal server which you are using
via Telnet, SSH, or RLogin. Are you using a custom or 3rd party message reader module? Or a custom message header? Are you using msglist.js or
the old scrolling message scan? I can't guess the answers to these questions.
Rob,
There are many ways in Synchronet to view a message header. I'm assuming you're referring to the terminal server which you are using via Telnet, SSH, or RLogin. Are you using a custom or 3rd party message reader module? Or a custom message header? Are you using msglist.js or the old scrolling message scan? I can't guess the answers to these questions.
Trying to get the bottom of your report, I logged onto your BBS as Guest and here's what I noticed:
1. You don't have msglist.js installed (which is fine, it's just another tool that possibly could help to identify the cause of your problem).
I wasn't even aware of such, but I guess I could install it.
2. *All* the messages in your Local group, most of which were posted before SBBS v3.18 was a thing, were displayed as having been written in UTC.
I tried that, and still no dice.
I did a login with echicken's web
interface (logon via telnet from the website), and the same thing. I had
an external FTelnet link, but it's not connecting at all now...so, I've
got to figure out what the issue is there.
3. When I downloaded a QWK packet with a HEADERS.DAT file, *all* of those same messages are shown to have a time zone of "c168" (which is CDT, UTC-5). So the message bases are fine, the messages were posted correctly.
I saw that, and that you had changed the password for the Guest User,
so I changed it back. In that regard, is there an exemption or restriction for Synchronet to exempt certain users from a password change?? As of now, I'd prefer that to apply only to the Guest account.
So again, I ask, are you using a custom message header?
I was just reading the messages online, with the Synchronet Command
shell, using the SlyEdit message editor, when posting/reading messages.
I saw that, and that you had changed the password for the Guest User,
so I changed it back. In that regard, is there an exemption or restriction for Synchronet to exempt certain users from a password change?? As of now, I'd prefer that to apply only to the Guest account.
Rob,
Well, the time shows up correctly...but instead of CDT, it shows UTC instead. Everything else is correct.
There are many ways in Synchronet to view a message header. I'm assuming you're referring to the terminal server which you are using via Telnet, SSH, or RLogin. Are you using a custom or 3rd party message reader module? Or a custom message header? Are you using msglist.js or the old scrolling message scan? I can't guess the answers to these questions.
That showed up whether I used MTel, SyncTerm,
or went through echicken's web interface...
That I guess it's a deal on the LAN.
I haven't checked it via
an external FTelnet link that I set up off of my own homepage, which I did before echicken's web interface was incorporated into Synchronet.
I would've loved to have run the system on UTC, since I'm an amateur
radio operator, and an amateur weather enthusiast. But, when I tried
it last time, it screwed up my netmail and echomail royally.
Rob,
>
> Well, it's showing up here as UTC...and I'm not logging in from the host
> console.
DM> Can you provide more details? There are *many* ways in Synchronet to
DM> view a message header. I can't guess which way you are using.
Well, the time shows up correctly...but instead of CDT, it shows UTC instead.
Everything else is correct.
2. *All* the messages in your Local group, most of which were posted before SBBS v3.18 was a thing, were displayed as having been written in UTC.
I tried that, and still no dice.
You tried *what*, exactly?
No, but I changed the code so in future versions users with no password won't be forced to change it on your password-change schedule.
Yeah, that's not the question. So... do you have a text/menu/msghdr.* file? Or have you made any changes to your ctrl/text.dat file?
So the Guest password is normally blank. And that's what it was before your system forced me to change to something non-blank. You've you "changed it back" to something else (not blank and not the password I changed it to) - so can't login as Guest now.
Which terminal program you used, doesn't seem relevant to the problem.
I would've loved to have run the system on UTC, since I'm an amateur
radio operator, and an amateur weather enthusiast. But, when I tried
it last time, it screwed up my netmail and echomail royally.
So I logged in to your BBS in 40 column mode and viewed a message
header, and voila: "cdt" was displayed. So it appears you have a custom message header that has hard-coded (for 80 column users) with the
string "UTC" in it.
Rob,
2. *All* the messages in your Local group, most of which were posted before SBBS v3.18 was a thing, were displayed as having been written in UTC.
I tried that, and still no dice.
You tried *what*, exactly?
Posting a message locally...they still show up from the BBS computer, over the LAN via SyncTerm, or coming in via the website telnet interface from echicken. Each message shows the correct local time, but show UTC at this end instead of CDT. I went into SCFG -> System -> Time Zone -- setting it
at US Central Time, and Automatic for Daylight Savings Time.
No, but I changed the code so in future versions users with no password won't be forced to change it on your password-change schedule.
OK, I got that, and it works. I had to delete and reinstall the Guest account for it to work. When I logged on, I was asked if I wanted to enable the Guest account, and I said "yes".
Yeah, that's not the question. So... do you have a text/menu/msghdr.* file? Or have you made any changes to your ctrl/text.dat file?
No on both counts.
Rob,
Which terminal program you used, doesn't seem relevant to the problem.
I wasn't sure if it did or not. The display with MTel or SyncTerm still showed it as that (it still showed UTC instead of GMT).
I would've loved to have run the system on UTC, since I'm an amateur radio operator, and an amateur weather enthusiast. But, when I tried
it last time, it screwed up my netmail and echomail royally.
So I logged in to your BBS in 40 column mode and viewed a message header, and voila: "cdt" was displayed. So it appears you have a custom message header that has hard-coded (for 80 column users) with the string "UTC" in it.
I haven't made any changes in the text.dat file.
I wasn't sure if it did or not. The display with MTel or SyncTerm still showed it as that (it still showed UTC instead of GMT).
I haven't made any changes in the text.dat file.
You can also change the message headers via text/menu/msghdr.* files.
Here's your message that I'm replying to's nntp header.
Date: Thu, 24 Sep 2020 17:44:00 -0500
-0500 should be central right now.
Definitely not UTC, where are you viewing this, telnet, web, nntp?
end instead of CDT. I went into SCFG -> System -> Time Zone -- setting it
at US Central Time, and Automatic for Daylight Savings Time.
I don't think it's a setting issue.
I suspect you have a text/menu/msghdr.* file. As I said earlier, when I logged into your BBS in 40-column mode, the messages' time zones were displayed correctly. This would be because a different message header display file is used in 40-column mode (by default, msghdr.40col.asc).
So take a look at your text/menu directory and I'm guessing that'll refresh your memory at some change you made there.
You can also change the message headers via text/menu/msghdr.* files.
Michael,
Here's your message that I'm replying to's nntp header.
Date: Thu, 24 Sep 2020 17:44:00 -0500
-0500 should be central right now.
Definitely not UTC, where are you viewing this, telnet, web, nntp?
Telnet via SyncTerm...or web via echicken's web interface. If I have
a NNTP deal, I'm not aware of it, let alone how to use it.
I guess I'll have to take a screenshot, and post it to the Facebook
group.
Rob,
end instead of CDT. I went into SCFG -> System -> Time Zone -- setting it at US Central Time, and Automatic for Daylight Savings Time.
I don't think it's a setting issue.
I'll have to get a screenshot, and post it via Facebook. For the editor, I'm using SlyEdit...but prefer to do my messages via QWK Mail.
I suspect you have a text/menu/msghdr.* file. As I said earlier, when I logged into your BBS in 40-column mode, the messages' time zones were displayed correctly. This would be because a different message header display file is used in 40-column mode (by default, msghdr.40col.asc). So take a look at your text/menu directory and I'm guessing that'll refresh your memory at some change you made there.
It's on the other computer, but I can look at it via TeamViewer.
Rob,
You can also change the message headers via text/menu/msghdr.* files.
OK, I'll check that. I wonder if a utility I had installed awhile back (that I obviously don't remember now) changed things.
I guess I'll have to take a screenshot, and post it to the Facebook
group.
That's not necessary. I logged into your BBS and saw it with my own
eyes.
Rob,
I guess I'll have to take a screenshot, and post it to the Facebook group.
That's not necessary. I logged into your BBS and saw it with my own eyes.
So, what is the verdict, Your Honor??
I guess I'm guilty of being a
worthless Sysop. Maybe it's time I give up my hobbies and disappear.
Re: Re: Message Base Glitch
By: Daryl Stout to Digital Man on Tue Sep 29 2020 07:53 am
Rob,
I guess I'll have to take a screenshot, and post it to the Facebook group.
That's not necessary. I logged into your BBS and saw it with my own eyes.
So, what is the verdict, Your Honor??
Re: Re: Message Base Glitch
By: Daryl Stout to Digital Man on Tue Sep 29 2020 07:53 am
Rob,
I guess I'll have to take a screenshot, and post it to the Facebook group.
That's not necessary. I logged into your BBS and saw it with my own eyes.
So, what is the verdict, Your Honor??
You definitely have a unique problem. I noticed (on your system) that:
- messages posted *east* of UTC, display the time zone correctly (e.g. UTC+1)
- messages posted *west* of UTC, always show as just "UTC"
- unless you login with a 40 column terminal (which uses msghdr.40col.*)
- unless you download a QWK packet (the headers.dat includes the correct TZs) - for all messages, the "age" displayed in the header appears correct
There's no verdict yet.
I guess I'm guilty of being a
worthless Sysop. Maybe it's time I give up my hobbies and disappear.
Doesn't appear so.
You definitely have a unique problem. I noticed (on your system) that:
- messages posted *east* of UTC, display the time zone correctly (e.g. UTC+1) - messages posted *west* of UTC, always show as just "UTC"
- unless you login with a 40 column terminal (which uses
msghdr.40col.*)
- unless you download a QWK packet (the headers.dat includes the
correct TZs) - for all messages, the "age" displayed in the header
appears correct
There's no verdict yet.
I guess I'm guilty of being a
worthless Sysop. Maybe it's time I give up my hobbies and disappear.
Doesn't appear so.
Can you be sure the x86 version of this is installed on the BBS system: https://www.microsoft.com/en-us/download/details.aspx?id=53840
Are you running in a VM?
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 333 |
Nodes: | 10 (0 / 10) |
Uptime: | 222:43:13 |
Calls: | 576 |
Messages: | 236316 |