Hello Charles!

** On Friday 18.12.20 - 13:53, Charles Pierson wrote to August Abolins:

What do you mean "normal names" ?

I sent the netmail to August Abolins, not the TGUID.

As Stas mentioned, that would never work. And rightly so -
because any Telegram user can change their name or alias.

Stas's (fido) bbs or the tosser/scanner, wouldn't know to whom
a message should be directed to if he only had a name to go
on. However, Telegram assigns a user id number for every
registered account. Stas simply leverages that to produce the
TGUID in the kludges.

Then, the fido user only has to address their netmail to
TGUID@z:n/f.p and it will reach the Telegram user that matches
the TGUID.

BUT, Stas has mentioned that he would allow Telegram users to
send messages intended for netmail to people directly by using
the following on the first line in a message to the
Fido2telebot:

--to:FN LN z:n/f.p--<CR>

--
../|ug

--- OpenXP 5.0.47
* Origin: Mobile? https://t.me/joinchat/SPBwvE1gkHzEKAkapsHkdQ (2:221/1.58)

Hello Stas!

** On Friday 18.12.20 - 17:28, Stas Mishchenkov wrote to August Abolins:

2020-12-16 03:51:01 [1905] From: August Abolins 2:221/1.58
2020-12-16 03:51:01 [1905] To : 1223717052
2020-12-16 03:51:05 [1905] Got error: Forbidden: bot was blocked by the user

Huh? I haven't changed anything with the Fido2telebot. :(


But, I just noticed that the setting for the bot was "Bot
blocked". I swear that I did not purposely do that.

Anyway, I did a /start on it and it seems that it should be
operational now.

Interesting. It's actually pretty cool to have control over
that and block incoming "netmail" that way.

--
../|ug

--- OpenXP 5.0.47
* Origin: Mobile? https://t.me/joinchat/SPBwvE1gkHzEKAkapsHkdQ (2:221/1.58)