Description of problem:

caja tries to set Permissions of $HOME/.config/caja to 755 and fails due to NetApp NTFS security style
Our home directories are qtrees lying on a NetApp volume on a NetApp Filer.
The NetApp FIlesystem provides multiprotocol access, so both NFSv4 and CIFS are possible on the same data.
For settings ACLs, there exist three so called "security styles": ntfs, unix, mixed
NTFS: you can set the permissions via windows explorer security tab. When you want to access a file from unix/linux, the NetApp Filesystem maps the permissions to fit.
UNIX: you can set the permissions via chmod from linux. When you want to access a file from CIFS, the NetApp Filesystem maps the permissions to fit.
Mixed: both worlds can set permissions, but you are advised to not use this mode, as one style can overwrite the other one.

As the homedirectories are normally accessed by windows, we decide to use the ntfs style.
A file in windows, where I have full permission on, maps in linux to "-rwx------"/ 700
Even every directory in my homedir maps to "drwx------"/700.
Now here is the problem, caja tries to modify the permissions of his folder in $HOME/.config/caja to "drwxr-xr-x" / 755, and it fails as linux is forbidden to set permissions.

I think it has something to do with this one
https://github.com/mate-desktop/caja/blob/master/libcaja-private/caja-file-utilities.c#L84
Why it is important to setup the dir as 755, as home directory in linux is normally created as 700?
So even if the caja folder can reached by other users, the home directory not, so I don't see a reason for this.

Version-Release number of selected component (if applicable):
caja-1.16.6-1.el7.x86_64

How reproducible:
easy with local users
not so easy with remote folders, as they are not so many users with multiprotocol access I think ;-)

Steps to Reproduce:
As normally people doesnt have a netapp filer, try the following:
1. create a test user with local homedirectory and login there with mate active (I do this via vnc).
2. A folder $HOME/.config/caja is created ,with permission 755.
3. Exit from mate (in my example kill the vnc session) and change the permission of the folder to 700 (for example via SSH)
4. Start VNC again, and the folder is changed back to 755

Actual results:
caja fails to start as it tries forever to set the $HOME/.config/caja permission to 755

Expected results:
ignore the mode bits, just check if the user has write access to the folder

Additional info: