I would like to detect emails that arrive in the inbox (vs emails that land in the spam folder) sent using Amazon SES.
I know that I can set up notifications for delivered emails, bounced email, and emails with complaints.
When you get a delivery notification, does it mean that the email landed in the inbox and not in the spam folder, or does it only mean that the email didn't bounce and that the email provider didn't reject the email?
And if it only means that the email didn't bounce, is there a way to know what emails actually land in the inbox vs automatically landing in the spam folder of the user?
There is no way to know this information:
This is not specific to SES, but all email in general.
Each email reading application will handle SPAM in different way.
For example, in GMAIL, items in SPAM folder will not render or download external resources.
You will not be able to detect if a message has never been viewed and in an Inbox -vs- Spam folder.
Related
I'd like to know what it means when a Microsoft Graph application has the Mail.Read permission that says Read mail in all mailboxes.
Does this mean that such an application can read all mailboxes of every user in the entire company or what all mailboxes are they?
The admins won't grant me this permission as they justifiably think it might be a god-mode. Is it?
First, let's see the description here:
Microsoft Graph lets your app get authorized access to a user's
Outlook mail data in a personal or organization account. With the
appropriate delegated or application mail permissions, your app can
access the mail data of the signed-in user or any user in a tenant.
Let's see the graph api which requiring this api permission:
Get the messages in the signed-in user's mailbox (including the
Deleted Items and Clutter folders).
But if the Mail.Read you mentioned is Application Mail.ReadBasic.All, Mail.Read, Mail.ReadWrite, then
can get messages in another user's mail folder
I'm afraid it is really the god-mode you said. But please note, it doesn't mean , you invite my outlook email address into your company's tenant then you can use this api to read the emails in my outlook email address.
It means that the application has the ability to read email messages in all mailboxes of all users within the organization that has granted the application access to their mailbox. This includes access to the contents of the messages, including subject, body, sender, recipient, and other properties
I'm trying to set up an autoresponder in Gmail that is not a typical vacation responder that's sent via a separate email. My autoresponder should respond directly to the email that came to the inbox.
There used to be a way with IFTTT, but they've since removed any Gmail triggers.
The reason I am looking for this is that I have a business on Yelp and when customers request quotes on Yelp, they get sent to my email. I can either open the Yelp app (or website) and respond there or respond directly to that email from my email address (it doesn't work to send a separate email to that Yelp email).
Has anyone ever done anything like this before? Alternatively, I was thinking of going the somewhat more complicated route and have an "incoming email" trigger in Zapier and then have something scrape the email for links and set up an automation to respond with my standard response, but that seemed like a lot...
I've solved it with Zapier! Basically, in Zapier you need to set up a Gmail response and respond to the same thread ID as the original email. This will work for any "respond to this email to respond to the client" messages from pages like Yelp for Business.
I'm new to develop VSTO. I have a Java schedule job to send email daily by SMTP.
If email is bounce back, my outlook would receive bounce back email.
Here is the question, since I used java program to send email, there is no copy in "sent items" folder. How can I trace back the original email Body from this bounce back email?
Thank you.
You can use the data from headers like Message-ID, To, From, Subject, Recieved property values for identifying the original item in Outlook.
We have some issues related with AWS SES bounce and complain emails,
and we send send emails on these conditions. these conditions are as follows:
1) When new user registered, 2) When user forget his/her password and 3) When he/she purchased any video from ourplatform. To send email we have implemented AWS SES mail service and successfully managed to send email from AWS SES. But here I have some doubt to handle Bounced and Complaint email. According to this post on stackoverflow:
Handle hard bounces / complaints or just stick to suppression list?
We have managed list of emails in our database, when new user 1st time registered into our platform and getting notification for bounced and complaint notifications from AWS SNS. But here are some case I want to discuss with you:
Bounce: When user 1st time registered into our platform and his/her email does not exist i.e. jm123#gmail.com in that case we save his/her email into our bounced email list, but when 2nd time he creates a email with the same email id ( jim123#gmail.com ) and want to register with our platform again then how we will remove that email from list because we have already black listed that email in our platform.
Complaint: In 2nd case when user accidentally put our platforms email as spam when we send him/her a email and getting complaint notifications for that email and for complaint emails we have managed list of complaint emails and saved that email in this list so that same user can not get email from the next time but after some time that user white list us from spam and wants our email notifications.
Note: Is this necessary to handle all bounced or complaint email into our database because randomness of emails are infinite and for all random emails we have to handle into our database. and before send emails to any new registered user, 1st we have to process our bounced and complaint emails list then we will decide the user is eligible to receive our email or not.
Sorry for my bad English.
The StackOverflow Question you linked to covers this in the Answer.
Yes, you should maintain your own database table of at least some of the permanent bounced emails, something like:
record ID (auto increment), email address, bounce type: invalid mailbox | user complaint | rejected for content | rejected for spam blacklist
Bounce: "when 2nd time he creates a email with the same email id ...
how we will remove that email from list because we have already black
listed that email in our platform?"
When the user tries to add the email, you query the email address in your table, you see the type is "invalid mailbox", and then reject it as invalid. You could possibly also log the IP address to catch spammers trying to create fake accounts.
Complaint: "... but after some time that user white list us from spam
and wants our email notifications."
When the user tries to add the email, you query the email address in your table, you see the type is "user complaint", and maybe ask them "are you sure?" before adding them back to your mail list. You change the type of the email in your database to something like "user confirmed OK to send"
You could also just add one extra field to your existing mailing list table to hold the bounce type, with the default type being 0 / OK / not bounced. Then when sending email you skip sending emails where the type is not 0 / OK.
But in hard bounced if user will have valid email address after put
his email address in table and he/she wants our subscription then how
we could handle
You could allow them to re-add the address and set the type back to 0, but this might be a fake address like "fake#fakefake.com."
If you want to let them do this you could have a second field "times bounce was cleared" and add +1 each time the address is set back to 0 / OK / mail allowed. If this counter reaches 3-5 you never let them add the email again. They must use a different email.
what about soft bounce
"Transient" (soft) bounces should be ignored. SES will try again later and if it still fails then you will get a hard bounce.
I've built a newsletter system which tracks:
Openings
Link clicks
Unsubscriptions
However, I need to find a way of tracking which newsletter emails 'bounced back'.
Has anyone done this before and whats the best way of doing it?
When sending the mail via SMTP you supply the FROM command which is sometimes referred to as the 'Sender' or 'Envelope Sender'. This is separate from the From: header in the email itself. What you want to do is to create a 'bounced' mailbox and set that as the 'Sender' for the email. If there is a bounce, then most mail servers will send a (NDR) notification back to this sender.
Then you need to periodically check this mailbox for NDR's and parse them for the original recipient and if it was a hard or soft bounce. There are various libraries that can do this for you such as ListNanny