Server Config - Amazon SES Bounces/Complaints

sendmedialtd

Active Member
Hey,

Heres a little tip for you, if you are planning on mailing millions of emails out a day then make sure you have a high powered server in order to send the kind of volume you are wanting to. Most of you will think the higher the CPU spec and the Memory the better, that isnt the case, another thing you need to think about is if you have your server setup correctly/optimised to handle thousands of connections at once. If your using Apache on your server then Apache is not the best thing for you, Apache has limits and can not handle thousands of concurrent connections, this will mean if your using a email service that notifies MailWizz regarding Bounces and Complaints that not all your bounces will be logged because Apache can not handle all the connections. This has happened to me because we send 5 million emails out a day via SES. Apache could not handle all the connections, we switched to LiteSpeed which you have to pay a monthly license fee for but its worth it. Theres alot of benefits from moving from Apache to LiteSpeed which includes:

DDoS Protection
Uses a hell of alot less CPU Load & Memory compared to Apache
User Friendly WebAdmin GUI
Cache Plugins
HTTP Load Balancing
and so much more (see them all here)

Here is a Benchmark comparing Apache and LiteSpeed:

serverload.png


We currently have our server installed with LiteSpeed and have it optimised to handle 6,000 concurrent connections. Yet our CPU Load and Memory useage is still alot lower than what it was with Apache.

If you have ever had any issues with not all your bounces/complaints being reported like i did because Apache failed because it couldnt handle all the connections then if you ask nicely from your ESP if they can send you a bounce report showing the email addresses of all the bounces then they may provide you with the list. I have Business Support with Amazon so after speaking with them on the phone and live chat they was nice and provided me with an excel file of all the email addresses that bounced which i can now import to the Blacklist. They may not do this for everyone and Live Chat and Phone support is only avilable for Business Support which is priced at $1,200/year. But its worth a try if you dont have it and ask nicely if they could send you an excel/CSV file of all the bounces.

Hope this helps some of you.
 
Oh, thats good info!
Also a load balancer with a few backends works a treat, with litespeed or nginx. That is, when a single server is not enough anymore.
 
Hey,

Heres a little tip for you, if you are planning on mailing millions of emails out a day then make sure you have a high powered server in order to send the kind of volume you are wanting to. Most of you will think the higher the CPU spec and the Memory the better, that isnt the case, another thing you need to think about is if you have your server setup correctly/optimised to handle thousands of connections at once. If your using Apache on your server then Apache is not the best thing for you, Apache has limits and can not handle thousands of concurrent connections, this will mean if your using a email service that notifies MailWizz regarding Bounces and Complaints that not all your bounces will be logged because Apache can not handle all the connections. This has happened to me because we send 5 million emails out a day via SES. Apache could not handle all the connections, we switched to LiteSpeed which you have to pay a monthly license fee for but its worth it. Theres alot of benefits from moving from Apache to LiteSpeed which includes:

DDoS Protection
Uses a hell of alot less CPU Load & Memory compared to Apache
User Friendly WebAdmin GUI
Cache Plugins
HTTP Load Balancing
and so much more (see them all here)

Here is a Benchmark comparing Apache and LiteSpeed:

serverload.png


We currently have our server installed with LiteSpeed and have it optimised to handle 6,000 concurrent connections. Yet our CPU Load and Memory useage is still alot lower than what it was with Apache.

If you have ever had any issues with not all your bounces/complaints being reported like i did because Apache failed because it couldnt handle all the connections then if you ask nicely from your ESP if they can send you a bounce report showing the email addresses of all the bounces then they may provide you with the list. I have Business Support with Amazon so after speaking with them on the phone and live chat they was nice and provided me with an excel file of all the email addresses that bounced which i can now import to the Blacklist. They may not do this for everyone and Live Chat and Phone support is only avilable for Business Support which is priced at $1,200/year. But its worth a try if you dont have it and ask nicely if they could send you an excel/CSV file of all the bounces.

Hope this helps some of you.
@sendmedialtd It's one of the great product and it actually works! :)
 
Oh, thats good info!
Also a load balancer with a few backends works a treat, with litespeed or nginx. That is, when a single server is not enough anymore.
Just out of interest, assuming I have VM's and a shared database on a seperate machine is it just a matter of cloning the machine? I am assuming that all of the config comes from the database so I only need the php code on the web server? My setup is all behind HA proxy so I would just be adding additional backend machines to that to scale.
 
I also assume I need CRON on a single capable machine not tied behind the HA proxy?
CRON job it's recommended to have it on a single capable machine that is not tied behind the HA proxy to avoid any potential performance issues. This ensures that the CRON job runs smoothly and does not cause any unnecessary delays or downtime.
 
CRON job it's recommended to have it on a single capable machine that is not tied behind the HA proxy to avoid any potential performance issues. This ensures that the CRON job runs smoothly and does not cause any unnecessary delays or downtime.
I have one machine for CRON and to deal with API requests. Sounds like I have it right :)
 
Back
Top