Can I test tg_BBS right here? I would like to see how correctly messages are generated in Fido echo conferences now.

--- tg BBS v0.6.3
* Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/256)

Greetings Brother!

Tuesday February 09 2021 19:05, you wrote to All about an urgent matter!:

Can I test tg_BBS right here? I would like to see how correctly
messages are generated in Fido echo conferences now.

Dont see why not... Got you on the west coast US


----
Regards,


Rick Smith (Nitro)

... BBSing, the 'Electronic High'
--- GoldED+/LNX 1.1.5-b20180707
* Origin: ----> Abacus Sysop Point --->>>>bbs.abon.us:2323 (1:105/10.1)

Hello Brother.

09 Feb 21 19:05, you wrote to all:

@MSGID: 2:460/256 00000003
@PID: tg_BBS_v0.6.3
@CHRS: CP866 2
@REPLYTO 2:460/256 534732808
Can I test tg_BBS right here? I would like to see how correctly
messages are generated in Fido echo conferences now.

--- tg BBS v0.6.3
* Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/256)
SEEN-BY: 103/705 124/5016 154/10 203/0 221/0 1 6 360 229/101 240/1120
1634
SEEN-BY: 240/1895 5832 8002 8005 261/38 280/464 5003 5555 288/100
292/854
SEEN-BY: 292/8125 310/31 313/41 335/364 371/52 380/5 382/147 396/45
423/81
SEEN-BY: 423/120 460/58 256 777 1124 5858 712/848 770/1 2452/250
5054/30
@PATH: 460/256 58 280/464 221/1 240/1120

Daniel

--- GoldED+/EMX 1.1.4.7
* Origin: Roon's BBS - Budapest, HUNGARY (2:371/52)

Hi Brother,

On 2021-02-09 19:05:13, you wrote to All:

@MSGID: 2:460/256 00000003
@PID: tg_BBS_v0.6.3
@CHRS: CP866 2
@TGUID: 534732808
@REPLYTO 2:460/256 534732808

A replyto kludge in echomail, that is the same as the senders nodenumber: Waste of space. ;)

@RealName: Stas Mishchenkov 2:460/58

And no TZUTC kludge...

Can I test tg_BBS right here? I would like to see how correctly
messages
are generated in Fido echo conferences now.

--- tg BBS v0.6.3
* Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/256)
SEEN-BY: 103/705 124/5016 154/10 203/0 221/0 6 229/101 240/5832 280/464 SEEN-BY: 280/5003 5555 288/100 292/854 8125 310/31 396/45 423/120 460/58 SEEN-BY: 460/256 777 1124 5858 712/848 770/1 2452/250 5054/30
@PATH: 460/256 58 280/464

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi, Rick!

09 ENo 21 08:25, Rick Smith -> Brother Rabbit:

Can I test tg_BBS right here? I would like to see how correctly
messages are generated in Fido echo conferences now.

Dont see why not... Got you on the west coast US

Thanks. It flew so quickly.

Have nice nights.
Stas Mishchenkov.

--- - a+4a, *<-r< p 4N!N u<2<oa aaoi<2N2ab%, ro *<, <>Nr% 4N!N o<tN*%?
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi, Wilfred!

09 ENo 21 17:57, Wilfred van Velzen -> Brother Rabbit:

@REPLYTO 2:460/256 534732808

A replyto kludge in echomail, that is the same as the senders nodenumber: Waste of space. ;)

In this case, it is necessary. It allows you to reply by netmail to the author of the message. Just try it.

@RealName: Stas Mishchenkov 2:460/58

And no TZUTC kludge...

I'm just working on it. Must it be, or should it be?

Have nice nights.
Stas Mishchenkov.

--- araa<br% - 0r< -<una o?n?*% b?b%-? ? ob><4?!aN*%, tr< oaio2 4<2<-a -p>?r%
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Can I test tg_BBS right here? I would like to see how correctly messages are generated in Fido echo conferences now.

As long as spelling mistakes don't count in SUBJ and BODY of msg, then all should be good, even a "requset" whatever that is! <G>


--- tg BBS v0.6.3
* Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/256)

Hi Stas,

On 2021-02-09 21:10:28, you wrote to me:

@REPLYTO 2:460/256 534732808

A replyto kludge in echomail, that is the same as the senders
nodenumber: Waste of space. ;)

In this case, it is necessary. It allows you to reply by netmail to the author of the message. Just try it.

You mean to the author on Telegram? It would be easier to just use Telegram if I wanted to reply privately! ;)
That would also be more secure, and not depend on netmail routing (which sometimes is broken).

