Subj : Re: FTN  / Usenet to a new BBS
To   : Joacim Melin
From : tenser
Date : Sun May 10 2020 06:11:21

On 09 May 2020 at 07:26p, Joacim Melin pondered and said...
 
 JM> I didn't know about the RFC1036 format but yeah - that's the general
 JM> idea. if it can't be done then that's not the end of the world but it
 JM> would be pretty neat to get it to work. 

Oh it can definitely be done.  It's just a matter of
massaging the data formats.  The biggest problem is
mapping BBS users to RFC822-style email addresses for
RFC1036 headers.  For that, you probably want to divine
the origin and then do a nodelist lookup of some kind,
or else make something up.  BBS user names fit into
fix-width fields in message headers, and can contain
spaces, so you've got to invent some syntax for papering
that over.

The only other really serious issue is that RFC1036-style
Message-ID: headers must be globally unique, and there's
no guarantee that FTN-style MSG files even have a message
ID at all.  There's some FTSC standard for this, though,
that seems ok.

--- Mystic BBS v1.12 A46 2020/04/20 (Windows/32)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.