Skip to content

Commit

Permalink
Fix list in generated doc (#1434)
Browse files Browse the repository at this point in the history
  • Loading branch information
jderusse authored Jun 12, 2023
1 parent af0fdd7 commit 26de916
Show file tree
Hide file tree
Showing 4 changed files with 0 additions and 16 deletions.
2 changes: 0 additions & 2 deletions src/SesClient.php
Original file line number Diff line number Diff line change
Expand Up @@ -29,11 +29,9 @@ class SesClient extends AbstractApi
*
* - **Simple** – A standard email message. When you create this type of message, you specify the sender, the
* recipient, and the message body, and Amazon SES assembles the message for you.
* -
* - **Raw** – A raw, MIME-formatted email message. When you send this type of email, you have to specify all of the
* message headers, as well as the message body. You can use this message type to send messages that contain
* attachments. The message that you specify has to be a valid MIME message.
* -
* - **Templated** – A message that contains personalization tags. When you send this type of email, Amazon SES API v2
* automatically replaces the tags with values that you specify.
*
Expand Down
6 changes: 0 additions & 6 deletions src/ValueObject/EmailContent.php
Original file line number Diff line number Diff line change
Expand Up @@ -19,18 +19,12 @@ final class EmailContent
* The raw email message. The message has to meet the following criteria:.
*
* - The message has to contain a header and a body, separated by one blank line.
* -
* - All of the required header fields must be present in the message.
* -
* - Each part of a multipart MIME message must be formatted properly.
* -
* - If you include attachments, they must be in a file format that the Amazon SES API v2 supports.
* -
* - The entire message must be Base64 encoded.
* -
* - If any of the MIME parts in your message contain content that is outside of the 7-bit ASCII character range, you
* should encode that content to ensure that recipients' email clients render the message properly.
* -
* - The length of any single line of text in the message can't exceed 1,000 characters. This restriction is defined in
* RFC 5321 [^1].
*
Expand Down
2 changes: 0 additions & 2 deletions src/ValueObject/MessageTag.php
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,6 @@ final class MessageTag
* The name of the message tag. The message tag name has to meet the following criteria:.
*
* - It can only contain ASCII letters (a–z, A–Z), numbers (0–9), underscores (_), or dashes (-).
* -
* - It can contain no more than 256 characters.
*/
private $name;
Expand All @@ -23,7 +22,6 @@ final class MessageTag
* The value of the message tag. The message tag value has to meet the following criteria:.
*
* - It can only contain ASCII letters (a–z, A–Z), numbers (0–9), underscores (_), or dashes (-).
* -
* - It can contain no more than 256 characters.
*/
private $value;
Expand Down
6 changes: 0 additions & 6 deletions src/ValueObject/RawMessage.php
Original file line number Diff line number Diff line change
Expand Up @@ -13,18 +13,12 @@ final class RawMessage
* The raw email message. The message has to meet the following criteria:.
*
* - The message has to contain a header and a body, separated by one blank line.
* -
* - All of the required header fields must be present in the message.
* -
* - Each part of a multipart MIME message must be formatted properly.
* -
* - Attachments must be in a file format that the Amazon SES supports.
* -
* - The entire message must be Base64 encoded.
* -
* - If any of the MIME parts in your message contain content that is outside of the 7-bit ASCII character range, you
* should encode that content to ensure that recipients' email clients render the message properly.
* -
* - The length of any single line of text in the message can't exceed 1,000 characters. This restriction is defined in
* RFC 5321 [^1].
*
Expand Down

0 comments on commit 26de916

Please sign in to comment.