Status Update
No update yet.
Comments
bl...@google.com
Metadata
- Summary: The Directory API's users.list method is inconsistently returning a nextPageToken when using the query parameter, and the starts with operator is not working for the orgDepartment field.
- Tags:
directory-api users-list next-page-token query-parameter org-department starts-with-operator
Additional resources:
https://issuetracker.google.com/savedsearches/566232?hl=it https://developers.google.com/drive/api/reference/rest/v3/files/list https://developers.google.com/admin-sdk/directory/v1/.../manage-users https://developers.google.com/admin-sdk/directory/reference/rest/v1/.../list https://stackoverflow.com/.../want-admindirectory-users-list-more-then-500... https://stackoverflow.com/.../drive-list-files-doesnt-have-nextpagetoken-wh... https://stackoverflow.com/.../how-to-resolve-the-missing-information-probl...
Description
I am looking to programmatically access and manage the blocked sender rules within Gmail settings under Google Workspace Admin Control. This includes the ability to:
Access: Retrieve the current list of blocked senders. Add: Add new email addresses or domains to the blocked sender list. Update: Modify existing entries in the blocked sender list. Delete: Remove email addresses or domains from the blocked sender list. Use Case: As an administrator, I need to automate the management of blocked senders to ensure our email system remains secure and free from unwanted emails. This will streamline the process of maintaining and updating the blocked sender list, reducing manual intervention, and enhancing overall efficiency.
Expected Outcome: Provide API endpoints or scripts that allow the following actions:
Retrieve the current list of blocked senders. Add a new sender to the blocked list. Update an existing sender’s details in the blocked list. Remove a sender from the blocked list. Priority: High