On Jul 1, 2025, at 9:23 PM, Jon Steinhart <[email protected]> wrote: > > Ken Hornstein writes: >>> what am I missing here? >>> [...] >> >> Jon's desire (which I share) would be to make this available to scan(1) >> which really means (a) giving scan the ability to parse MIME messages >> and (b) making the MIME information available to the format engine. >> It's a tall order. >> >> --Ken > > So here's what I'd like which as I said earlier is already done, just > not in a convenient way for scan: > > 4506 07/24 redacted-email-adr Board Packet - June 29th, 2025 4pm > 4506.1.2 imge/png - image001.png > 4506.2 application/pdf - 6.29.25 Board Meeting Agenda.pdf > 4506.3 application/pdf - 6.29.25 Board Motions.pdf > 4506.4 application/pdf - OCF BoD Minutes 6.2.25.pdf > 4506.5 application/pdf - ED Board Report - June 29, 2025.pdf > 4506.6 application/pdf - Balance Sheet May 2025.pdf > 4506.7 application/pdf - P&L May 2025.pdf > 4506.8 application/pdf - Committee Best Practices Committee Minutes > 4-15-25.pdf > 4506.9 application/pdf - Elders Committee Minutes 5-22-25.pdf > 4506.10 application/pdf - Energy Park 4.6.2025 Minutes.pdf > 4506.11 application/pdf - Energy Park 5.18.25 Minutes.pdf > 4506.12 application/pdf - Food Committee Closed Work Session 5.27.25.pdf > 4506.13 application/pdf - Path Planning Committee Board Report May > 2025.pdf > 4506.14 application/pdf - Craft Committee Letter of Interest - Tash > Wesp.pdf > 4506.15 application/pdf - Craft Committee Letter of Support - Tash > Wesp.pdf
One idea I had was to use subfolders for MIME messages. For example, if message 6 is a MIME message with parts 1.1 text, 1.2 html 2 image, this might be stored as 6/header, 6/contents, 6/1.1, 6/1.2, 6/2 The contents file indicates the content metadata for all the parts. If a part's content metadata contains a filename, this name can be (sym)linked to the part number. Optionally an extension can be given for a part file to indicate what it is without having to read the contents file. If a part contains a forwarded email message, it can be similarly unpacked (may be on demand). This can be done on INCorporating messages or on demand (when specific commands are run). This would make composition easier as well -- given part files, the contents file can be created semiautomatically by running "file" on them. [I looked at what plan9's upasfs does but felt that was a bit excessive. https://9p.io/magic/man2html/4/upasfs ] Unfortunately I didn't make enough progress on my Go rewrite of nmh.... FWIW.
