You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Often govt people use Microsoft Office 356 exclusively and some organisations disable sending attachments alltogether.
It's pretty inefficient sending attachment (Base64 is another encoding layer and adds bytes) and organisations have reasons not to enable sending random files off filesystem and to only allow editing files in the cloud.
There has been multiple published incidents where e.g. govt employees send wrong attachments to wrong e-mail addresses e.g. in reply-all and thus security often prevents it's use - whether it's good intent or not people can debate but it's just the reality :)
Typically organisations respond when something goes wrong they try to prevent it with a hammer and here we go we may have bodies sending links that can be downloaded.
It would be interesting to do automatic scraping from a Sharepoint that seems typical at public enterprise setting.
The text was updated successfully, but these errors were encountered:
Often govt people use Microsoft Office 356 exclusively and some organisations disable sending attachments alltogether.
It's pretty inefficient sending attachment (Base64 is another encoding layer and adds bytes) and organisations have reasons not to enable sending random files off filesystem and to only allow editing files in the cloud.
There has been multiple published incidents where e.g. govt employees send wrong attachments to wrong e-mail addresses e.g. in reply-all and thus security often prevents it's use - whether it's good intent or not people can debate but it's just the reality :)
Typically organisations respond when something goes wrong they try to prevent it with a hammer and here we go we may have bodies sending links that can be downloaded.
It would be interesting to do automatic scraping from a Sharepoint that seems typical at public enterprise setting.
The text was updated successfully, but these errors were encountered: