![google mail convert email to group email google mail convert email to group email](https://www.nimble.com/blog/wp-content/uploads/2019/03/VRSN_CompanyBrandedEmail_BlogImage8_201712-670x446-2.png)
![google mail convert email to group email google mail convert email to group email](http://4.bp.blogspot.com/_gOKMpkNWO64/S4KFmIhjX8I/AAAAAAAAB0I/uRF2NmpgI4w/s640/Carnival+2010+612.b.jpg)
The migrated email's sender is and the email is migrated to the archive of the group: This is an example email message in RFC 822 text format that was migrated into the archive of The is this example's Message-ID. The Content-Length is limited to 25MB which includes the message's meta data, body, and any attachments: POST Content-Type: message/rfc822Ĭontent-Length: number of bytes in the emailĪuthorization: Bearer Auth token The email's meta data, body, and any attachments This example migrates email messages to the archive. POST group email address/archive?uploadType=media Note: The documentation assumes you understand and have successfully completed the prerequisite tasks. The group email address is the requested destination of the migrated email message. Include the Authorization header as described in Authorizing requests. To migrate an email message to a group's archive, use the following POST HTTP request. Migrate an email message to Google Groups Do not use the API if data location is required for your account. The API does not support data location policies requiring data to be stored in specific geographic or political boundaries for contractual reasons.The API project's maximum QPS is 10, and the maximum number of migration requests per day is 500,000. But the API does not support parallel message insertions into the same group archive. The API supports parallel requests for email insertions into different group archives.The response is returned in the JSON data format. Confirm the email message's To:, From:, and Date: fields are properly formed. Use the Content-type: message/rfc822 header. Before migration, the email message format must be in the RFC 822 standard definition.If the email's sender has the same domain as the target group, confirm the email sender exists before migrating the email message to the target group's archive.įor more information about listing groups and users, see the Directory API.Confirm that the target group exists and the group's email is accurate before migrating an email message to that group's archive.
Google mail convert email to group email how to#
For more information about how to identify and fix these, see the Directory API, the Groups Settings API, and Ways to create groups. For migration purposes, the API returns an error if a group is suspended, has not been created, or has read-only access.For specific information for custom application migration to Google Workspace, see the Google Workspace migration tools product matrix. All group members who have access to the group's archive can view the migrated messages, but the emails are not delivered to individual group members.For information about migrating or syncing emails from a specific custom application to Gmail, see Gmail API. The API is for the migration of shared emails to Google Groups.When managing a migration, it is important to note: The media upload feature allows the API to store group email messages in the cloud and make it available to the server. The Groups Migration API manages the migration of shared emails from public folders and distribution lists to a group's discussion archive.