Open sumeetpareek opened 11 years ago
First thing I did was open the campaign and noticed that none of the mails (even the 78% sent in last two days) were opened. Which is obviously super weird.
On the server side PHP process (the cron script sending the mails out?) was running for TOO long.
The SENDY settings page showed only 4 mails reported as sent by AWS SES. Which I verified on AWS console too.
This question on the sendy forums helped in looking at the direction of the from mail - https://sendy.co/forum/discussion/comment/1795
Basically if the from mail is a mail that that is not verified yet on the AWS SES then the below happens -
Which means that if we have a wrong from email address set, then for 1L mails sendy would be stuck for 1L seconds and still no mails would go out.
And this has been precisely the case with us. The from address was correct for until recently, but somebody seems to have changed it to a non-verified mail. See below.
@ankurshrivastav I have shared the sendy admin account email / password with you on mail. The next steps you will need to take are -
that might not be the only reason why the emails aren't sent. cron jobs to execute the scheduled.php file in sendy installation directory is a must. or you'll have the same reaction. also double check the API access key and secret phrase from amazon aws. they keep changing the security settings. now you can setup IAM for it, but it is optional now (feb'16). Also it shows in amazon access key area if SES used it recently, so you can check it that way as well.
Here is the campaign in questions = http://messenger.aamaadmiparty.org/report?i=1&c=24
This is what the dashboard shows