AWS WorkMail API to get a message list or the last email - amazon-workmail

I need to write the e2e test for the next scenario:
Send invitation email with enrollment link to a specific mailbox
Find this email from the mailbox, parse the email body in order to get the enrollment link to follow the link end complete the enrollment process
In order to get the email, I want to use Amazon WorkMail, I want to use API to get a message list or the last email
for example:
const email = await AWS.SomeMailLibrary.fetchLatestEmail(emailAddress)
I haven't found yet if AWS WorkMail had API I need, Would you mind helping me with it?
thanks

Related

How can I set up a noreply#mydomain.com email in SES

I want to be able to send messages using SES. My sender's email is noreply#mydomain.com . The domain and sender's email are verified identities in SES. Now whenever my app sends an email, I don't want the receiver to be able to reply to the email I sent. How can I configure the sender email so that it never receives an email as reply from the user?
Ok so this is going to sound simple but follow this guide. There is one step though I struggled with which I got lost for hours on. Guide
Make sure when you're creating the MX record, you need to add the inbound SMTP as well as the normal email smtp.
10 inbound-smtp.us-east-1.amazonaws.com
11 email-smtp.us-east-1.amazonaws.com
You need to add both in order to receive email as well. Then, your rule sets will work as intended.

AWS SES Not Delivering

I am currently using AWS SES to send emails to my users. However, it appears that my users who use outlook / Microsoft's Business Email System are not receiving my emails. SES also tells me that I have no bounces too.
The user's email has {name}.onmicrosoft.com on it.
How can I go about resolving this?
EDIT: Found out that the key phrase "password" is a root cause for the email being blocked and not showing up at all. Not sure how to combat this as I am sending a password reset email.
Thanks

AWS SES verified emails

Trying to understand something thats not clear from AWS SES emails.
I have a simple emailer on my website that I have setup using nodemailer.
It has 3 fields
Name: name of user filling out form
email: email address of user filling out email.
Description: description filled out by user.
I'm seeing in AWS docs that I need to verify on their console the users email.
You can only send mail from verified email addresses and domains.
Note: This restriction applies even when your account isn't in the
sandbox.
This could be any number of different user email address how would I be able to verify them all I wouldn't know them.
What am I not getting here. I have verified the To: email which will always be the same as its coming to my domain email.
You'll want to send from an email address under your control (SES enforces this on a technical level, but spam filters tend to de facto enforce this everywhere due to things like SPF records) with a Reply-To header of the email address submitting the form.

How to trigger EMail messages in using the engagement plan

I am using ECM 2.1 for sending out emails.
I want to know how can I added the triggered emails to all the recipients who have opened the email and who are productive users on the email sent.
Can I modify the existing plan and add this feature.
By Using tokenized emails
An action that can be executed from within a Sitecore Engagement Plan is to send an email to a static or to the visitors email address.
follow this link:
http://www.newguid.net/sitecore/2013/sending-tokenized-emails-from-a-sitecore-engagement-plan/

Can't send email to myself

I'm using opencart 1.5.1.3. For some reason I can't send an email to the same account I am sending from. For example, I can't receive the notification email when an order is placed. The email reaches the customer OK and if I specify additional email address to send the mail to, they receive the email OK, the email configured as the store email addres doesn't receive the email. I'm using the 'mail' option to send email.
The email is hosted at google apps. Please help
some web hosting prevent self-to-self email for safety reason.
maybe it is your hosting provider block this mail.