Hi All!handle.
This message should be close to the max char coun that Telegram cna
Then, the idea is to see how Telegram handles a R)eply with the originalwhen quoted.
123456789+123456789+123456789+And now let's see what a Reply will look like.
@MSGID: 2:460/58 00000405
@REPLY: 2:460/58 00000403
@PID: tg2fido_gate_v0.6.1
@INTL 2:333/808 2:460/58
@TOPT 7
Hi August,Pwd, Sec
On 2020-10-16 15:18:11, you wrote to August Abolins:
@MSGID: 2:460/58 00000405
@REPLY: 2:460/58 00000403
@PID: tg2fido_gate_v0.6.1
@INTL 2:333/808 2:460/58
@TOPT 7
My tosser gave warnings on this message:
14:20:13.107 Processing 89904904.pkt from 2:221/0 to 2:280/464 14:20:13.107 Pkt info: HPT 1.9, Type 2+, 4773, 2020-10-16 14:19:54,
14:20:13.107 Warning: Found netmail kludge in echomail: INTL 2:333/8082:460/58
14:20:13.107 Warning: Found netmail kludge in echomail: TOPT 7Is that the original 4096 char message that I just replied to?
Bye, Wilfred.
@MSGID: 2:460/58 00000407
@REPLY: 2:460/58 00000406
@PID: tg2fido_gate_v0.6.1
@INTL 2:280/464 2:460/58
Is that the original 4096 char message that I just replied to?@MSGID: 2:460/58 00000405
@REPLY: 2:460/58 00000403
@PID: tg2fido_gate_v0.6.1
@INTL 2:333/808 2:460/58
@TOPT 7
My tosser gave warnings on this message:
14:20:13.107 Processing 89904904.pkt from 2:221/0 to 2:280/464
14:20:13.107 Pkt info: HPT 1.9, Type 2+, 4773, 2020-10-16 14:19:54,
Pwd, Sec
14:20:13.107 Warning: Found netmail kludge in echomail: INTL
2:333/808 2:460/58
14:20:13.107 Warning: Found netmail kludge in echomail: TOPT 7
Bye, Wilfred.
Hi August,14:19:54,
On 2020-10-16 15:29:12, you wrote to Wilfred van Velzen:
@MSGID: 2:460/58 00000407
@REPLY: 2:460/58 00000406
@PID: tg2fido_gate_v0.6.1
@INTL 2:280/464 2:460/58
This one has it too. It seems to be the gate software that adds these.
@MSGID: 2:460/58 00000405
@REPLY: 2:460/58 00000403
@PID: tg2fido_gate_v0.6.1
@INTL 2:333/808 2:460/58
@TOPT 7
My tosser gave warnings on this message:
14:20:13.107 Processing 89904904.pkt from 2:221/0 to 2:280/464 WvV>> 14:20:13.107 Pkt info: HPT 1.9, Type 2+, 4773, 2020-10-16
Thanks. Maybe the "netmail kludge" is something Stas added in the new version of the bot? Does THIS message have it too?Pwd, SecIs that the original 4096 char message that I just replied to?
14:20:13.107 Warning: Found netmail kludge in echomail: INTL
2:333/808 2:460/58
14:20:13.107 Warning: Found netmail kludge in echomail: TOPT 7 WvV>>
Bye, Wilfred.
It was your reply from Telegram to that message...
Bye, Wilfred.
@MSGID: 2:460/58 00000409
@REPLY: 2:460/58 00000408
@PID: tg2fido_gate_v0.6.1
@INTL 2:280/464 2:460/58
@CHRS: CP866 2
@TGUID: 1223717052
@REPLYTO 2:221/1.58
@RealName: August Abolins 2:221/1.58
Thanks. Maybe the "netmail kludge" is something Stas added in the new version of the bot? Does THIS message have it too?
@MSGID: 2:460/58 00000409
@REPLY: 2:460/58 00000408
@PID: tg2fido_gate_v0.6.1
@CHRS: CP866 2
@TGUID: 1223717052
@REPLYTO 2:221/1.58
@RealName: August Abolins 2:221/1.58
@SEEN-BY: 57/0 220/70 221/0 6 226/17 317/3 340/1000 460/58 777 1124 5858 @SEEN-BY: 467/888 633/267 280 640/1138 1321 1384 712/620 848 770/0 1 100 @SEEN-BY: 772/0 1 220 230 5054/30
@PATH: 460/58 640/1384 712/848 770/1
Thanks. Maybe the "netmail kludge" is something Stas added in the new version of the bot? Does THIS message have it too?
Hi All!handle.
This message should be close to the max char coun that Telegram cna
Then, the idea is to see how Telegram handles a R)eply with the originalwhen quoted.
123456789+123456789+123456789+These will be two different messages. Telegram does not quote in the usual way. Accordingly, each of these two messages can be 4096 characters long.
Hi August,Pwd, Sec
On 2020-10-16 15:18:11, you wrote to August Abolins:
@MSGID: 2:460/58 00000405
@REPLY: 2:460/58 00000403
@PID: tg2fido_gate_v0.6.1
@INTL 2:333/808 2:460/58
@TOPT 7
My tosser gave warnings on this message:
14:20:13.107 Processing 89904904.pkt from 2:221/0 to 2:280/464 14:20:13.107 Pkt info: HPT 1.9, Type 2+, 4773, 2020-10-16 14:19:54,
14:20:13.107 Warning: Found netmail kludge in echomail: INTL 2:333/8082:460/58
14:20:13.107 Warning: Found netmail kludge in echomail: TOPT 7Thanks. Hope I fixed it.
Bye, Wilfred.
@MSGID: 2:460/58 00000410
@REPLY: 2:460/58 00000406
@PID: tg2fido_gate_v0.6.1
@INTL 2:280/464 2:460/58
@CHRS: CP866 2
@TGUID: 534732808
@REPLYTO 2:460/58
@RealName: Stas Mishchenkov 2:460/58
14:20:13.107 Warning: Found netmail kludge in echomail: INTL
2:333/808 2:460/58
Thanks. Hope I fixed it.
Thanks. Maybe the "netmail kludge" is something Stas added in the new version of the bot? Does THIS message have it too?
Didn't have it when I saw the message. It could have been stripped
somewhere along the line. Either that, or HPT strips it when the message
is tossed.
messageDidn't have it when I saw the message. It could have been stripped somewhere along the line. Either that, or HPT strips it when the
is tossed.
I noticed one thing. In Hpt/JAM the @INTL is not present, but in Hpt/Squish it is. :)
On 17 Oct 2020, 08:52a, Tommi Koivula said the following...
Didn't have it when I saw the message. It could have been stripped
somewhere along the line. Either that, or HPT strips it when the message
is tossed.
I noticed one thing. In Hpt/JAM the @INTL is not present, but in
Hpt/Squish it is. :)
That's strange... Why would it be stripped for JAM? :/
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 412 |
Nodes: | 16 (2 / 14) |
Uptime: | 19:08:00 |
Calls: | 8,623 |
Calls today: | 9 |
Files: | 13,238 |
Messages: | 5,936,882 |