It was my typing. I just went back and looked at my sent message.
@MSGID: -1001231012163:666
@REPLY: 665
@PID: Telegram to fido gate by Stas Mishchenkov
--- tg2fido.pl
* Origin: Telegram to fido gate by Stas Mishchenkov ()
Hi Stas. 17 Sep 20 04:40:46, August Abolins wrote to Charles
Pierson:
@MSGID: -1001231012163:666 @REPLY: 665 @PID: Telegram to fidoOuch.
gate by Stas Mishchenkov --- tg2fido.pl * Origin: Telegram to
fido gate by Stas Mishchenkov ()
Hello, Tommi Koivula.
On 9/17/20 6:17 AM you wrote:
Hi Stas. 17 Sep 20 04:40:46, August Abolins wrote to CharlesWhy ouch?
Pierson:
@MSGID: -1001231012163:666 @REPLY: 665 @PID: Telegram to fidoOuch.
gate by Stas Mishchenkov --- tg2fido.pl * Origin: Telegram to
fido gate by Stas Mishchenkov ()
--
Best regards!
Posted using Hotdoged on Android
--- Hotdoged/2.13.5/Android
* Origin: Houston, TX, USA (4:902/26.52)
@MSGID: -1001231012163:666
@REPLY: 665
@PID: Telegram to fido gate by Stas Mishchenkov
--- tg2fido.pl
* Origin: Telegram to fido gate by Stas Mishchenkov ()
Ouch.
@MSGID: -1001231012163:666 @REPLY: 665 @PID: Telegram to fido
gate by Stas Mishchenkov --- tg2fido.pl * Origin: Telegram to
fido gate by Stas Mishchenkov ()
Ouch.
Why ouch?
Hi, Chuck! 16 сен 20 22:57, Chuck Pierson -> Tommi Koivula:
Ouch.
Why ouch?No from address in @msgid and Origin line.
Have nice nights.
Stas Mishchenkov.
Stas, I'm not sure why,. But I've seen a couple of messages from you double posted.
Stranger, it isn't only yours. I've seen a couple of different ones duplicated from different systems.
I would like to know at what point they double and for whom. If
these are messages from Fido and you see them in Fido, then I
don't think it's my fault, if these are messages аrom Fido to
Telegram, then I turned off the replay links from Fido's side just because they did not always work correctly on the side of
Telegrams and could have led, among other things, to a doubling of messages in Telegrams.
I would like to know at what point they double and for
whom. [...]
I notice that the MSGIDs from the Telegram messages don't
look like the typical MSGID; hence they don't seem to
work well with the threading mechanisms in Thunderbird or
OpenXP.
MSGID: 2:460/58 -1001231012163:662
MSGID: 2:460/58 -1001231012163:659
MSGID: -1001231012163:663
MSGID: -1001231012163:664
MSGID: -1001231012163:666
Hello Stas! ** On Friday 18.09.20 - 21:35, August Abolins wrote to
Stas Mishchenkov:
I notice that the MSGIDs from the Telegram messages don't lookI take that back! OpenXP handles these things quite well:
like the typical MSGID; hence they don't seem to work well with
the threading mechanisms in Thunderbird or OpenXP.
MSGID: 2:460/58 -1001231012163:662 MSGID: 2:460/58It is Thunderbird that fails to link them in a tree-view
-1001231012163:659 MSGID: -1001231012163:663 MSGID:
-1001231012163:664 MSGID: -1001231012163:666
properly.
--
../|ug
--- OpenXP 5.0.46 * Origin: The future is not what it used to be. (2:221/1.58)
It is Thunderbird that fails to link them in a tree-view
properly.
What are you using thunderbird as?
It appears to be Fido, as at least one of the echoes I see them in
isn't on Telegram. enet.sysop
Hi, Charles! 18 ╤Б╨╡╨╜ 20 00:00, Charles Pierson -> Stas Mishchenkov:
It appears to be Fido, as at least one of the echoes I see themin CP> isn't on Telegram. enet.sysop Apparently someone had a slight
glitch.
Hi, Charles! 18 ╤Б╨╡╨╜ 20 00:00, Charles Pierson -> Stas Mishchenkov:
It appears to be Fido, as at least one of the echoes I see themin CP> isn't on Telegram. enet.sysop Apparently someone had a slight
glitch.
Looking, these dupes all have the same Message ID. I'm starting to
think something is hung up on my side.
Looking, these dupes all have the same Message ID. I'm startingIf they are detected as dupes, there is no problem on your system.
to think something is hung up on my side.
If you have a single link for echomail, then the problem is at
that link. If you have multiple links, then it's to be expected
and nothing you can do about it. ;)
Looking, these dupes all have the same Message ID. I'm starting
to think something is hung up on my side.
If they are detected as dupes, there is no problem on your system.
Nothing is detecting them as duplicates. Just my seeing them.
orIf you have a single link for echomail, then the problem is at
that link. If you have multiple links, then it's to be expected
and nothing you can do about it. ;)
One connection. I think it started just after a connection issue a week
so ago.
I notice that the MSGIDs from the Telegram messages don't look like
the typical MSGID; hence they don't seem to work well with the
threading mechanisms in Thunderbird or OpenXP.
Examples:
MSGID: 2:460/58 -1001231012163:662
MSGID: 2:460/58 -1001231012163:659
MSGID: -1001231012163:663
MSGID: -1001231012163:664
MSGID: -1001231012163:666
The last few posted are missing the 2:460/58
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 410 |
Nodes: | 16 (2 / 14) |
Uptime: | 81:09:12 |
Calls: | 8,579 |
Calls today: | 3 |
Files: | 13,225 |
Messages: | 5,932,301 |