![]() ![]() Other things you can do, since the cron job for processing bounces is a simple command line script, you can actually call it from the command line as: If you don’t see those headers, then that’s bad, somehow those were stripped by the server that returned those emails into your bounce box, nothing much to do in this case. Next, it’s always a good way to actually login for the bounce box and verify if there are emails there and if there are, and those are returned for your MailWizz campaigns, look in the email source and make sure the following headers are there:īecause MailWizz uses those two headers to identify the campaign and the subscriber so that it can take proper actions against them. ![]() These services will limit the number of connections and might as well deny access to read the bounce boxes thus MailWizz won’t be able to connect and read the emails. If all the above look fine on your server, then make sure you don’t use services like gmail / yahoo / aol / etc as bounce servers. If the output contains the false word, then you don’t have imap installed and you have too. To make sure your command line php contains the imap extension and the functions, the best way would be to create a php file on your server, say imap.php with the following contents: Which will tell you the version you are using in command line and if that is indeed using the CLI module and not the web module, because, I also saw the command line calling the web module, which is wrong since the web module is subject to timeouts and the such while the command line module isn’t (well, it shouldn’t anyway) thus is perfect for long running scripts. You can verify this from command line, by running the command php -v And because the extension is missing, MailWizz might not be able to restore a proper state of the bounce server (MailWizz has fallbacks mechanisms to cope with missing pcntl extension) and your bounce server will remain stuck in cron-processing mode and will not be picked for processing next time when the cron runs, remember, only bounce server having the status active are picked up for processing.īottom line, if you see your bounce server has the status “cron-running” for more than 30 minutes, then you can go to your application.īackend -> Miscellaneous -> Emergency Actions and reset your bounce servers status so that they become active again.Īnother thing is that, when processing bounces, MailWizz uses php’s imap extension and even if your web instance of php contains the imap extension that doesn’t mean your command line (CLI) contains it too, matter a fact, I saw multiple servers that use php 5.3 as the web module(well, yeah php-fpm too, but you get the point), and php 5.2 as the CLI module. The thing is, the pcntl extension is something that doesn’t come with php and has to be installed separately so most of the time is likely that your php install doesn’t contain the extension. MailWizz relies on pcntl extension to make sure if the process doesn’t exit nicely (because of some error or timeout) to restore the initial status of the server, that is, the active status so that the server can be selected next time when the cron job will run. When a bounce server is being used to process bounces, its status changes from active to “cron-running” in your MailWizz web interface. So, you’ve sent a campaign and expect to get some bounces back because you intentionally put invalid emails there but nothing shows in the bounces area of the campaign and you are stumped because of that (that makes two of us) and of course you need to know why. Seems that bounces aren’t processed, what can I do? ![]()
0 Comments
Leave a Reply. |