Unable to send campaigns

texo

Sendy will not send emails to a list, and after a few minutes simply displays the "resume" link.
We're using the latest version. Desperate!

We're using the latest version, cron is setup, domain and sender email are verified.

Ben

Sendy does send emails.

I just sent a Cyber Monday email to thousands of subscribers for another app.

Are you using 1.1.2?

If so, go to 'Reports' section. Then see what's the errors causing your emails not to send.

texo

Yes, I'm using 1.1.2
There are no errors listed in "Reports"
The campaign (to 8 recipients only) has been "Sending" for 55 minutes.
Clearly something is wrong, because another brand on this install is working correctly.

So I'd appreciate some help in troubleshooting the problem.

EDIT: I've just tested now, and the other brand on this install is not able to send either, when sending to the recipients from the first campaign.

Ben

Can you please PM me your installation URL, email and password. As well as access to your database (phpmyadmin?).

patrika

I also run into problem after I upgraded to 1.1.2. A campaign, that I started earlier today with only approx. 600 subscribers in the list, never was sent. What normally only takes, like 10-15 minutes remained in a sending state for at least 2 hours and the column "recipients" said 0 for the all time.
After this failure I created a very small and simple "dummie"-mail and tried to send to a smaller testlist with only 9 recipients, and this worked.
Just a thought: I duplicated the e-mail and just changed some parts in it (which I have done many times before). Can the new version have problems with duplicated campaigns?

EDIT: I needed to send the campaign so I downgraded back to 1.1.1.4. Now everything worked again. So there is something strange with the 1.1.2-version. At least for me in my configuration.

texo

Thanks, Ben, I will do so now. These are the only errors I can find, in apache error log:

48187:[Mon Nov 26 11:43:54 2012] [error](70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://sendit.mydomain.co.za/app?i=4

48188:[Mon Nov 26 11:53:29 2012] [error](70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://sendit.mydomain.co.za/app?i=4

48189:[Mon Nov 26 12:09:29 2012] [error](70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://sendit.mydomain.co.za/app?i=4

48191:[Mon Nov 26 12:19:57 2012] [error](70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://sendit.mydomain.co.za/app?i=3

48215:[Mon Nov 26 12:30:43 2012] [error](70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://sendit.mydomain.co.za/app?i=3

48216:[Mon Nov 26 12:43:16 2012] [error](70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://sendit.mydomain.co.za/app?i=3

48223:[Mon Nov 26 13:15:22 2012] [error](70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://sendit.mydomain.co.za/app?i=4

48228:[Mon Nov 26 14:04:17 2012] [error](70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://sendit.mydomain.co.za/app?i=4

48229:[Mon Nov 26 14:27:21 2012] [error](70007)The timeout specified has expired: ap_content_length_filter: apr_bucket_read() failed, referer: http://sendit.mydomain.co.za/app?i=3

Ben

@patrika there's nothing to do with 'duplicating campaigns'.

I have tested 1.1.2, sent to nearly ten thousand emails before pushing out the update.

I'm not sure what the issue is until I have a chance to check (I'm not at my desk now).

You can PM me your installation URL, email and password. As well as your phpmyadmin access to your database.

patrika

Hi Ben! I needed to send the campaign now, so I downgraded back to 1.1.1.4. After that, everything worked again. So there is something strange with the 1.1.2-version, -at least for me in my configuration. I'll stick with that version for a while.

hamid

Hello Ben. I also upgraded to 1.1.2 last week but when I tried to send out a campaign today to 1900 recipients, it said campaign was sent successfully but in reality no emails were sent. An hour later, I resent the campaign and again it said it was sent successfully but again no emails were sent out. I reverted back to v1.0.9 and resent the campaign. This time it went out. The strange thing about 1.1.2 was that it instantly said the campaign was sent successfully when it normally takes about 12 minutes to do so. Just thought to share. BTW, I love Sendy. Thanks so much.

Ben

Hi @hamid, 1.1.2 was released yesterday (less than 24 hours ago), not last week. Are you sure you were on 1.1.2?

Very glad that you like Sendy.

hamid

Originally I thought I had 1.1.1.2 but then thought I added an extra 1 so I'm not sure which version I had. In any case, I just download v 1.1.2 and will let you know how it goes.

Ben

Good news. After troubleshooting on @texo's server for almost nearly 8 hours, I've re-adjusted the sending code so that sending works on his server and ours. New features like 'auto retry' and 'error logging' are maintained. So it should work on servers similar to @texo's.

I've updated the same build, 1.1.2, available at http://sendy.co/get-started. I did not update the version to a new one as I know that I've been pushing out quite a lot of updates last week. If you have problems with sending on 1.1.2, just download the same build and replace /includes/helpers/class.amazonses.php.