The raw data of the message. This data needs to base64-encoded if you are accessing Amazon SES directly through
the HTTPS interface. If you are accessing Amazon SES using an AWS SDK, the SDK takes care of the base 64-encoding
for you. In all cases, the client must ensure that the message format complies with Internet email standards
regarding email header fields, MIME types, and MIME encoding.
The To:, CC:, and BCC: headers in the raw message can contain a group list.
If you are using
SendRawEmail with sending authorization, you can include X-headers in the raw
message to specify the "Source," "From," and "Return-Path" addresses. For more information, see the documentation
Do not include these X-headers in the DKIM signature, because they are removed by Amazon SES before sending the
For more information, go to the Amazon SES Developer Guide.
The AWS SDK for Java performs a Base64 encoding on this field before sending this request to the AWS service.
Users of the SDK should not perform Base64 encoding on this field.
Warning: ByteBuffers returned by the SDK are mutable. Changes to the content or position of the byte buffer will
be seen by all objects that have a reference to this object. It is recommended to call ByteBuffer.duplicate() or
ByteBuffer.asReadOnlyBuffer() before using or reading from the buffer. This behavior will be changed in a future
major version of the SDK.