Subj : oxp: utc kludge, and X_C: line
To   : August Abolins
From : Martin Foster
Date : Sat Dec 07 2019 09:25:00

Hello August!

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

 AA>>>> Is the TZUTC coming from the OSes setting?

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

 MF>> He says that it gets it from the OS.

 AA> Thanks for getting back on that.

You're welcome.

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

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

 AA> Is is supposed to appear in the EDA: line?

Nope.

 AA> Is the "W+0" supposed to represent "+0000" for your utc time
 AA> 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 :)

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

:-)

 AA> The equivalent does not appear using other readers when checking
 AA> 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)

.