[nos-bbs] JNOS mime aware prototype (another update)

[maiko at pcsinternet.ca]

I have updated the source again in the rsync area.

I now have a good start for anyone that wants to test more complex
scenarios, but I can confirm the following.

I used PINE to send a test message and 3 attached files (jpeg, pdf, and 
jpg)
to my local JNOS account. What that means if if you were on the BBS and 
you
were to read your mail, you will see something like the following :

    Message #32
    Date: Fri, 22 Apr 2022 15:29:41 -0500 (CDT)
    From: mikey <root at slackware.localdomain>
    To: ve4klm at 192.168.4.201
    Subject: test jpeg pdf jpg

      This message is in MIME format.  The first part should be readable 
text,
      while the remaining parts are likely unreadable without MIME-aware 
tools.

    -------------------------
    Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII

    text
    jpeg pdf jpg
    halo
    maiko
    -------------------------
    Content-Type: IMAGE/JPEG; name=copyright.jpeg
    Content-Transfer-Encoding: BASE64
    Content-ID: 
<alpine.LNX.2.11.2204221529410.27969 at slackware.localdomain>
    Content-Description: jpeg
    Content-Disposition: attachment; filename=copyright.jpeg

    Saved to : /jnos/public/copyright.jpeg
    -------------------------
    Content-Type: APPLICATION/PDF; name=ve4klm_QSL_design1.pdf
    Content-Transfer-Encoding: BASE64
    [snip]

If anyone has suggestions for better formatting or if you don't want the
MIME headers present, whatever, please give me your comments. Thanks.

IF you are using thunderchicken or whatever to pop your mail, you will 
see
the same, however you will have to ftp to your /jnos/public area to grab
the files. What I am getting at is for those who want to stick with the
conventional text based and BBS prompt based systems, this is for you.

You will not see gibberish anymore, files are saved to whatever path is
setup for that user in ftpusers file. I hope that makes sense.

I have NOT tried this on recursive mime content. In other words if you
forward an email that already has attachements within, and other complex
possibilities. I need to find those exceptions and deal with them as 
they
happen (that's the approach right now).

Anyways, that's the last I will mention on the list for now. It's there
for people to play with, let me know how we can maybe make it better ?

Maiko / VE4KLM