Most of hosting companies (almost all of them) apply some restrictions to the send process so you won't be able to send a lot of e-mails at once (this limitation is usually around 300 e-mails per hour). This article will explain you how AcyMailing sends your e-mails and how you can overcome any server limitation.
First of all, AcyMailing always uses a queue to send your e-mails.
In some cases, the mail server does not return a failed status to AcyMailing so AcyMailing will consider that all your e-mails have been sent properly and won't be able to stop the send process automatically. In that case, it's very important to configure AcyMailing to respect your sending limitations.
You can see and manage your queue of messages by clicking on the queue menu on the AcyMailing back-end.
If you use AcyMailing Starter or our commercial version (without the Automatic Only option) and you send a Newsletter, AcyMailing will open a popup and start sending your Newsletter to your users.
If AcyMailing detects errors during the process, it will either automatically refresh the page (to avoid a time out for example) or stop the sending process (if a hosting limitation is detected). In both cases AcyMailing should display you a clear message about what's going on and if AcyMailing stopped the send process, you will be able to resume it by clicking on the Process button on the queue page.
During the send process, the sending window (the popup) should always stay opened.
If you close it, AcyMailing will finish the current batch and then stop the send process.
That's not a problem as you will be able to resume it anyway.
If you want to be able to log out, turn off your computer and let Acy do the job, you will have to go for one of our paid version.
Using one of our commercial versions (AcyMailing Essential, Business or Enterprise), you will be able to configure AcyMailing to automatically overcome any server limitation and you won't have to keep your internet connection opened during the send process.
If you use AcyMailing to send e-mails from the front-end, it will always use the Automatic process but you should still configure a cron task to trigger AcyMailing regularly.
Depending on your hosting limitations, you can optimize the AcyMailing send process.
We recommend you to keep 5% of e-mails for your other components (send passwords, registration confirmation...) so if your limitation is 250 e-mails per hour, you should not use more than 240 e-mails for AcyMailing.
Each batch should not send more than 250 e-mails.
Here is the optimal configuration you should use based on the hosting company you are using for your website :
Tired of your hosting sending limitations? You can connect AcyMailing to an external delivery service...
My sending limitations are 300 e-mails per hour and I use your commercial version, how do I configure AcyMailing?
With a limitation of 300 e-mails per hour, we recommend to configure AcyMailing to send 280 e-mails per hour so 70 e-mails every 15 minutes.
Even if you don't have any sending limitation, we don't recommend you to send more than 300 e-mails per batch. Why?
If you don't mind your send process to take an entire day (or even more), the best configuration is usually to send 120 e-mails every 15 minutes.
You can increase your number of e-mails per task if you want to speed up the send process and/or create your own cron task with a frequency of 5 minutes.
It depends on the sending method you're using.
Last Updated on Sunday, 02 March 2014 17:59