Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    MYSTIC    |    Mystic support echo    |    16,010 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 13,705 of 16,010    |
|    Bj”rn Wiberg to g00r00    |
|    Potential left-over files when downloadi    |
|    05 Aug 21 09:27:56    |
      TID: Mystic BBS 1.12 A47       MSGID: 2:201/137 75cd5e57       TZUTC: 0200       Hello g00r00!              As you already know, most archivers are configured in Mystic to junk paths on       unpacking.              I noticed that when viewing an archive which doesn't use the built-in archive       viewer -- i.e. the archive is not ZIP/RAR/LHA/LZH -- and which contains files       in subdirectories, and selecting (D)ownload File from the archive view prompt       (prompt #304), and then entering a path as part of the File Name prompt       (prompt #353), e.g. subdir/subdir.txt, Mystic will extract the file (the       archiver will junk the paths of the extracted file) and then look for the file       as subdir/subdir.txt to send to the user, fail to find it, and the file (named       subdir.txt only, not in a subdirectory, as the paths were junked) will be left       over in the root of the temp* directory.              Is there any smart way to avoid this? Could Mystic perhaps perform a 'basename        |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca