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.
ByteBuffers are stateful. Calling their
get methods changes their
position. We recommend
java.nio.ByteBuffer#asReadOnlyBuffer() to create a read-only view of the buffer with an independent
position, and calling
get methods on this rather than directly on the returned
Doing so will ensure that anyone else using the
ByteBuffer will not be affected by changes to the