MSGID: 2:280/464.47 67e27324   
   REPLY: 1770.binkd@1:2320/105 2c469bd7   
   PID: JamNNTPd/Linux 1   
   CHRS: LATIN-1 2   
   TZUTC: 0100   
   TID: CrashMail II/Linux 1.7   
   Mike wrote (2025-03-24):   
      
    >> I think I did have that problem once and the way I got around it was to   
    >> create a vfat filesystem for that directory.   
      
    MP> That is another idea worth trying.   
      
   There are other filesystems that are or can be mounted case-insensitive too:   
   exFAT, NTFS, JFS, XFS, ext4, f2fs, zfs.   
      
   ext4 and f2fs is a bit complicated. NTFS can be mounted with mount.lowntfs-3g.   
   I think the easiest ones are vfat, exfat, jfs and zfs. I just tried jfs and   
   zfs and it seems to work fine. Just in case you want to use a more   
   sophisticated (journaled) filesystem than vfat/exfat.   
      
   truncate -s 256M /tmp/jfs.img   
   mkfs.jfs -O /tmp/jfs.img   
   mount /tmp/jfs.img /mnt   
      
   truncate -s 256M /tmp/zfs.img   
   zpool create testpool /tmp/zfs.img   
   zfs create -o casesensitivity=insensitive testpool/outbound   
      
   You could also use Squish on Linux.   
      
   ---   
    * Origin: No REPLY kludge - no reply (2:280/464.47)   
   SEEN-BY: 10/0 1 102/401 103/1 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 129/305 153/757 7715 154/10 30 110 203/0 214/22 218/0 1 215   
   SEEN-BY: 218/601 700 720 840 860 880 940 221/0 226/30 227/114 229/110   
   SEEN-BY: 229/114 200 206 275 300 307 317 426 428 470 550 664 700 705   
   SEEN-BY: 240/1120 5832 266/512 280/464 5003 5006 5555 291/111 292/854   
   SEEN-BY: 292/8125 301/1 310/31 320/219 322/757 341/66 234 342/200   
   SEEN-BY: 396/45 423/120 460/58 467/888 633/280 712/848 770/1 902/26   
   SEEN-BY: 5020/400   
   PATH: 280/464 103/705 218/700 229/426