/** * Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved. * SPDX-License-Identifier: Apache-2.0. */ #pragma once #include #include #include #include namespace Aws { namespace Utils { namespace Xml { class XmlNode; } // namespace Xml } // namespace Utils namespace SES { namespace Model { /** *

Represents the raw data of the message.

See Also:

AWS * API Reference

*/ class RawMessage { public: AWS_SES_API RawMessage(); AWS_SES_API RawMessage(const Aws::Utils::Xml::XmlNode& xmlNode); AWS_SES_API RawMessage& operator=(const Aws::Utils::Xml::XmlNode& xmlNode); AWS_SES_API void OutputToStream(Aws::OStream& ostream, const char* location, unsigned index, const char* locationValue) const; AWS_SES_API void OutputToStream(Aws::OStream& oStream, const char* location) const; /** *

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 for SendRawEmail.

Do not include * these X-headers in the DKIM signature, because they are removed by Amazon SES * before sending the email.

For more information, go to the Amazon * SES Developer Guide.

*/ inline const Aws::Utils::ByteBuffer& GetData() const{ return m_data; } /** *

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 for SendRawEmail.

Do not include * these X-headers in the DKIM signature, because they are removed by Amazon SES * before sending the email.

For more information, go to the Amazon * SES Developer Guide.

*/ inline bool DataHasBeenSet() const { return m_dataHasBeenSet; } /** *

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 for SendRawEmail.

Do not include * these X-headers in the DKIM signature, because they are removed by Amazon SES * before sending the email.

For more information, go to the Amazon * SES Developer Guide.

*/ inline void SetData(const Aws::Utils::ByteBuffer& value) { m_dataHasBeenSet = true; m_data = value; } /** *

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 for SendRawEmail.

Do not include * these X-headers in the DKIM signature, because they are removed by Amazon SES * before sending the email.

For more information, go to the Amazon * SES Developer Guide.

*/ inline void SetData(Aws::Utils::ByteBuffer&& value) { m_dataHasBeenSet = true; m_data = std::move(value); } /** *

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 for SendRawEmail.

Do not include * these X-headers in the DKIM signature, because they are removed by Amazon SES * before sending the email.

For more information, go to the Amazon * SES Developer Guide.

*/ inline RawMessage& WithData(const Aws::Utils::ByteBuffer& value) { SetData(value); return *this;} /** *

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 for SendRawEmail.

Do not include * these X-headers in the DKIM signature, because they are removed by Amazon SES * before sending the email.

For more information, go to the Amazon * SES Developer Guide.

*/ inline RawMessage& WithData(Aws::Utils::ByteBuffer&& value) { SetData(std::move(value)); return *this;} private: Aws::Utils::ByteBuffer m_data; bool m_dataHasBeenSet = false; }; } // namespace Model } // namespace SES } // namespace Aws