TID: Mystic BBS 1.12 A48   
   MSGID: 1:129/215 969d8bb9   
   REPLY: 2:301/113 6f7116de   
   TZUTC: -0500   
    AS> I always have problems receiving and processing files with TIC and   
    AS> attachments (tossing) if the attachment or the TIC file has a space in   
    AS> the name. This does not cause any problems for Windows users because   
    AS> they can handle spaces, but it does for us Linux and Raspberry Pi users   
    AS> with a Linux.   
      
   Another thing to consider here is that in Unix systems filenames are case   
   sensitive.  So for example:   
      
    AS> + Jan 09 09:25:37 File MyGUI v1.0.2.26.zip Area FSX_MUTL From 21:1/100   
      
   If your .TIC has "MyGUI v1.0.2" as the filename but the actual file is "mygui   
   v1.0.2" in lower case, then those are not the same files in Unix.  This could   
   be a reason why it would work in Windows (which is not case sensitive) but not   
   in Linux.   
      
   If we determine this is your issue, then maybe what I can do is add a new   
   option that you can turn on to make that TIC filename check case insensitive   
   in Unix.   
      
   ... No honey, I can't eat with the family. My computer gets lonely!   
   --- Mystic BBS v1.12 A48 2022/01/07 (Windows/32)   
    * Origin: Sector 7 * Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 15/0 30/0 80/1 90/1 103/705 105/81 106/201 120/340   
   SEEN-BY: 120/616 123/10 131 129/215 305 153/7715 154/10 30 40 50 700   
   SEEN-BY: 203/0 218/700 220/80 90 221/1 6 226/18 30 227/114 201 229/110   
   SEEN-BY: 229/307 310 424 426 428 452 550 664 700 240/1120 5832 249/206   
   SEEN-BY: 249/317 400 266/512 280/464 282/464 1038 292/854 301/0 1   
   SEEN-BY: 301/101 113 317/3 320/219 322/757 335/364 341/66 342/200   
   SEEN-BY: 396/45 633/280 712/848 770/1 920/1 2320/105 3634/12 5020/1042   
   SEEN-BY: 5058/104   
   PATH: 129/215 154/10 301/1 229/426