Hello August!

### Replying to a message in "FIDOTEST" ###

Why would anyone need to turn TZUTC off and on?

..it's the way the developer decided to implement it, thus giving the
user the option to enable/disable it.

Is the TZUTC coming from the OSes setting?

That's something I've been wondering about so I'll ask the developer.

He says that it gets it from the OS.

Regards,
Martin

--- OpenXP 5.0.41
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

** 05.12.19 - 09:18, Martin Foster wrote to August Abolins:

Is the TZUTC coming from the OSes setting?

[snip] ..I'll ask the developer.

He says that it gets it from the OS.

Thanks for getting back on that.

BTW.. the TZUTC does not seem to appear in my .40 version:

EMP: /FIDO/POINTS
ABS: Martin Foster@2:310/31.3
BET: Without TZUTC kludge
ROT: 2:221/1!310/31 280/464 221/1
MID: 2:310/31.3@fidonet df2262c2
EDA: 20191205091800W+0
LEN: 510
BEZ: 2:310/31.3@fidonet df125f91
MAILER: OpenXP/5.0.41 (Linux) (x86_64) / OpenXP 5.0.41
X_C:
X-XP-NTP: 30
F-TO: August Abolins
X-XP-Charset: US-ASCII

Is is supposed to appear in the EDA: line? Is the "W+0" supposed to represent "+0000" for your utc time offset?

And, the X_C: intrigues me. Is this where OXP users can pass secret messages? <G> The equivalent does not appear using other readers when checking your original message. :)




../|ug

--- OpenXP 5.0.40
* Origin: o,,,,o��`��o,,,,o��`��o,,,,o (2:221/1.58)

Hello August!

* 05.12.19 at 08:26, August Abolins wrote to Martin Foster:

Is the TZUTC coming from the OSes setting?

[snip] ..I'll ask the developer.

He says that it gets it from the OS.

Thanks for getting back on that.

You're welcome.

BTW.. the TZUTC does not seem to appear in my .40 version:

It doesn't appear in my .41 development version either because the implementation of the TZUTC kludge is mainly for the benefit of other
Fido software. It's complicated and I don't fully understand how it
works yet.

EMP: /FIDO/POINTS
ABS: Martin Foster@2:310/31.3
BET: Without TZUTC kludge
ROT: 2:221/1!310/31 280/464 221/1
MID: 2:310/31.3@fidonet df2262c2
EDA: 20191205091800W+0
LEN: 510
BEZ: 2:310/31.3@fidonet df125f91
MAILER: OpenXP/5.0.41 (Linux) (x86_64) / OpenXP 5.0.41
X_C:
X-XP-NTP: 30
F-TO: August Abolins
X-XP-Charset: US-ASCII

Is is supposed to appear in the EDA: line?

Nope.

Is the "W+0" supposed to represent "+0000" for your utc time
offset?

Yes, that's how it's always worked but during our testing of the TZUTC kludge, we discovered that the time offset at the end of the EDA
kludge wasn't working correctly. We're working on that now :)

And, the X_C: intrigues me. Is this where OXP users can pass secret messages? <G>

:-)

The equivalent does not appear using other readers when checking
your original message. :)

I'll pass your comment on to the developer and see if he can shed some
light on this ;)

Regards,
Martin

--- OpenXP 5.0.41
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello August!

* 07.12.19 at 09:25, Martin Foster wrote to August Abolins:

[snip]

And, the X_C: intrigues me. Is this where OXP users can pass secret
messages? <G>

:-)

The equivalent does not appear using other readers when checking
your original message. :)

I'll pass your comment on to the developer and see if he can shed some light on this ;)

Here's what he said .....

---------- 8< ----------
According to source code the X_C kludge is a kludge with no content,
but it's always written into outgoing mails.

I suppose it was once intended for Crosspoint/OpenXP internal use, but
then forgotten.
---------- 8< ----------

Regards,
Martin

--- OpenXP 5.0.41
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)