did I get it right? You have a single share which is read-only for you users. This share contains symlinks to other shares where the user has write-access?
Well, I guess for Windows it is not a different share as it does not know anything about symlinks. And the recycle bin works for drives. So Win tried to create the bin on your read-only share. Where it does not have write-access and thus cannot create the bin.
I am unsure if the mentioned options really help.
The point here is,when Windows uses the recycle bin it actually does not move the files there in, it flags them as “pending” (or so) and only touches the directory entry. It does not move the data (this would take too long). So when not touching data it cannot have recycle bin on a different physical device.
Are your shares all set to
browseable=yes? I read some related post telling this helped.
But it is an interesting question, what happens when the user has write access? Does Samba then move the file? I don’t know. I would try to give write access and see if it works then.