description of .pkt format

A day has passed, and you are still alive! All! Does anyone have the exact subject? in English or Russian? lather up, plz. ZXNet: 500:8462/1 ~/ <~ http://zx.fatal.ru/ Fido: 2:5057/21.93 /_ _> SkyNet: 71:170/21

Hello Sergey! 12 May 02 22:18, Sergey Zotov -> All: SZ> does anyone have the exact subject? in English or Russian? lather, plz. Look for the FTS-0001 standard. In general it’s like this: - packet header (58 bytes); - packed letters (0 or more); - pseudo-letter (2 bytes 00), serving as a sign of the end of the *.pkt file. Thus, the size of an empty packet is 60 bytes. Each packaged letter in the package is represented by the following structure: - letter header, which begins with the letter type attribute - 2 bytes (02 00); - six fields of fixed length (each 2 bytes); - one line of fixed length 20 bytes, terminated with a zero byte; - three strings of variable length, terminated with 0 (total maximum 144 bytes). This concludes the title; - message text of unlimited length, terminated with a zero byte. All additional control information is considered in terms of package structure as part of the body of the letter. Structure of a letter packaged for sending: name field size comment fields in bytes PktType 2 Packet type, old type 1 deprecated, value fields (02 00) origNode 2 Origin node of the letter destNode 2 Destination node origNet 2 Origin Network destNet 2 AttributeWord 2 Letter attributescost 2 price DateTime 20 Date and time last modified letter toUserName 36 Recipient name fromUserName 36 subject 72 topic text unlimited Structure of a mail packet of type 2.0: Name Field size Type Expected Comments fields in bytes value OrgNode 2 Word 0-65535 Sender node number DstNode 2 Word 0-65535 recipient Year 2 Int 19??-2??? Year of creation of the package Month 2 Int 0-11 Month of creation (0 - January) Day 2 Int 1-31 Hour 2 Int 0-23 Min 2 Int 0-59 Sec 2 Int 0-59 Baud 2 Int - Baud rate (not used) PktVer 2 Int always=2 Package version OrgNet 2 Word 1-65535 Origin network number DstNet 2 Word 1-65535 Destination network number PrdCodl 1 Byte 1-255 FTSC Product Code (first part) SerialNo 1 1-255 Byte Serial number Password 8 Char A-Z,0-9 Package password OrigZone 2 Int 1-65535 Origin zone DestZOne 2 Int 1-65535 Destination zoneFiller 20 - - Reserve Packed Messages - - - Zero or more packed messages Ugh... There are also packages like 2+ and 2.2 (FTS-0039). Nikolaj

Hello Sergey! May 12, 2002 (it was 10:18 pm then) Sergey Zotov in his letter to All wrote: SZ> does anyone have the exact subject? in English or Russian? lather, plz. So let's continue... Structure of mail package type 2+ Name Field size Type Expected Comments fields in bytes value OrgNode 2 Word 0-65535 DstNode 2 Word 0-65535 Year 2 Int 19??-2??? Month 2 Int 0-11 Day 2 Int 1-31 Hour 2 Int 0-23 Min 2 Int 0-59 Sec 2 Int 0-59 Baud 2 Int - PktVer 2 Int Always=2 OrgNet 2 Word 1-65535 DstNet 2 Word 1-65535 PrdCodl 1 Byte 1-255 FTSC Product Code (first part) PVMajor 1 Byte 1-255 Product code FTSC (second part) Password 8 Char A-Z,0-9 Package password QOrgZone 2 Int 1-65535 Origin zone (for ZMailQ,Qmail) QDstZone 2 Int 1-65535 Destination zone (-//-) Filler 2 Byte - Reserve CapValid 2 Word Bit field Compatibility check maskPrdCodH 1 Byte 1-255 FTSC product code (high byte) PVMinor 1 Byte 1-255 Product code FTSC (low byte) CapWord 2 Word Bit field Compatibility mask OrigZone 2 Int 1-65535 Origin zone DestZone 2 Int 1-65535 Destination zone OrigPoint 32 2 Int 1-65535 Point of origin DestPoint 34 2 Int 1-65535 Destination point ProdData 36 4 Long Any Defined by the program PktTerm 2 Word 0 Values ending header package Compatibility mask structure: Supported Compatibility Mask system types FTSC packet types packages High bits Low bits U 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 2+,3, and 7 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 1 2+,3, and 5 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1 2+ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 Stone Age 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 There is also type 2.2. Do you need him? Nikolaj.

Hi! In short, you didn’t tell me anything new. then a specific question. where are they stored? message attributes in .pkt? With .msg everything is clear - there are 2 bytes. after all, a tosser somehow finds out what needs to be sent, for example, a receipt or read confirmation. where is this stated? I'm interested in where the mark is located that says attach is attached to the .pkt file. How can I find out if this is possible at all? ZXNet: 500:8462/1 ~/ <~ http://zx.fatal.ru/ Fido: 2:5057/21.93 /_ _> SkyNet: 71:170/21

A day has passed, and you are still alive! Nikolaj! On 20 May 02, Nikolaj Amosov wrote to Sergey Zotov: NA> So, let's continue... NA> Structure of a mail packet of type 2+ NA> Name Field size Type Expected Comment NA> fields in value bytes [Killed.] NA> Compatibility mask structure: NA> Supported Compatibility mask NA> system types FTSC packet types NA> packages NA> High bits Low bits NA> U 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 NA> 2+,3, and 7 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 1 NA> 2+,3, and 5 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1 NA> 2+ 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 NA> Stone Age 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 NA> There is also type 2.2. Do you need him? I still don’t understand where the flags in .pkt are located... how can I find out what the letter is? requires, for example, confirmation of receipt/reading? everything is clear in .msg.Crap! how do I attach attach to NAM? view Larka's database? and by There is no way for the output .pkt to determine that the file is also flying with it? ZXNet: 500:8462/1 ~/ <~ http://zx.fatal.ru/ Fido: 2:5057/21.93 /_ _> SkyNet: 71:170/21