Based on the README documentation, it appears that the vfs_recycle module should be enabled by default in Samba docker container. However, when attempting to delete a file from the Samba network shared directory, the files are being deleted directly instead of being moved to the expected .deleted folder. This behavior has been observed while connecting to and deleting files from the network shared directory on both Mac Big Sur and Windows 10 machines
Despite following the recommended steps, including attempting to create the .deleted folder manually, the issue persists. The .deleted folder does not exist, and manually creating it does not yield any difference in the observed behavior.
Given this situation, I am seeking assistance in understanding the root cause of this issue. Could there be a specific reason why the vfs_recycle module is not functioning as expected? Has there been any recent change in the module's behavior or compatibility with the current Samba version? I appreciate any insights or recommendations to address this matter.
Based on the README documentation, it appears that the vfs_recycle module should be enabled by default in Samba docker container. However, when attempting to delete a file from the Samba network shared directory, the files are being deleted directly instead of being moved to the expected .deleted folder. This behavior has been observed while connecting to and deleting files from the network shared directory on both Mac Big Sur and Windows 10 machines
Despite following the recommended steps, including attempting to create the .deleted folder manually, the issue persists. The .deleted folder does not exist, and manually creating it does not yield any difference in the observed behavior.
Given this situation, I am seeking assistance in understanding the root cause of this issue. Could there be a specific reason why the vfs_recycle module is not functioning as expected? Has there been any recent change in the module's behavior or compatibility with the current Samba version? I appreciate any insights or recommendations to address this matter.
smb.conf has the following configuration: