So just had a site where mails where queued but weren't send.
I checked the cron status: Acymailing reported that the cron triggered okay.
So I decided to run the cron url from the browser and immediately i was faced with the following error message:
Out of range value for column 'unsubscribe_total' at row 1
So I looked at table #__acym_mail_stat and found an entry there where the value for unsubscribe_total was 1073741824
unsubscribe_total being a field of type int(11) explains why this was giving the error.
replacing the high value with 0 solved the problem and The scheduled mails were sending again.
Now here are some observations:
- the cron stranded with an error message: why is acymailing in configuration . queue reporting that the cron was successfully triggered? It is better to report there if the cron execution was successfull instead of triggered.
- Why is the number of unsubscribe_total that high? My theses here is that a (hacker) bot just hits the site with the unsubscribe link trying to get it to overload or create other issues... which it did. If this is the case, then it would make sense to only unsubscribe a user once (!) instead of just count every visit of the unsubscribe link for that user.
Anyway, wanted to share here so that if others run into the same issue they maybe have a solution 🙂