Title: not getting alert emails Last modified: September 1, 2016 --- # not getting alert emails * Resolved [Rob Fleming](https://wordpress.org/support/users/rob0/) * (@rob0) * [9 years, 10 months ago](https://wordpress.org/support/topic/not-getting-alert-emails/) * Hello all: I am not getting any alert emails from WordFence. I am currently using GoDaddy managed WordPress hosting but am planning to migrate to GoDaddy’s deluxe Linux C-Panel hosting to allow direct control over my security and ability to use full SSL for my entire blog. What could be causing this email issue? * Thanks in advance for your help. * [https://wordpress.org/plugins/wordfence/](https://wordpress.org/plugins/wordfence/) Viewing 5 replies - 1 through 5 (of 5 total) * [wfalaa](https://wordpress.org/support/users/wfalaa/) * (@wfalaa) * [9 years, 10 months ago](https://wordpress.org/support/topic/not-getting-alert-emails/#post-7709249) * Hi Rob, It could be many things, please take a look at the following check-list: * – Make sure you chose the required alerts options under: (Wordfence > Options => Alerts) – Note the value of the “Maximum email alerts to send per hour” option.– Go to (Wordfence > Diagnostics => Other Tests) and try [sending test email](https://docs.wordfence.com/en/Wordfence_options#Send_a_test_email_from_this_WordPress_server_to_an_email_address) from there. – Check if your email server’s IP address has been added to a blacklist, check [this reference for more details](https://docs.wordfence.com/en/Emails_are_no_longer_being_sent_from_Wordfence,_but_alerts_are_enabled). * Finally, check your email spam folder. * Let me know how it goes, Thanks. * Thread Starter [Rob Fleming](https://wordpress.org/support/users/rob0/) * (@rob0) * [9 years, 10 months ago](https://wordpress.org/support/topic/not-getting-alert-emails/#post-7709254) * I had checked the settings you had mentioned on your reply and only after a full uninstall of your plugin and reinstall did the alert settings begin working…. I was planning on keeping WordFence install, but after consulting with a colleague working at Freebsd.org we have surmised the very same security can be achieved with some .htaccess rules and two edits to my WordPress functions.php file. I have had nothing with poor experiences with this plugin and the only thing that is worse is the incessant but false offer to purchase WordFence for $8.25 a month when in reality it is $99 annually and this precludes many WordPress users from choosing the premium version which in my opinion is a waste of money when some .htaccess edits and the addition of one or two “free” plugins will do exactly the same thing as WordFence….which to me sounds more as a WordOffence! * [bluebearmedia](https://wordpress.org/support/users/bluebearmedia/) * (@bluebearmedia) * [9 years, 10 months ago](https://wordpress.org/support/topic/not-getting-alert-emails/#post-7709257) * You’re certainly entitled to your opinion, but as a long-time WordFence user of the plug-in on many of my client sites, I can tell you that your assertions and assumptions are completely inaccurate. * Thread Starter [Rob Fleming](https://wordpress.org/support/users/rob0/) * (@rob0) * [9 years, 10 months ago](https://wordpress.org/support/topic/not-getting-alert-emails/#post-7709258) * well. I suppose if I were just a script kiddie then you would be right, however, I do know how to efficiently write code for WordPress and while I thought I would give WordFence and try, and everything I have posted in my previous posts and this one are not assumptions, but pure facts… you should look up the definition of a word before you attempt to use it…it only proves your ignorance! * While Wordfence does offer some automated features such as email warnings etc, everything in Wordfence can be achieved using .htaccess rules and a few simple additions to the WordPress functions.php and two 100% free WordPress plugins. * The biggest issue with WordFence is it nearly always breaks WordPress upon deactivation and has so many variables as part of the configuration that this fact alone can cause false positive triggers. Along with the fact, it is a memory hog makes this plugin hardly worth using when any competent WordPress admin could use the same simple formula I have and achieve the same results. Sadly, it is the WordPress owners who think that after setting up WordPress and adding in a few plugins that they are a “real” developer when in reality it is far from the truth. * So you can continue on the path of the script kiddie, while I use coding technology to protect my site! BUH BYE! * [wfasa](https://wordpress.org/support/users/wfasa/) * (@wfasa) * [9 years, 10 months ago](https://wordpress.org/support/topic/not-getting-alert-emails/#post-7709259) * Hello! Wordfence tracks attacks on more than 1 million WordPress websites and we use that data to build Firewall rules to protect both our free and paying customers. I’ll have to insist we do a lot more than send out a few emails. * Rob, I’m sorry to hear you’ve had bad experiences with our plugin. I am not going to try to convince you to use Wordfence. I hope you find a solution that works for you. Please try to keep the discussion healthy though and do not throw around insults like “script kiddie”. Thanks! Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘not getting alert emails’ is closed to new replies. * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865) * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/) * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq) * [Support Threads](https://wordpress.org/support/plugin/wordfence/) * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/) * 5 replies * 4 participants * Last reply from: [wfasa](https://wordpress.org/support/users/wfasa/) * Last activity: [9 years, 10 months ago](https://wordpress.org/support/topic/not-getting-alert-emails/#post-7709259) * Status: resolved