Samber indirect implementation can only be uploaded and cannot be deleted

The indirect implementation of Samber can only be uploaded and cannot be deleted-Linux Enterprise Application-Linux server application information. The following is a detailed description. I found a lot of articles on this proposition on the Internet, and finally referred to this knowledge point to indirectly implement this function.
The general idea is to add T-bits to the shared folder. I tried to use umask IN THE Samber configuration file to specify the T bit, but it cannot be implemented. Only RWX permissions can be specified. Later, I thought of letting the files or folders created under the shared folder inherit the permissions of folders in the group to which the shared folder belongs. However, after the client is uploaded through WINDOWS, the owner is still a common user. With W permissions, you can still delete files uploaded by yourself.
Finally, the shared folder owner group is all designated as ROOT, and another script is written as chown root folder name? R
Chmod 1700 folder name? R
Then, use crontab to set an interval, which means that normal users cannot delete the file after the upload time.
You only need to have the permissions to delete the file. Therefore, you must control the permissions.