Here is a short video showing the verification process. Verification is done via the SES console. Email Address verification - AWS SES will allow you to send from any email address once you verify that you own it.This video will give simple instructions on how to generate your access key and secret key and the proper permissions needed. The user that the keys are generated for also needs to have the proper permissions to send with SES. These keys are generated per user in your AWS account. Access Keys and Secret Keys - These are the required parameters for the EmailConnectAmazon function.Low cost, only pay what you use - there are no upfront costs and no minimum commitments.AWS allows for you to request sending limits that will fit your needs. High sending limits - Most email providers will impose pretty low sending limits on the amount of emails you can send in a day and how fast you can send them.High Deliverability - Emails sent using SES are sent from AWS IP addresses that maintain good reputation among mailbox providers which means it is less likely your emails will be marked as spam.Also, you do not need to know the requirements for connecting (username, password, ssl/tls requirements, host name and required ports, etc.) SES communicates over HTTPS and uses the standard port 443. Less coordination with IT - There is no SMTP server required so there is no need to contact your IT department to open sending ports in a firewall or other IT related tasks normally associated with setting up and sending with an SMTP server.Sending emails with AWS SES is a great way to send emails. The Email plugin is capable of connecting to Amazon Web Services Simple Email Service by using the function EmailConnectAmazon. Sending with Amazon Web Services Simple Email Service For the countries and regions that support sender IDs, see Supported Regions and Countries. phone numbers will not display the sender ID. However, support for sender IDs varies by country and/or region. In the AWS SNS console you can add an up to 11 character alphanumeric sender ID that will appear in your messages. Messages after 100 sent and any non-US numbers incur a per message charge that can be found here. The first 100 messages sent to US numbers are free. This functionality does not currently support 2-way SMS other than when recipients opt out. If a recipient decides to opt back in, you can select their number and click "opt in" so they can receive messages from you again. This will show a list of numbers that have opted out from receiving SMS messages. This list can be managed in your AWS account in the SNS section at Text messaging (SMS)->View opted-out phone numbers. By replying "stop" to the message sent, AWS will put their number on the opt-out list and they will no longer receive any messages from you even if they are sent. Some carriers may break long messages into separate, shorter messages.ĪWS also has a mechanism for recipients to opt out of receiving messages from you. Your function call should look something like this:ĮmailSMSSend("AccessKeyHere" "SecretKeyHere" "17702349293" "Your Message Here"] If you want to send to multiple numbers, separate them with commas like so "17702349293,16781234567." The plugin will strip out any other characters besides 0-9 so phone numbers could also be put in the format +1(770)234-9293. For example the country code for the United States is +1 so any number that originates in the US needs to have "1" in front of it like so: 17702349293. Recipient numbers need to have the phone number's country code in front of it. Directions for creating these keys can be found here. The function requires that you have an AWS account and have generated an access key and secret key. The Email plugin leverages Amazon AWS / SNS to send SMS messages world wide. 6.7 Saving attachments to a container field.6.6 Fetch unread messages and create new records for each.6.2 Lower the chances of your email being identified as spam.6.1 Overview: Adding HTML with Inline Attachments.5.7 Office365 Authentication unsuccessful.5.4 Downloaded emails are not decoded properly.5.3 EmailConnectX method error: "PKIX path building failed".5.2 EmailSend error: "Invalid Addresses".4.2 Office 365 OAuth Worflow: Automated Example.4.1 Office 365 OAuth Workflow: Manual Example.3.2 Google OAuth Worflow: Automated Example.3.1 Google OAuth Workflow: Manual Example.2 Sending with Amazon Web Services Simple Email Service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |