Subj : Re^8:  Directly include binary data in messages
To   : James Coyle
From : Tim Schattkowsky
Date : Mon Mar 21 2022 07:29 pm

//Hello James,//

on *02.03.22* at *4:36:01* You wrote in Area *FTSC_PUBLIC*
to *Rob Swindell* about *"Re: Re^2:  Re^4:  Directly include binary data in messages"*.

RS>> Sure, either way. rob at synchro dot net or FTN netmail. They end up in
RS>> the same inbox.

JC> Cool deal I will send it along.

JC> I ended up having a backup of the code and the document so I put it all
JC> back into Mystic this evening.  I am in the process of putting up a build
JC> for anyone to test that supports the STARTTLS implementation of the
JC> document I will send.

JC> I haven't tested it much though just enough to see it actually work once
JC> between a Mystic client/server.

JC> The documentation is a bit sloppy, not really intended to be anything
JC> formal.

So is there now any implementation BinkP implementation using STARTTLS and what are the details?

BTW: RFC8314 suggests already in the introduction that for email, implicit TLS should be preferred over STARTTLS :)

Regards,
Tim

--- WinPoint 407.1
* Origin: Original WinPoint Origin! (2:240/1120.29)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.