sendmedialtd
Active Member
Hey,
I've had a few issues with getting MailWizz working properly on a server that has cPanel/WHM installed. Below are some issues which iv had to trouble shoot myself and fix them myself, so i thought I'd create a topic so anyone else who may have the same issues can look at this thread and fix them themselves. This topic will be updated as new issues arise with a guide on how to fix the problem. If your issue is not listed then feel free to add to this and i will see if i can fix it for you.
If you have had any other issues yourself and have fixed them please let me know in the comments so i can add them to this thread. If any of the below issues have resolved your problems make sure you give this Thread a LIKE or comment to say thank you.
1) Connection Refused
Some of you who have the Connection Refused error when adding SMTP/Feedback Loop/Bounce Server settings is caused by one of 2 issues. The first one being the SMTP Restriction, make sure that you go to WHM > Security Centre > SMTP Restirctions and TURN OFF that feature.
If you have Config Server Firewall Enabled then you will also need the do the following 2 changes, go to WHM > Pluggins > Config Server Firewall & Security. Click on the Config Server Firewall Tab and then click on Firewall Configuration. If SMTP_BLOCK is enabled then leave it as Enabled and then search for SMTP_ALLOWUSER. You will need to add the account username to the SMTP_ALLOWUSER section that is hosting the MailWizz App. Without doing so the firewall will keep blocking outgoing SMTP connections. Do NOT turn off SMTP_BLOCK as its there for your security. If you turn it off then it will allow ALL accounts on your server to connect to outgoing SMTP services which can be a security risk for any exploited scripts running on the server. Please make sure you read the next issue too.
Another thing to check is to make sure in the Firewall Configuration that you have Port 25 showing in the TCP_OUT setting otherwise your server will not be able to connect to any outgoing SMTP server using port 25. Also make sure Ports 465 for SSL and 587 for TLS is also OPEN on the firewall.
2) Connection Timed Out
Following on from the above issue there is another issue which when validating SMTP Servers where you may get the following warning:
Please ignore that warning, your validation email has actually been delivered so make sure you check your emails and click on the link to validate the SMTP Server. As you can see from the warning you "<< 250 Accepted" the emails was accepted and delivered fine. As for the Time Out error it looks to be a false warning. I've looked into the Exim Logs and can see the following:
From what i can tell from the Exim Logs is that its actually the MTA that MailWizz uses that is closing the connection using the QUIT command, but for what ever reason MailWizz is reporting it as an error. I've informed @twisted1919 about this and we will all just have to wait and see if anything can be done about this or if i can find a way myself on how to resolve the false warning.
EDIT: Even though the emails still get sent, if you actually want to do it so you dont get the timeout error then make sure you increase the Timeout on the Deliver Server setting. Increase this to 60 should resolve the problem.
3) exec function must be enabled in order to handle the DKIM keys.
With the latest Cpanel/WHM you will have multiple PHP versions installed which allow you to control which accounts use what version of PHP. Your first thought is to check the Disabled Functions in the PHP INI file. How ever you will see that the disabled_functions section is blank which may seem confusing. This is because cPanel/WHM by default will automatically disable some functions without you even knowing, exec being one of them. To stop this you first need to find out what version of PHP the account hosting MailWizz is using, go to the following, WHM > Software > MultiPHP Manager. Find your account and look at what PHP Version the account is using i.e ea-PHP70.
Then using an Editor or download Config Server Explorer (highly recommended) you then need to edit the following file /opt/cpanel/ea-php70/root/etc/php-fpm.d/YOURDOMAIN.com.conf
Remember to replace ea-php70 with the php version your account is using and change YOURDOMAIN.com to your actual domain name.
By default you will see the following: php_admin_value[disable_functions] = exec,passthru,shell_exec,system
Make sure you remove exec from that list and then click Save and then Restart PHP and Apache via WHM > Restart Services.
4) No Campaigns are sending and no Cron Jobs are running.
Ok so again it seems the cron command may need to be different for cPanel/WHM servers. First of all login to SSH using Putty. You then want to type in the following command:
That will give you a response such as /usr/local/bin/php. That is the path to PHP in order to run Cron Jobs. When installing MailWizz the setup guide will tell you to install cron jobs with the path to PHP as /usr/bin/php (without the local part). That is because that is the usual path to PHP and will work on most servers, how ever it seems yet again cPanel/WHM like to make things confusing. So if the response you got was somthing different to the ones you have setup in your Cron Tab then make sure you update the path to PHP. Once you have done so then your Cron Jobs will start to work and you should now see your campaigns starting to be processed.
5) Error 400! The CSRF token could not be verified.
This error is produced when your PHP is not setup correctly or changes need to be made. The most common reason for this is the setting for post_max_size and upload_max_filesize. Login to WHM and go to PHP INI Editor and then select Editor Mode. Select the PHP version of the account MailWizz is hosted on and then search for upload_max_filesize, you need to increase that value. I have mine set at 500M because its a dedicated server and i only user MailWizz on the server. You then need to search for post_max_size and increase the value of that, i have that set to 200M. Once done click Save, and then restart PHP and Apache.
6) Error 500! Missing the temporary folder to store the uploaded file "FILENAME.csv".
This error is produced because it has no path set in PHP of where to store tempory files. Login to WHM and go to PHP INI Editor and then select Editor Mode. Select the PHP version of the account MailWizz is hosted on and then search for upload_temp_dir. You want to set the path to /tmp which is the default location by most servers. Also make sure you uncomment the line out if it is by removing the ; from the beginning so it says upload_tmp_dir and NOT ;upload_tmp_dir
Save, restart PHP and Apache.
7) Connection to the Delivery Servers taking longer than 20 seconds?
There are a few different reasons for why this could be happening, the main reason for this is because of a Delay setting in WHM, to change this you need to go to "Home »Service Configuration »Exim Configuration Manager". Under ACL Options you will find this part:
"Introduce a delay into the SMTP transaction for unknown hosts and messages detected as spam. "
If that is turned on then make sure you turn it OFF. Save the Exim Configuration and restart Exim.
If that still hasnt fixed the issue for you then your issue will be because of the version of cPanel/WHM you are running, make sure you have upgraded from EasyApache3 to EasyApache4 as if you've not then you wont be able to download the new versions of cPanel/WHM. To do this login to SSH as ROOT and run this command:
The upgrade will take a while so wait for it to complete. Once you've upgraded then make sure you upgrade the cPanel/WHM software to the latest version. I've seen people with old versions (including myself) of Exim/cPanel/WHM cause this delay and once upgraded theres no such issue. Again upgrading cPanel/WHM (which will internally upgrade Exim) will take an hour or so to complete.
Note: This setting is for the Servers the Delivery Servers are on. So for example if you have 1 server hosting MailWizz and another server you use for your Delivery Servers then its just the Delivery Servers server you need to make this change to.
---------------------------------------------------
Thanks,
Mike
I've had a few issues with getting MailWizz working properly on a server that has cPanel/WHM installed. Below are some issues which iv had to trouble shoot myself and fix them myself, so i thought I'd create a topic so anyone else who may have the same issues can look at this thread and fix them themselves. This topic will be updated as new issues arise with a guide on how to fix the problem. If your issue is not listed then feel free to add to this and i will see if i can fix it for you.
If you have had any other issues yourself and have fixed them please let me know in the comments so i can add them to this thread. If any of the below issues have resolved your problems make sure you give this Thread a LIKE or comment to say thank you.
1) Connection Refused
Some of you who have the Connection Refused error when adding SMTP/Feedback Loop/Bounce Server settings is caused by one of 2 issues. The first one being the SMTP Restriction, make sure that you go to WHM > Security Centre > SMTP Restirctions and TURN OFF that feature.
If you have Config Server Firewall Enabled then you will also need the do the following 2 changes, go to WHM > Pluggins > Config Server Firewall & Security. Click on the Config Server Firewall Tab and then click on Firewall Configuration. If SMTP_BLOCK is enabled then leave it as Enabled and then search for SMTP_ALLOWUSER. You will need to add the account username to the SMTP_ALLOWUSER section that is hosting the MailWizz App. Without doing so the firewall will keep blocking outgoing SMTP connections. Do NOT turn off SMTP_BLOCK as its there for your security. If you turn it off then it will allow ALL accounts on your server to connect to outgoing SMTP services which can be a security risk for any exploited scripts running on the server. Please make sure you read the next issue too.
Another thing to check is to make sure in the Firewall Configuration that you have Port 25 showing in the TCP_OUT setting otherwise your server will not be able to connect to any outgoing SMTP server using port 25. Also make sure Ports 465 for SSL and 587 for TLS is also OPEN on the firewall.
2) Connection Timed Out
Following on from the above issue there is another issue which when validating SMTP Servers where you may get the following warning:
Please ignore that warning, your validation email has actually been delivered so make sure you check your emails and click on the link to validate the SMTP Server. As you can see from the warning you "<< 250 Accepted" the emails was accepted and delivered fine. As for the Time Out error it looks to be a false warning. I've looked into the Exim Logs and can see the following:
From what i can tell from the Exim Logs is that its actually the MTA that MailWizz uses that is closing the connection using the QUIT command, but for what ever reason MailWizz is reporting it as an error. I've informed @twisted1919 about this and we will all just have to wait and see if anything can be done about this or if i can find a way myself on how to resolve the false warning.
EDIT: Even though the emails still get sent, if you actually want to do it so you dont get the timeout error then make sure you increase the Timeout on the Deliver Server setting. Increase this to 60 should resolve the problem.
3) exec function must be enabled in order to handle the DKIM keys.
With the latest Cpanel/WHM you will have multiple PHP versions installed which allow you to control which accounts use what version of PHP. Your first thought is to check the Disabled Functions in the PHP INI file. How ever you will see that the disabled_functions section is blank which may seem confusing. This is because cPanel/WHM by default will automatically disable some functions without you even knowing, exec being one of them. To stop this you first need to find out what version of PHP the account hosting MailWizz is using, go to the following, WHM > Software > MultiPHP Manager. Find your account and look at what PHP Version the account is using i.e ea-PHP70.
Then using an Editor or download Config Server Explorer (highly recommended) you then need to edit the following file /opt/cpanel/ea-php70/root/etc/php-fpm.d/YOURDOMAIN.com.conf
Remember to replace ea-php70 with the php version your account is using and change YOURDOMAIN.com to your actual domain name.
By default you will see the following: php_admin_value[disable_functions] = exec,passthru,shell_exec,system
Make sure you remove exec from that list and then click Save and then Restart PHP and Apache via WHM > Restart Services.
4) No Campaigns are sending and no Cron Jobs are running.
Ok so again it seems the cron command may need to be different for cPanel/WHM servers. First of all login to SSH using Putty. You then want to type in the following command:
Code:
which phpThat will give you a response such as /usr/local/bin/php. That is the path to PHP in order to run Cron Jobs. When installing MailWizz the setup guide will tell you to install cron jobs with the path to PHP as /usr/bin/php (without the local part). That is because that is the usual path to PHP and will work on most servers, how ever it seems yet again cPanel/WHM like to make things confusing. So if the response you got was somthing different to the ones you have setup in your Cron Tab then make sure you update the path to PHP. Once you have done so then your Cron Jobs will start to work and you should now see your campaigns starting to be processed.
5) Error 400! The CSRF token could not be verified.
This error is produced when your PHP is not setup correctly or changes need to be made. The most common reason for this is the setting for post_max_size and upload_max_filesize. Login to WHM and go to PHP INI Editor and then select Editor Mode. Select the PHP version of the account MailWizz is hosted on and then search for upload_max_filesize, you need to increase that value. I have mine set at 500M because its a dedicated server and i only user MailWizz on the server. You then need to search for post_max_size and increase the value of that, i have that set to 200M. Once done click Save, and then restart PHP and Apache.
6) Error 500! Missing the temporary folder to store the uploaded file "FILENAME.csv".
This error is produced because it has no path set in PHP of where to store tempory files. Login to WHM and go to PHP INI Editor and then select Editor Mode. Select the PHP version of the account MailWizz is hosted on and then search for upload_temp_dir. You want to set the path to /tmp which is the default location by most servers. Also make sure you uncomment the line out if it is by removing the ; from the beginning so it says upload_tmp_dir and NOT ;upload_tmp_dir
Save, restart PHP and Apache.
7) Connection to the Delivery Servers taking longer than 20 seconds?
There are a few different reasons for why this could be happening, the main reason for this is because of a Delay setting in WHM, to change this you need to go to "Home »Service Configuration »Exim Configuration Manager". Under ACL Options you will find this part:
"Introduce a delay into the SMTP transaction for unknown hosts and messages detected as spam. "
If that is turned on then make sure you turn it OFF. Save the Exim Configuration and restart Exim.
If that still hasnt fixed the issue for you then your issue will be because of the version of cPanel/WHM you are running, make sure you have upgraded from EasyApache3 to EasyApache4 as if you've not then you wont be able to download the new versions of cPanel/WHM. To do this login to SSH as ROOT and run this command:
Code:
/scripts/migrate_ea3_to_ea4 --runThe upgrade will take a while so wait for it to complete. Once you've upgraded then make sure you upgrade the cPanel/WHM software to the latest version. I've seen people with old versions (including myself) of Exim/cPanel/WHM cause this delay and once upgraded theres no such issue. Again upgrading cPanel/WHM (which will internally upgrade Exim) will take an hour or so to complete.
Note: This setting is for the Servers the Delivery Servers are on. So for example if you have 1 server hosting MailWizz and another server you use for your Delivery Servers then its just the Delivery Servers server you need to make this change to.
---------------------------------------------------
Thanks,
Mike
Last edited:
