I'm working on a system that delivers bulk emails.
My question is how do I receive a copy of Non-Delivery notification to another email address?
The reason I need to do this , is so that I can programmatically create my own black lists.
Amazon SES somehow manges to do this, but how?
Any help would greatly be appreciated.
Thanks,
Jamie
It depends which MTA you are using (e.g. sendmail, qmail, postfix, etc), but most MTA's will log undeliverables, so you can get the non-deliverable addresses from the logs. Also, most MTA's will send a non-deliverable notice to back to the envelope sender of the original message.
Related
hopefully this is a simple question.
I have a list of emails and I want to identify those sending automatic replies. But Outlook does not show which addresses these are if there are more than 3. Any idea how to get them all to display?
Thanks! Mike
Screenshot of Outlook message
Use GetMailTips EWS operation - see https://msdn.microsoft.com/en-us/library/office/dd877060(v=exchg.150).aspx
Hey all thanks in advance for the look.
We are attempting to develop a drip campaign email platform. For each "drip"we need to detect if the recipient replied to the email.
If so we would like discontinue the following drips.
For this we need some sort of reply detection but everything I have seen about tracking email metrics online is related to bounce rate and open rate.
Not much available on reply rate in terms of how to build such functionality.
Preferably we would like to do this on Amazon SES but if there is no such option we are willing to look at other smtp providers.
Perhaps there is some unique header we can save with the outbound email, then check against all the inbox emails. I guess this relates to how do email clients know to thread emails - perhaps it's a similar process.
Yes, you can fetch/read the email replies.
For that you will have to create 'Rule Sets' within the 'Email Receiving section' of SES.
The replies can be redirected to services like S3, SNS,Lambda, workmail to name a few and then you can read those from that redirected service
We are trying to send mail on to Gmail account by using send grid api but Gmail has blocked the email which is sent from send grid. Please check the message given below:
550 5.7.1 [167.89.24.147 12] Our system has detected that this message is likely unsolicited mail. To reduce the amount of spam sent to Gmail, this message has been blocked. Please visit http://support.google.com/mail/bin/answer.py?hl=en&answer=188131 for more information. kw15si11591084pab.218 - gsmtp
We have checked all header parameter suggested by Send Grid and implemented it in our code. At the same moment, it works fine for other domain like AOL, Rediff etc.
Please suggest how we overcome with this problem as we have huge users on Gmail and we will send our emails to all those users as. Also, we have noticed that the email came after some time from Send Grid.
Many thanks in advance.
The recipient mail server analyzed your message and determined that the content of the message is spammy. My recommendation would be to run your formatted message through a third-party service, www.mail-tester.com , to identify ways to improve the reception of the message. It's also possible that your sending IP address, 167.89.24.147 based on the response message you've included, is listed on a black list. You'll want to scan your sending IP on a site like http://multirbl.valli.org/ and, if you see that your IP is listed anywhere, submit a delisting request with the black list.
SendGrid also has a Spam Checker app - Turning on SendGrid's Spam Checker app can help combat this, as you're able to set a predefined filter and get alerted when your content exceeds the filter that you set.
Whenever i try to send a mail from my website for email verification, the same is being received in a spam folder. I noticed that plain messages are being received in inbox, but whenever i try to include an ordinary http link[http://abcd.in/abcd/verify.php?key=2f27feb552c83c6c65b9bfc4d799e775], the mail goes to the spam folder. Cant point out the reason why this is happening. Please help me to resolve this issue.
Thanks All
From experience, I know that the spam score can be affected when hyperlinks have an alphanumeric argument tagged onto the end. I suggest trying to reformat the URL into something like;
http://abcd.in/abcd/f27feb552c83c6c65b9bfc4d799e775/verify.php
and extracting the reference using a Regex or Split()
Is your outgoing mail server configured to receive mail?
Are you using a proper mail server with proper setup at all or some bulk-mail-sending dud?
Are your mails sent with a real from address? And I don't mean the header-from that you can add in your software, but the protocol-from that is being used by sendmail
Do you have domain keys/dkim set up for your mail server?
Is the header OR the protocol from address from a different domain? Do they have set up domain keys allowing your mailserver?
Does your mail server feature the same domain name on the reverse lookup?
Does your mail server offer to receive mail for the user they are sending for?
Is your webhost using a smart relay? Do they rewrite the from: address?
Or do you send mails with internal mail address from?
I will be sending legitimate emails to a list of recipients and some of them are probably obsolete by now.
I wish to know, based on the email bounces, which are obsolete and delete them from the database. Except VERP I haven't seen anything standardized for this task.
Is there some other way that you know about?
There is no other way than VERP. DSN mails are good to extract the precise reason of bouncing, but not all servers send standard DSN mails. In addition to that, DSN mails can be forged which may be an issue. You can add a simple digital signature to a VERP address.
There is absolutely a way to do this. I run the engineering team at Kickbox. Our product takes a list of emails and will tell you which are valid and which are not (without sending to them). We have an API too.
You want to avoid bounces by sending to bad emails. Send to too many and your IP address will be globally blacklisted.
You can technically verify emails yourself through regular SMTP (just stop the SMTP commands before actually sending the email), but there are plenty of weird SMTP edge cases and for any serious number of emails you'll want to do this through a proper email network (like ours :-).
Hope that helps