Hey, i've got the same problem that my acymailing enterprise 6.1.5 doens't send any campain anymore. when i clik to send now and the pop-up page page just shows "There is nothing to send'. The campaign remains unsent. Also when i tried to schedulded the campaign, it doesn't start. the campaign before (on 6 march) worked properly. The only difference is that i updated to 6.1.5 and joomla 3.9.6 yesterday. While updating i didn't mentioned problems. In acymailing , it says that i have the last version 6.1.5
Ignace

The testmail during the configuration of the campaign works, but no starting of the queue (it stays at scheduling). i'm here in Belgium and see the time of the cron task (last time : acymailing trigged 7 min ago at 19:44). Here is it 21:51). Could there be a problem with different time blocks?

I've set the website time correct for Belgium (Brussels), now in the configuration tab , i've got the correct time that the cron is activated, but still no sending of campaigns, neither schedulded or now

    4 days later

    • SsrnSupport Beginner

      • Post #13
      • Edited

      We've exactly the same issue during our evaluation of AcyMailing Starter 6.1.5 running on Joomla! 3.9.6
      So, i'm interested in the solution.
      Activation mails from subscriptions or test mails are delivered without any problems using both methods PHPmail or SendMail.

        Remi_Acyba: I anstalled the update (starter_v6.1.5_2019-06-10_12-21-19) as well, and it is NOT WORKING propperly.

        The queue does not sent the items automatically (so, as before).
        Stop/resume of the queue does not make the system send mails also.

        Chnaged compeared to before:
        I can now use the button "send now" in the queue. Then the emails are sent.
        The message from the previus version "There is nothing to send" is not displayed anymore.

        I performed als a complete new installation on a test site as well. I.e. started with a blank site - not updated from the last ACYmailing version.

        May it's helpful: My server is at UTC+1h

          The SPAM test and test email are likewise hanging.

          @srn Is your cron enabled on your AcyMailing 6 instance ?
          If yes, then please send us your backend access and a link to this thread via our support form.
          We will take a look at it.

          @Timmy64 This may be due to your configuration.
          If emails are not sent (or mailtester doesn't receive it) then that means there is something wrong with your mail configuration.

          • srn replied to this.

            Alexandre
            It is still the "starter" installation. So, there is no possibility to setup a cron right now in my installation.

            But - i am not trying to schedule a campain.
            I setup a list of some test-recipients and some test newsletters (test campains) with the aim of sending the mails "immediately".
            This just created the que but did not process the send process further.
            I needed to push "send now" in the que again.

            I also tried out the starter edition of v5 a few days before. There the que was processed automatically as I expected.

            So, i don't know whats wrong.

            Do you still need an admin login?

              Hi @srn,

              Oh ok, I get the point.
              Well that's something we've changed in AcyMailing 6 that's right.

              We decided to keep all the things belonging to the send process in the queue interface.
              That's why the email isn't processed as soon as the campaign is added in the queue.

              We will probably add a button or a message to give user the possibility to trigger the queue once the campaign is added into it.

              Thanks for the feedback!

              Mine, too. "There is nothing to be send", allthough theer are campaigns the queue. Test works fine. Sending to a test-list is not possible. Cron doesn't work either. Re-Install of the recent 6.1.15 doesn't help. What can I do to get it running? Regards, Ilja

              ok, it's perfectly working now with cron. no clue why, but that's ok!