Module aws_sdk_ses::types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that Amazon Simple Email Service can respond with.

Structs

• AddHeaderAction

  When included in a receipt rule, this action adds a header to the received email.

• Body

  Represents the body of the message. You can specify text, HTML, or both. If you use both, then the message should display correctly in the widest variety of email clients.

• BounceAction

  When included in a receipt rule, this action rejects the received email by returning a bounce response to the sender and, optionally, publishes a notification to Amazon Simple Notification Service (Amazon SNS).

• BouncedRecipientInfo

  Recipient-related information to include in the Delivery Status Notification (DSN) when an email that Amazon SES receives on your behalf bounces.

• BulkEmailDestination

  An array that contains one or more Destinations, as well as the tags and replacement data associated with each of those Destinations.

• BulkEmailDestinationStatus

  An object that contains the response from the SendBulkTemplatedEmail operation.

• CloudWatchDestination

  Contains information associated with an Amazon CloudWatch event destination to which email sending events are published.

• CloudWatchDimensionConfiguration

  Contains the dimension configuration to use when you publish email sending events to Amazon CloudWatch.

• ConfigurationSet

  The name of the configuration set.

• Content

  Represents textual data, plus an optional character set specification.

• CustomVerificationEmailTemplate

  Contains information about a custom verification email template.

• DeliveryOptions

  Specifies whether messages that use the configuration set are required to use Transport Layer Security (TLS).

• Destination

  Represents the destination of the message, consisting of To:, CC:, and BCC: fields.

• EventDestination

  Contains information about an event destination.

• ExtensionField

  Additional X-headers to include in the Delivery Status Notification (DSN) when an email that Amazon SES receives on your behalf bounces.

• IdentityDkimAttributes

  Represents the DKIM attributes of a verified email address or a domain.

• IdentityMailFromDomainAttributes

  Represents the custom MAIL FROM domain attributes of a verified identity (email address or domain).

• IdentityNotificationAttributes

  Represents the notification attributes of an identity, including whether an identity has Amazon Simple Notification Service (Amazon SNS) topics set for bounce, complaint, and/or delivery notifications, and whether feedback forwarding is enabled for bounce and complaint notifications.

• IdentityVerificationAttributes

  Represents the verification attributes of a single identity.

• KinesisFirehoseDestination

  Contains the delivery stream ARN and the IAM role ARN associated with an Amazon Kinesis Firehose event destination.

• LambdaAction

  When included in a receipt rule, this action calls an Amazon Web Services Lambda function and, optionally, publishes a notification to Amazon Simple Notification Service (Amazon SNS).

• Message

  Represents the message to be sent, composed of a subject and a body.

• MessageDsn

  Message-related information to include in the Delivery Status Notification (DSN) when an email that Amazon SES receives on your behalf bounces.

• MessageTag

  Contains the name and value of a tag that you can provide to SendEmail or SendRawEmail to apply to an email.

• RawMessage

  Represents the raw data of the message.

• ReceiptAction

  An action that Amazon SES can take when it receives an email on behalf of one or more email addresses or domains that you own. An instance of this data type can represent only one action.

• ReceiptFilter

  A receipt IP address filter enables you to specify whether to accept or reject mail originating from an IP address or range of IP addresses.

• ReceiptIpFilter

  A receipt IP address filter enables you to specify whether to accept or reject mail originating from an IP address or range of IP addresses.

• ReceiptRule

  Receipt rules enable you to specify which actions Amazon SES should take when it receives mail on behalf of one or more email addresses or domains that you own.

• ReceiptRuleSetMetadata

  Information about a receipt rule set.

• RecipientDsnFields

  Recipient-related information to include in the Delivery Status Notification (DSN) when an email that Amazon SES receives on your behalf bounces.

• ReputationOptions

  Contains information about the reputation settings for a configuration set.

• S3Action

  When included in a receipt rule, this action saves the received message to an Amazon Simple Storage Service (Amazon S3) bucket and, optionally, publishes a notification to Amazon Simple Notification Service (Amazon SNS).

• SendDataPoint

  Represents sending statistics data. Each SendDataPoint contains statistics for a 15-minute period of sending activity.

• SnsAction

  When included in a receipt rule, this action publishes a notification to Amazon Simple Notification Service (Amazon SNS). This action includes a complete copy of the email content in the Amazon SNS notifications. Amazon SNS notifications for all other actions simply provide information about the email. They do not include the email content itself.

• SnsDestination

  Contains the topic ARN associated with an Amazon Simple Notification Service (Amazon SNS) event destination.

• StopAction

  When included in a receipt rule, this action terminates the evaluation of the receipt rule set and, optionally, publishes a notification to Amazon Simple Notification Service (Amazon SNS).

• Template

  The content of the email, composed of a subject line and either an HTML part or a text-only part.

• TemplateMetadata

  Contains information about an email template.

• TrackingOptions

  A domain that is used to redirect email recipients to an Amazon SES-operated domain. This domain captures open and click events generated by Amazon SES emails.

• WorkmailAction

  When included in a receipt rule, this action calls Amazon WorkMail and, optionally, publishes a notification to Amazon Simple Notification Service (Amazon SNS). It usually isn't necessary to set this up manually, because Amazon WorkMail adds the rule automatically during its setup procedure.

Enums

• BehaviorOnMxFailure
  When writing a match expression against BehaviorOnMxFailure, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• BounceType
  When writing a match expression against BounceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• BulkEmailStatus
  When writing a match expression against BulkEmailStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ConfigurationSetAttribute
  When writing a match expression against ConfigurationSetAttribute, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• CustomMailFromStatus
  When writing a match expression against CustomMailFromStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DimensionValueSource
  When writing a match expression against DimensionValueSource, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DsnAction
  When writing a match expression against DsnAction, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• EventType
  When writing a match expression against EventType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• IdentityType
  When writing a match expression against IdentityType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• InvocationType
  When writing a match expression against InvocationType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• NotificationType
  When writing a match expression against NotificationType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ReceiptFilterPolicy
  When writing a match expression against ReceiptFilterPolicy, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SnsActionEncoding
  When writing a match expression against SnsActionEncoding, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• StopScope
  When writing a match expression against StopScope, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• TlsPolicy
  When writing a match expression against TlsPolicy, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• VerificationStatus
  When writing a match expression against VerificationStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.