One of our applications use mandrill with a web hook. It was working fine and suddenly it does not receive inbound emails. I am seeing Mx record on AWS and all the tests are working fine.
But we don't receive emails. I have emailed mandrill support but they didn't respond.
Does anybody know how to debug such an issue?
I tried sending emails they are not bouncing back nor they are not received in mandril inbound box.
Thanks for any help.
Related
I have a Rails 4.2 app that's hosted on AWS that uses SES to deliver emails. I've set up SNS to POST notifications to the app when an email bounces. If I send a test email via the SES console, the endpoint associated with the SNS subscription gets hit by AWS exactly as expected with the bounce notification. When an email that gets sent from the application itself bounces, the endpoint is not hit, though there appears to be a corresponding bounce in the email statistics shown in the SES console.
If an email gets sent from the app with a Return-Path, the email associated with the return path does receive a "Delivery Status Notification (Failure)" message from the SES mailer daemon (though that email does go to spam). I have also checked the Apache access_log and error_log and only see the bounce notification endpoint hit when emails are sent via the SES console.
The emails within the app are sent via ActionMailer with a delivery_strategy of :aws_sdk (provided by the aws-sdk-rails gem). I have also tried using a delivery strategy of :smtp with email-smtp.us-east-1.amazonaws.com and the SES credentials--the only differences between the two strategies is that the :smtp strategy fails to follow the Return-Path. The Domain and email used in the "From" address are both verified with AWS, and DKIM is enabled, verified and appears to be working. The Bounce Notifications SNS Topic for the Domain is the correct one (and the topic's subscription has already been confirmed).
I've tested delivering emails to addresses with non-existent domains, non-existent addresses with real domains and bounce#simulator.amazonses.com. All tests with the app result in nothing being POSTed to the notification endpoint, and all tests with the SES console result in the expected behavior. All Amazon services use the same region (us-east-1), and all emails that are expected to be delivered without bouncing get delivered appropriately.
The code that delivers the mail looks essentially like this:
class SomeMailer < ApplicationMailer
def some_email
...
mail(
to: destination,
from: sender,
cc: cc_addresses,
subject: some_subject,
template_name: some_template,
return_path: return_path_email
)
end
end
I've tried taking out the return_path which has no effect on the SNS endpoint being hit.
I've done quite a bit of searching here and in the AWS docs and haven't found anything that changes this behavior. Any tips on how to get the bounce notifications delivered when being sent by the app would be greatly appreciated.
If you are using a Simple Mail Service verified email address to send the emails then make sure your notification topic is configured for that email address. If it is only configured for your domain then it will not work.
I ran into the same problem you describe and it was because I only had the notifications configured on my domain name and not the email address.
It's late but will surely help others, I was facing the same problem than realized that I was missing the configuration set header when I was sending an email from my web app.
I got to know this through SES sent test mail screen where there is a configuration set header.
Aws SES sent test email screen
So by adding this header you will start receiving the notifications.
We are using Rails 2.3.8 version. In our application, we tend to send individual email to all users ( around 1500 users - Bulk email ). We are not using any services other than Actionmailer. Hence, we cannot use any service (like mailGun, sendGrid, mailchimp, etc) Also, we have our own SMTP server, through which all the mails are sent.
We have added our mailing functionality to be executed in two scenarios.
Rake Task with CRON JOB ( Auto mails to be sent at specific time)
Via controller ( Mails are sent when a button is clicked)
In both the cases, Initially, the mails are forwarded to the users without any issues. As the user count increases, suddenly the mail functionality stops and throws either of the two following errors.
535 5.7.3 Authentication Unsuccessful
Execution expired
Could anyone please help me sort out the issue?
Is there any timeout value that has to be set for SMTP server connectivity? Or are there any restrictions (like number of mails sent per minute) ?
Thanks in Advance
I want to use SendGrid to receive emails. Here is my scenario.
User A will send an email from user-a#example.com to User B at user-b#example.org
I've setup a rule so that emails received by User B are forwarded to c#example.net.
example.net is my domain and I have configured example.net in SendGrid to point to an MVC controller which will process the JSON posted by SendGrid.
Is this possible? I was able to receive one email but after that it stopped working. What went wrong? Can any one help me out?
The problem was solved via a different channel. The resolution can be found here: https://community.sendgrid.com/sendgrid/topics/receiving_forwarded_mails_send_grid
Through using a number of debug tools, including RequestBin and Runscope, the user found there was an error in their controller, rather than an error in forwarding or message parsing.
We were able to debug and find the problem which as you predicted was with our controller.
We are still testing by sending mails from various domains but have not come across any mail that is getting lost.
— saurabh abhyankar, May 22nd 10:53 AM GMT
I'm trying to send email from my app, emails seem to be going to mandrill correctly and there getting delivered, but I see nothing in my inbox.
I've even tried sending them through my domain and I'm still not getting them. I get them from my live website its using gmail but I want to switch
Using mxtoolbox.com I found
SMTP Reverse DNS Mismatch and
454 4.7.1 Relay access denied which could mean its been marked for spam?
It's sent through emails twice so I'm wondering if theres a time between emails sent or something.
When I was testing this I thought my emails where being dropped by gmail. I found that for some reason there was a very long lag going from Mandril to Gmail. I received all my tests about an hour after Mandril sent them. Hope this helps someone stuck like I was.
Found this question trying to diagnose my issue.
I am using Mandrill and found that sending emails from Mandrill to Gmail will take anywhere from 10 seconds to 15 minutes. Can't establish a reason why sometimes it takes longer.
Mandrill blocks certain domains from being the send address to prevent fraud, but as long as you're sending from an address you know exists to an address you know exists, you should be fine. Also, if that were the problem, the email would bounce rather than send. Also, some email services have policies that prevent you from doing things like sending an email to your address from your address from an external service. Based on that error message you provided, it could be something like that; I would check your provider's policies (and your spam folder).
Not an answer but if you look on your mandrill Outbound activity page and click on the green icon that says Delivered you should see that it says No smtp events.
I don't know why it doesn't send but this show that it hasn't sent.
Or should I say hasn't arrived where it was supposed to.
Update:
On further investigation I found out that the emails weren't sending because I was using my personal email address as the sender from_email: When I changed this to a more business sounding email address it worked. So make something up if you have to, like no-reply#nonsense.com
I have application that needs to send emails and sms text messages. It sends emails just fine, but when I try to send text messages using email gateways (for verizon, xxxyyyzzzz#vtext.com) I get nothing. I have texted the phone using though the email gateway using my gmail account, so I know it works. I would just think that from my app's point of view I am just sending out another email. Any idea why this doesn't work? Or what I can do to troubleshoot it?
I should also note that I am doing this from a Rails app on my local computer...not that it should matter.
Maybe Verizon has software that can identify emails sent from software rather than humans, and rejects yours?
Try making your software add all the same headers (eg. X-Mailer) that a normal email client would add.
Verizon could be doing a reverse DNS query as a simple spam check. Your ISP's info could show up during this look up instead of the return address info that your email message contains, and thus could be getting blocked.
To troubleshot this make sure that the return e-mail address that you are using is coming from an ISP e-mail account.
Here is how to debug it on Linux. Run your Rails application server with strace:
strace -s99999 -e connect,read,write,close -o strace.log script/server
Then examine strace.log and see exactly which SMTP server the Rails application connects to, and what it reads and writes.
Then do the same with your favorite mail client (recommended: mutt, because Thunderbird is slow in strace).
Try to send exactly the same bytes from Rails what your mail client sends.
I have used SMS_Fu in the past to send out text messages. It has worked wonderfully.
I have written a client app for Ruby for sending SMS, please see http://freebiesms.blogspot.com/2009/07/send-free-sms-from-ruby.html to download
complete source code.
Regards
Dan