Request Body

The request does not have a request body.

Response Syntax

HTTP/1.1 200 messageContent

Response Elements

If the action is successful, the service sends back an HTTP 200 response.

The response returns the following as the HTTP body.

messageContent (p. 187)

The raw content of the email message, in MIME format.

Errors

For information about the errors that are common to all actions, see Common Errors (p. 228).

ResourceNotFoundException

The requested email message is not found.

HTTP Status Code: 404

GetRawMessageContent

Examples

In the following examples, the Authorization header contents (AUTHPARAMS) must be replaced with an AWS Signature Version 4 signature. For more information about creating these signatures, see Signature Version 4 Signing Process in the AWS General Reference.

You only need to learn how to sign HTTP requests if you intend to manually create them. When you use the AWS Command Line Interface (AWS CLI) or one of the AWS SDKs to make requests to AWS, these tools automatically sign the requests for you with the access key that you specify when you conﬁgure the tools. When you use these tools, you don't need to learn how to sign requests yourself.

Example

This example gets the raw content of an in-transit email message and sends it to a text ﬁle named "test".

Sample Request

GET /messages/a1b2cd34-ef5g-6h7j-kl8m-npq9012345rs HTTP/1.1 Host: workmailmessageflow.us-east-1.amazonaws.com

Accept-Encoding: identity

User-Agent: aws-cli/1.16.273 Python/3.6.0 Windows/10 botocore/1.13.9 X-Amz-Date: 20191107T195012Z

Authorization: AUTHPARAMS

Sample Response

HTTP/1.1 200 OK

Cache-Control: no-cache

Content-Type: application/json Date: Thu, 07 Nov 2019 19:50:12 GMT

x-amzn-RequestId: ea71f214-79c5-4f89-9d4e-1ab4c43ae0df Content-Length: 1344

Connection: keep-alive Subject: Hello World

From: =?UTF-8?Q?marymajor_marymajor?= <[email protected]>

To: =?UTF-8?Q?mateojackson=40example=2Enet?= <[email protected]>

Date: Thu, 7 Nov 2019 19:22:46 +0000 Mime-Version: 1.0

Content-Type: multipart/alternative;

boundary="=_EXAMPLE+"

References: <[email protected]>

X-Priority: 3 (Normal) X-Mailer: Amazon WorkMail Thread-Index: EXAMPLE Thread-Topic: Hello World

Message-Id: <[email protected]>

This is a multi-part message in MIME format. Your mail reader does not understand MIME message format.

--=_EXAMPLE+

Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit

hello world

--=_EXAMPLE+

Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

GetRawMessageContent

<!DOCTYPE HTML><html>

<head>

<title>testing</title>

</head>

<body>

<p style=3D"margin: 0px; font-family: Arial, Tahoma, Helvetica, sans-serif; font-size:

small;">hello world</p>

</body>

</html>

--=_EXAMPLE+--See Also

For more information about using this API in one of the language-speciﬁc AWS SDKs, see the following:

• AWS Command Line Interface

• AWS SDK for .NET

• AWS SDK for C++

• AWS SDK for Go

• AWS SDK for Java V2

• AWS SDK for JavaScript

• AWS SDK for PHP V3

• AWS SDK for Python

• AWS SDK for Ruby V3

PutRawMessageContent

Service: Amazon WorkMail Message Flow

Updates the raw content of an in-transit email message, in MIME format.

This example describes how to update in-transit email message. For more information and examples for using this API, see Updating message content with AWS Lambda.

NoteUpdates to an in-transit message only appear when you call PutRawMessageContent from an AWS Lambda function conﬁgured with a synchronous Run Lambda rule. If you call PutRawMessageContent on a delivered or sent message, the message remains unchanged, even though GetRawMessageContent returns an updated message.

Request Syntax

POST /messages/messageId HTTP/1.1 Content-type: application/json

URI Request Parameters

The request uses the following URI parameters.

messageId (p. 190)

The identiﬁer of the email message being updated.

Length Constraints: Minimum length of 1. Maximum length of 120.

Pattern: [a-z0-9\-]*

Required: Yes

The request accepts the following data in JSON format.

content (p. 190)

Describes the raw message content of the updated email message.

Type: RawMessageContent (p. 224) object Required: Yes

Response Syntax

HTTP/1.1 200

PutRawMessageContent

Response Elements

If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.

Errors

For information about the errors that are common to all actions, see Common Errors (p. 228).

InvalidContentLocation

WorkMail could not access the updated email content. Possible reasons:

• You made the request in a region other than your S3 bucket region.

• The S3 bucket owner is not the same as the calling AWS account.

• You have an incomplete or missing S3 bucket policy. For more information about policies, see Updating message content with AWS Lambda in the WorkMail Administrator Guide.

HTTP Status Code: 400 MessageFrozen

The requested email is not eligible for update. This is usually the case for a redirected email.

HTTP Status Code: 400 MessageRejected

The requested email could not be updated due to an error in the MIME content. Check the error message for more information about what caused the error.

HTTP Status Code: 400 ResourceNotFoundException

The requested email message is not found.

HTTP Status Code: 404

Examples

Example

This example illustrates one usage of PutRawMessageContent.

Sample Request

POST /messages/4e87856b-f02f-39d5-a029-9e39ace5b6f1 HTTP/1.1 Host: workmailmessageflow.us-east-1.amazonaws.com

Accept-Encoding: gzip, deflate

User-Agent: aws-cli/1.16.230 Python/3.7.5 Darwin/18.7.0 botocore/1.12.220 X-Amz-Date: 20210127T151129Z

PutRawMessageContent

Authorization: AUTHPARAMS Content-Length: 81

Connection: close

{"content": {"s3Reference": {"bucket": "My-S3-Bucket", "key": "My-S3-Object-Key"}}}

Sample Response

HTTP/1.1 200 OK

Cache-Control: no-cache

Content-Type: application/json Date: Wed, 27 Jan 2021 15:11:30 GMT

x-amzn-RequestId: ddd7de94-a4eb-4af8-8c3f-1d16cf98b458 Content-Length: 2

Connection: Close {}