TID: Mystic BBS 1.12 A46   
   MSGID: 2:301/113 f7f9000e   
   REPLY: 1:129/215 969d8bb9   
   TZUTC: 0100   
   Hi G00r00   
      
   I know I need to update to the A47 version, but I have too many things on my   
   plate at the moment, and I am also unable to work due to massive disc   
   problems. I can't sit in front of the PC non-stop and do everything because I   
   want to do a clean installation of the A47 with data transfer to /mysticbbs   
   and no longer to /home/mystic/mysticbbs/..... There are a few things that   
   need to be done, but it's not going so quickly with the disc problems.   
      
    g0>  AS> I always have problems receiving and processing files with TIC and   
    g0>  AS> attachments (tossing) if the attachment or the TIC file has a space i   
    g0>  AS> the name. This does not cause any problems for Windows users because   
    g0>  AS> they can handle spaces, but it does for us Linux and Raspberry Pi use   
    g0>  AS> with a Linux.   
    g0>    
    g0> Another thing to consider here is that in Unix systems filenames are case   
    g0> sensitive.  So for example:   
      
   Yes, I realise that the addon/option would have to harmonise the filenames   
   all to lower case and without spaces that are previously replaced by   
   underscores "_" before sending these files via the FTN mailer with a TIC file   
   to it.   
      
   The other question in general is whether it doesn't also make sense that file   
   uploads are generally harmonised and stored on the hard disk in lower case   
   and without spaces which are replaced by underscores "_". Then the problem   
   would always be solved in any case.   
      
    g0>    
    g0>  AS> + Jan 09 09:25:37 File MyGUI v1.0.2.26.zip Area FSX_MUTL From 21:1/10   
    g0>    
    g0> If your .TIC has "MyGUI v1.0.2" as the filename but the actual file is   
    g0> "mygui v1.0.2" in lower case, then those are not the same files in Unix.   
    g0> This could be a reason why it would work in Windows (which is not case   
    g0> sensitive) but not in Linux.   
    g0>    
    g0> If we determine this is your issue, then maybe what I can do is add a new   
    g0> option that you can turn on to make that TIC filename check case   
    g0> insensitive in Unix.   
    g0>    
      
   As far as I know, A47 users are also affected by the same problem, so it   
   seems to me that this problem is not fixed yet. As I said, it would be best   
   to have a parameter that you can switch on/off. So that the religion of the   
   20th century does not collide with the religion of the 21st century. There   
   are different views on what needs to be solved where and when 8.3 or   
   harmonised long file names.    
      
   Best regards   
      
        Alisha Manuela   
   --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)   
    * Origin: swissIRC BBS (2:301/113)   
   SEEN-BY: 1/123 15/0 30/0 80/1 90/1 103/705 105/81 106/201 120/340   
   SEEN-BY: 123/131 129/305 153/7715 154/10 218/700 221/1 6 226/30 227/114   
   SEEN-BY: 229/110 307 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 920/1 5020/1042 5058/104   
   PATH: 301/113 1 229/426