BBS:      TELESC.NET.BR
Assunto:  Re: Weekly nodelist report on noteworthy changes (093)
De:       Wilfred van Velzen
Data:     Mon, 6 Apr 2026 21:54:02 +0200
-----------------------------------------------------------
Hi mark,

On 2026-04-06 08:12:54, you wrote to me:

 WV>> I don't know why this was implemented into FMail.

 ml> because some wanted/needed to use another transmission format/protocol at
 ml> times... especially when tunneling FTN through other networks and their
 ml> protocols... tunneling like this is how fidonet was able to connect
 ml> internationally and overseas...

It's clear why it was useful. It's not clear to me why it was implemented in a tosser, instead of in a specialized piece of separate software...

 WV>> I don't think this is a job for a tosser.

 ml> creating an outbound bundle of messages in a non-FTN format? i guess i could
 ml> agree if one were FTN-centric and didn't support other non-FTN protocols...

 ml> i mean, how hard is it to output a FTN packet in UUEncode, XXEncoding, or some
 ml> other similar encoding that stores binary data in ASCII format? spit it out in
 ml> a text file into an email server's outbound or in a directory and let some
 ml> other external process handle moving it to the email server's outbound...

It's not hard, just not a job for a tosser. It's a job for a mailer.

 ml> is this needed today? no but there are some who are playing around
 ml> with the old methods so they can understand things better... having a
 ml> FTN mailer that can support creating outbound FTN packets wrapped in a
         ^^^^^^
So you agree with me! ;-)

 ml> different form for sending via non-FTN methods isn't really bad... it
 ml> does help to alleviate the need to figure out and script the
 ml> intermediate steps...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
 * Origin: FMail development HQ (2:280/464)

-----------------------------------------------------------
[Voltar]