And no TZUTC kludge...

I'm just working on it. Must it be, or should it be?

Well your message arrived here without it. So it isn't necessary, but it is a nice to have!

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Brother,

Can I test tg_BBS right here? I would like to see how correctly
messages are generated in Fido echo conferences now.

Sure, this is a testing area after all.. :)

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hi, August!

09 ENo 21 21:55, August Abolins -> Brother Rabbit:

Can I test tg_BBS right here? I would like to see how correctly
messages are generated in Fido echo conferences now.

As long as spelling mistakes don't count in SUBJ and BODY of msg, then all should be good, even a "requset" whatever that is! <G>

Like any self-respecting biker, I have several stab wounds. One of them damaged the nerves on the arm. Now I often make typos, but it gradually goes away. ;)

Have nice nights.
Stas Mishchenkov.

--- ao<i<n!aN iaia n<2a!a ><-aoooar% b?b%-?. ca4pa!NN !N n<2a!a,!< r<aN o>aaoN
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hello Brother,

Can I test tg_BBS right here? I would like to see how correctly messages are generated in Fido echo conferences now.

Sure, this is a testing area after all.. :)

Ttyl :-),
Al

Thanks. Continue testing.


--- tg BBS v0.6.3
* Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/256)

Hi, Wilfred!

09 ENo 21 20:47, Wilfred van Velzen -> Stas Mishchenkov:

@REPLYTO 2:460/256 534732808

You mean to the author on Telegram?

In this case, yes.

It would be easier to just use Telegram if I wanted to reply
privately! ;) That would also be more secure,

Meanwhile, this opportunity is used, which means it is convenient.

and not depend on netmail routing (which sometimes is
broken).

I also noticed this and made a large number of password links to be able to avoid this.

Have nice nights.
Stas Mishchenkov.

--- iEne-, >eaea?o*?o 2er< o a?4ENa<><2N, ipnpr oouo!Nr% ?o ana oa b4eo o -or2N
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

On 10 Feb 2021, Stas Mishchenkov said the following...

As long as spelling mistakes don't count in SUBJ and BODY of msg, the should be good, even a "requset" whatever that is! <G>

Like any self-respecting biker, I have several stab wounds. One of them damaged
the nerves on the arm. Now I often make typos, but it gradually goes
away. ;)

I may not be a biker, but I make typos all of the time. It happens. One now defunct MMORRPG I played I was famous for my typos.

--- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
* Origin: theoasisbbs.ddns.net:1357 (1:106/127)

Hi Stas,

On 2021-02-10 13:39:38, you wrote to me:

It would be easier to just use Telegram if I wanted to reply
privately! ;) That would also be more secure,

Meanwhile, this opportunity is used, which means it is convenient.

Not just for testing? ;)

and not depend on netmail routing (which sometimes is
broken).

I also noticed this and made a large number of password links to be able to
avoid this.

Me too, but I don't have links to every region in fidonet... ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi, Wilfred!

10 ENo 21 13:22, Wilfred van Velzen -> Stas Mishchenkov:

It would be easier to just use Telegram if I wanted to reply
privately! ;) That would also be more secure,

Meanwhile, this opportunity is used, which means it is convenient.

Not just for testing? ;)

I do not read transit traffic, but I see from the logs that there is traffic in the netmail.

and not depend on netmail routing (which sometimes is
broken).

I also noticed this and made a large number of password links to be able
to avoid this.

Me too, but I don't have links to every region in fidonet... ;)

As soon as I notice that there is no netmail coming from me somewhere or to me from somewhere, I make another link to bypass the broken path.

Have nice nights.
Stas Mishchenkov.

--- aron!< iooaNr r<2%-< oa r<, tr< ><4!?*%. C2-<u<2%.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi Stas,

On 2021-02-10 17:48:34, you wrote to me:

and not depend on netmail routing (which sometimes is
broken).

I also noticed this and made a large number of password links to be
able to avoid this.

Me too, but I don't have links to every region in fidonet... ;)

As soon as I notice that there is no netmail coming from me somewhere or to
me from somewhere, I make another link to bypass the broken path.

You should also try to get the broken route fixed!

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi, Wilfred!

10 ENo 21 17:22, Wilfred van Velzen -> Stas Mishchenkov:

As soon as I notice that there is no netmail coming from me somewhere
or to me from somewhere, I make another link to bypass the broken
path.

You should also try to get the broken route fixed!

Usually, first I try to contact the appropriate network coordinator or the node on which the routing is broken, but most often I still have to build a bypass path.

Have nice nights.
Stas Mishchenkov.

--- - C oo >< !au?<!a2%!<br?...? - Aa-?-na. C oo? - iNr. - C *< ra-?
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi Stas,

On 2021-02-11 14:22:50, you wrote to me:

As soon as I notice that there is no netmail coming from me
somewhere or to me from somewhere, I make another link to bypass the
broken path.

You should also try to get the broken route fixed!

Usually, first I try to contact the appropriate network coordinator or the node on which the routing is broken,

That would be the right thing to do...

but most often I still have to build a bypass path.

That is not good! :-(

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi Brother,

On 2021-02-09 19:05:13, you wrote to All:

@MSGID: 2:460/256 00000003
@PID: tg_BBS_v0.6.3
@CHRS: CP866 2
@TGUID: 534732808
@REPLYTO 2:460/256 534732808

A replyto kludge in echomail, that is the same as the senders nodenumber: Waste of space. ;)

@RealName: Stas Mishchenkov 2:460/58

And no TZUTC kludge...

Can I test tg_BBS right here? I would like to see how correctly messages
are generated in Fido echo conferences now.

--- tg BBS v0.6.3
* Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/256) SEEN-BY: 103/705 124/5016 154/10 203/0 221/0 6 229/101 240/5832 280/464
SEEN-BY: 280/5003 5555 288/100 292/854 8125 310/31 396/45 423/120 460/58
SEEN-BY: 460/256 777 1124 5858 712/848 770/1 2452/250 5054/30
@PATH: 460/256 58 280/464

Bye, Wilfred.

Is @TZUTC kludge now proper?


--- tg BBS v0.6.3
* Origin: Fido by Telegram BBS by Stas Mishchenkov (2:460/256)

Hi Brother,

On 2021-02-11 16:45:23, you wrote to me:

@PID: tg_BBS_v0.6.3
@TZUTC: 0300

Is @TZUTC kludge now proper?

Yes, it looks ok!

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi, Wilfred!

11 ENo 21 14:54, Wilfred van Velzen -> Brother Rabbit:

@TZUTC: 0300
Is @TZUTC kludge now proper?

Yes, it looks ok!

Must it be "0300" or nay be "+0300"?

Have nice nights.
Stas Mishchenkov.

--- f ?o r<u< ><-<2N!?N, -<r<a<N o!aNr, oatN4 4!pr uaoNrp.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hello Stas,

@REPLY: 2:280/464 60253728
@MSGID: 2:460/5858 60260c87
@PID: GED+W64 1.1.5-b20170303
@CHRS: CP866 2
@TZUTC: 0300
@RealName: Brother Rabbit
@TID: hpt/w64-mvcdll 1.9.0-cur 2020-11-09
Hi, Wilfred!

11 ENo 21 14:54, Wilfred van Velzen -> Brother Rabbit:

@TZUTC: 0300
Is @TZUTC kludge now proper?

Yes, it looks ok!

Must it be "0300" or nay be "+0300"?

Have nice nights.
Stas Mishchenkov.

SEEN-BY: 106/127 153/757 154/10 221/1 6 360 280/464 5555 335/364
460/58 256
SEEN-BY: 460/777 1124 5858 4500/1 5020/1042 5054/30
@PATH: 460/5858 58 221/6

That's what I see..

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hi Stas,

On 2021-02-12 08:04:02, you wrote to me:

@TZUTC: 0300
Is @TZUTC kludge now proper?

Yes, it looks ok!

Must it be "0300" or nay be "+0300"?

From http://ftsc.org/docs/fts-4008.002 paragraph 4:

Implementations must NOT put a plus ('+', ASCII 43, 2Bh) in front of
the offset for positive numbers, but robust implementations should
be prepared to find (and ignore) a plus if it exists.


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi, Wilfred!

12 ENo 21 10:14, Wilfred van Velzen -> Stas Mishchenkov:

From http://ftsc.org/docs/fts-4008.002 paragraph 4:

Implementations must NOT put a plus ('+', ASCII 43, 2Bh) in front of
the offset for positive numbers, but robust implementations should
be prepared to find (and ignore) a plus if it exists.

Thanks. So I did everything right.

Have nice nights.
Stas Mishchenkov.

--- iEne-, >eaea?o*?o 2er< o a?4ENa<><2N, ipnpr oouo!Nr% ?o ana oa b4eo o -or2N
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)