Subj : P1nG 1:229/426
To   : Nodelist Police Commissioner
From : Tommi Koivula
Date : Fri Apr 09 2021 12:22:10


 OA>>> @Via 1:229/426@fidonet @20210409.011830.LST O/T-Track+ 2.85
 OA>>> @Via D'Bridge 4 2:292/854  04/09 07:21
 OA>>> @Via 2:292/854@Ward_Dossche @20210409.062359.UTC O/T-Track+
 OA>>> 2.85

 TK>> This @domain part is always so funny.

 NC> What's not funny is the line above it.

Yes.

 NC> And you editted out the extra newline that is always present.

I didn't, I think HPT does that.

There were two replies in one .PKT. Please note that the first one has @Via line from Ward, the other does not. :D

=== Cut ===
PktInfo/w32-mvc 1.9.0-cur 2021-04-01

Packet header
==============================================================================
Filename       : S:\Temp\50724091.pkt
OrigAddr       : 2:292/854.0
DestAddr       : 2:221/1.0
AuxNet         : 0
CapWord        : 0x0001
DateCreation   : Fri 2021-04-09 08:24:04
ProdCode       : 001a
ProdVersion    : 4.0

Message header
------------------------------------------------------------------------------
From           : "One Ping To Rule Them All"
To             : "P1nG"
Subject        : "P1nG 1:229/426"
DateTime       : "09 Apr 21  01:18:30"
Attr           : 0x0001 -> Private
OrigAddr       : 229/426
DestAddr       : 221/6

Message text
------------------------------------------------------------------------------
@INTL 2:221/6 1:229/426
@TOPT 166
@MSGID: 1:229/426@fidonet 0ed66cc0
@REPLY: 2:221/6.166 606fe39a
@PID: O/T+ 2.85 ME9292
@CHRS: IBMPC 2
@CODEPAGE: 437
Instead of trying to build newer and bigger weapons of
destruction, mankind should be thinking about getting more
use out of the weapons we already have.

================================================================
From    : P1nG, 2:221/6.166
To      : PING, 1:229/426
Date    : 09 Apr 21  08:18:18
Subject : P1nG 1:229/426
================================================================

Ping Msg to 1:229/426

-
--
-+-
-+- PING BOT
 + Origin: --- (2:221/6.166)


@Via 1:229/426@fidonet @20210409.011830.LST O/T-Track+ 2.85

@Via D'Bridge 4 2:292/854  04/09 07:21
@Via 2:292/854@Ward_Dossche @20210409.062359.UTC O/T-Track+ 2.85

Message header
------------------------------------------------------------------------------
From           : "One Ping To Rule Them All"
To             : "P1nG"
Subject        : "PING"
DateTime       : "09 Apr 21  01:19:17"
Attr           : 0x0001 -> Private
OrigAddr       : 229/426
DestAddr       : 221/6

Message text
------------------------------------------------------------------------------
@INTL 2:221/6 1:229/426
@MSGID: 1:229/426@fidonet 0ed672a0
@REPLY: 2:221/6 606fe3e3
@PID: O/T+ 2.85 ME9292
@CHRS: IBMPC 2
@CODEPAGE: 437
The crows seemed to be calling his name, thought Caw.

================================================================
From    : P1nG, 2:221/6
To      : PING, 1:229/0
Date    : 09 Apr 21  08:19:30
Subject : PING
================================================================

Ping MSG to 1:229/0

-+- CRASH PING BOT
 + Origin: -- (2:221/6)


@Via 1:229/426@fidonet @20210409.011917.LST O/T-Track+ 2.85

@Via D'Bridge 4 2:292/854  04/09 07:24

=== Cut ===

 NC> I've talked about it to Nick years ago. But he's not interested in
 NC> making it more compliant to the standard.

:(

 NC> And it's probably difficult to produce a correct UTC time stamp in a
 NC> DOS program...

O/T-Track can do it. ;)

'Tommi

---
 * Origin: - rbb.fidonet.fi - Finland - (2:221/1)

.