enh: add backend check for download permission for cloud attachements

[hamza221]

For now it silently Fails on draft/outbox save/update

• [x] Find a way to reflect in the front end for versions prior to 3.6 if needed (not needed)

[hamza221]

they're supposed to be filtered out, it's a regression, I'm investigating update: https://github.com/nextcloud/mail/commit/0958ec341a8f6fa712057f4d96314f03b0c12351

[hamza221]

I'm still investigating the frontend regression, my doubt i that it's a filepicker regression, since share-attributes are not shown anymore, I'm checking with other colleagues

[st3iny]

I'm still investigating the frontend regression, my doubt i that it's a filepicker regression, since share-attributes are not shown anymore, I'm checking with other colleagues

Sounds good. I'd also say that we can move forward with this PR and look at the frontend separately.

[hamza221]

@st3iny fyi frontend is fixed here #9697

[st3iny]

/backport to stable3.7

[st3iny]

/backport to stable3.6

[hamza221]

/backport to 2.9

Update : typo :'(

[backportbot[bot]]

The backport to 2.9 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout 2.9
git pull origin 2.9

# Create the new backport branch
git checkout -b backport/9592/2.9

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick f0e072ed

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/9592/2.9

Error: Failed to clone repository: Failed to checkout branches: error: pathspec '2.9' did not match any file(s) known to git

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[hamza221]

/backport to stable2.2

[hamza221]

/backport to stable1.15