Hello Stas!

** On Tuesday 22.09.20 - 07:48, Stas Mishchenkov wrote to August Abolins:

=== Import 2020-09-22_07-48-09.png Start ===
begin 644 2020-09-22_07-48-09.png MB5!.1PT*&@H````-24A$4@```U,```'Y"`(```#KPO-J```@`$E$051XG.R]

Very cool. Your system detects the included .uue code,
decodes it, stores the file on your server and creates an URL
for it for TgM.

But I think some FTN systems would split the message enroute?

--
../|ug

--- OpenXP 5.0.46
* Origin: The future is not what it used to be. (2:221/1.58)

Hi, August!

22 ᥭ 20 08:16, August Abolins -> Stas Mishchenkov:

=== Import 2020-09-22_07-48-09.png Start ===
begin 644 2020-09-22_07-48-09.png
MB5!.1PT*&@H````-24A$4@```U,```'Y"`(```#KPO-J```@`$E$051XG.R]

Very cool. Your system detects the included .uue code,
decodes it, stores the file on your server and creates an URL
for it for TgM.

Now a message is sent with the URL of the file and the file itself is a separate message with the SUBJ in the description. I think this is a bit redundant. I plan not to send a message if, besides uue, there is nothing else in it. Conversely, the file will not be sent if it is more than fifty megabytes. Only a message with a link will be sent.

But I think some FTN systems would split the message enroute?

I have a desplit procedure. However, this is not convenient and can lead to errors. I plan to simply not broadcast the broken UUE.

Have nice nights.
Stas Mishchenkov.

--- Ÿ ¨§ ⮣® ¯®ª®«¥­¨ï, ª®â®à®¥ §­ ¥â, § ç¥¬ ¬­ãâ £ §¥âã.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)