Title: [Plugin: WP Security Scan] Security Scan breaks Subscribe2 Mail Queue
Last modified: August 20, 2016

---

# [Plugin: WP Security Scan] Security Scan breaks Subscribe2 Mail Queue

 *  [ricka99](https://wordpress.org/support/users/ricka99/)
 * (@ricka99)
 * [14 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-security-scan-security-scan-breaks-subscribe2-mail-queue/)
 * Mail Queue gave this error message: WPMQ Error. The wp_mail() function already
   exists. This is likely to be caused by another plugin.
 * I discovered that it was WP Security Scan causing the problem. The error message
   went away as soon as I disabled Security Scan.
 * The Mail Queue developer said this, “Having just had a look at the [WP Security
   Scan] code, it’s because this plugin requires the WP core pluggable.php file 
   on loading instead of using the action API. That means the pluggable code is 
   called earlier than it should be.”
 * [Link](http://wordpress.org/support/topic/plugin-subscribe2-mail-queue-error-message?replies=4#post-2350444)
   to Forum Post.
 * Hope you guys fix this soon.
 * [http://wordpress.org/extend/plugins/wp-security-scan/](http://wordpress.org/extend/plugins/wp-security-scan/)

Viewing 4 replies - 1 through 4 (of 4 total)

 *  [WebsiteDefender](https://wordpress.org/support/users/websitedefender/)
 * (@websitedefender)
 * [14 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-security-scan-security-scan-breaks-subscribe2-mail-queue/#post-2307953)
 * Thanks Rick for letting us know about this issue! We’ll look into it and see 
   what we can do about it.
 * Thank you for your feedback!
 *  [WebsiteDefender](https://wordpress.org/support/users/websitedefender/)
 * (@websitedefender)
 * [14 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-security-scan-security-scan-breaks-subscribe2-mail-queue/#post-2308078)
 * Hello, Rick!
 * I have installed the [http://wordpress.org/extend/plugins/subscribe2/](http://wordpress.org/extend/plugins/subscribe2/)
   plug-in but couldn’t replicate that error…they both work just fine together…
 * Edit:
    WP v3.2.1 WP Security Scan v3.0.7 Subscribe 2 v6.5
 *  Thread Starter [ricka99](https://wordpress.org/support/users/ricka99/)
 * (@ricka99)
 * [14 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-security-scan-security-scan-breaks-subscribe2-mail-queue/#post-2308080)
 * The conflict is with the WP Mail Queue plugin. Info [here](http://wpplugins.com/plugin/76/wordpress-mail-queue-wpmq/).
 * There are not many people who are going to use this plugin but since the developer
   claims that the conflict results from your not using the “action API”, I think
   it would be worthwhile to check it out and see if you should be using it.
 *  [WebsiteDefender](https://wordpress.org/support/users/websitedefender/)
 * (@websitedefender)
 * [14 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-security-scan-security-scan-breaks-subscribe2-mail-queue/#post-2308135)
 * Hi RickA99,
 * Thank you for your suggestion. We will definitely check them out.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘[Plugin: WP Security Scan] Security Scan breaks Subscribe2 Mail Queue’
is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wp-security-scan_f2f2f2.svg)
 * [Acunetix WP Security](https://wordpress.org/plugins/wp-security-scan/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-security-scan/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-security-scan/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-security-scan/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-security-scan/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-security-scan/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [WebsiteDefender](https://wordpress.org/support/users/websitedefender/)
 * Last activity: [14 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-security-scan-security-scan-breaks-subscribe2-mail-queue/#post-2308135)
 * Status: not resolved