.
. _____ _ _ _ ___ _ ___ _ _____ ___ ___ _____
|_ _| | |_| | (_) / ) (_) / ) /_\ |_ _| | | / ) |_ _|
| | | _ | | | \__ \ | | \__ \ / \ | | | _| \__ \ | |
|_| |_| |_| |_| (___/ |_| (___/ \_|_/ |_| |___| (___/ |_|
. :::::_____:::_:::_:::_:::___:::::_:::___::::::_:::::_____:::___:::___:::_____
::::|_:::_|:|:|_|:|:(_):/:):::(_):/:)::::/_\:::|_:::_|:|:|:/:):|_:::_| ::::::|:|:::|::_::|:|:|:\__:\:::|:|:\__:\:::/:::\::::|:|:::|:_|::\__:\:::|:|
::::::|_|:::|_|:|_|:|_|:(___/:::|_|:(___/:::\_|_/::::|_|:::|___|:(___/:::|_|
.
.
@MSGID: 2:460/256 000006d4
@PID: tg_BBS_v0.7.1
@TZUTC: 0300
@CHRS: CP866 2
@TGUID: 534732808
@REPLYTO 2:460/256 534732808
@RealName: Stas Mishchenkov 2:460/58
Hi, All!
.
. _____ _ _ _ ___ _ ___ _ _____ ___ ___ _____
|_ _| | |_| | (_) / /) (_) // ) /_\ |_ _| | /| // ) |_
_|
| | | _ | | | \__ \ | | \__ \ / \ | | | _| \__ \
| |
|_| |_| |_| |_| (___/ |_| (___/ \_|_/ |_| |___| (___/
|_| . :::::_____:::_:::_:::_:::___:::::_:::___::::::_:::::_____:::___:::___: ::_____ ::::|_:::_|:|:|_|:|:(_):/:/):::(_):/:/)::::/_\:::|_:::_|:|:/|:/:/):|_: ::_| ::::::|:|:::|::_::|:|:|:\__:\:::|:|:\__:\:::/:::\::::|:|:::|:_|::\__:\ :::|:| ::::::|_|:::|_|:|_|:|_|:(___/:::|_|:(___/:::\_|_/::::|_|:::|___|:(___/ :::|_| . .
Have a nice carrot!
Brother Rabbit.
... A good companion not only listens attentively, but pours the drink
on time
--- Use "%UserProfile %Tearline text" to customize tearline.
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)
SEEN-BY: 153/757 154/10 218/840 221/1 6 360 280/464 5555 301/1 335/364 341/66
SEEN-BY: 460/58 256 777 1124 5858 4500/1 4600/140 5020/1042 5054/30
@PATH: 460/256 58 221/6
That's what I see here.. wrapped a bit in this reply.
That's what I see here.. wrapped a bit in this reply.
Why did your reply wrap and not mine from Telegram? Both used
the BR> prefix and there were no additional chars after that.
Why did your reply wrap and not mine from Telegram? Both used
the BR> prefix and there were no additional chars after that.
Different editors behave differently. Your reply did wrap also but not
the same as mine.
Hi, All!
.
. _____ _ _ _ ___ _ ___ _ _____ ___ ___ _____
|_ _| | |_| | (_) / /) (_) // ) /_\ |_ _| | /| // ) |_ _|
| | | _ | | | \__ \ | | \__ \ / \ | | | _| \__ \ | |
|_| |_| |_| |_| (___/ |_| (___/ \_|_/ |_| |___| (___/ |_| . :::::_____:::_:::_:::_:::___:::::_:::___::::::_:::::_____:::___:::___:::_____ ::::|_:::_|:|:|_|:|:(_):/:/):::(_):/:/)::::/_\:::|_:::_|:|:/|:/:/):|_:::_| ::::::|:|:::|::_::|:|:|:\__:\:::|:|:\__:\:::/:::\::::|:|:::|:_|::\__:\:::|:| ::::::|_|:::|_|:|_|:|_|:(___/:::|_|:(___/:::\_|_/::::|_|:::|___|:(___/:::|_| .
.
Different editors behave differently. Your reply did wrap also
but not the same as mine.
See https://susepaste.org/47138907
The top image is how my reply looked when it arrived to my
OpenXp.
The bottom image is your reply to the same message as it
arrived on my system.
Have a nice carrot! :)
Hi Finglonger,
On 2025-04-12 23:51:40, you wrote to :
The To: and Subject: fields were empty.
@MSGID: 1:153/153 7FB50F52
@PID: ZeusBBS 1.5 0
There is no TZUTC kludged.
The TZUTC is nice to have, but not mandatory.^^^^^^^^^^^^^^^^^
I'm not sure, but Zeus probably can't produce a TZUTC kludge. We should check in an AmigaNet area, where the experts are. ;-)
Here is what his message date looked like here, which agrees with August's: Date: Mon, 14 Apr 2025 09:33:53 +0000
The TZUTC is nice to have, but not mandatory.
^^^^^^^^^^^^^^^^^
Then why make it a point to tell people they don't have it?
EDA: 20250412235100W+0
A TZUTC was detected with OpenXP. That's the "EDA" above.
EDA: 20250412235100W+0
A TZUTC was detected with OpenXP. That's the "EDA" above.
I don't know how this works in OpenXP, but there wasn't a TZUTC kludge
in the original message.
Is the "+0" maybe specifying UTC time, which could be identical to the absence of a TZUTC kludge?
So what are we saying here? Am I not sending a field that I should be sending?
The only thing I can think of that I can change would be the packet
header type I'm using...? I would have to go to an older type 2, but
I'm using the 0039 (matching my hub).
I'm not sure what else I can change... I wonder if I have a setting disabled in my zmp.cfg file for the Zeus mailer...
The TZUTC is nice to have, but not mandatory.^^^^^^^^^^^^^^^^^
Then why make it a point to tell people they don't have it?
I'm not sure, but Zeus probably can't produce a TZUTC kludge. We should
check in an AmigaNet area, where the experts are. ;-)
So what if he can't?
Maybe his system is using UTC
and internet RFC capable clients like OpenXP, as well as my client are correct?
Here is what his message date looked like here, which agrees with August's:
Date: Mon, 14 Apr 2025 09:33:53 +0000
.. and here's the date of your message that I'm replying to:
Date: Mon, 14 Apr 2025 19:30:22 +0200
I didn't need a TZUTC kludge for either of those..
Date: Mon, 14 Apr 2025 19:30:22 +0200
I didn't need a TZUTC kludge for either of those..
The +0200 comes from the TZUTC kludge! Without the kludge you can't
know if the message date is my local time, or UTC.
Sysop: | altere |
---|---|
Location: | Houston, TX |
Users: | 69 |
Nodes: | 4 (0 / 4) |
Uptime: | 07:19:55 |
Calls: | 1,062 |
Calls today: | 2 |
Files: | 8,069 |
Messages: | 298,918 |