Forum Replies Created

Viewing 15 replies - 31 through 45 (of 1,410 total)
  • Plugin Contributor redsand

    (@redsand)

    UPDATE:

    We published a blog post about the fake plugin:
    Malware Alert: Beware of Fake Plugin X-WP-SPAM-SHIELD-PRO

    Bleeping Computer covered it as well:
    Hacker Hides Backdoor Inside Fake WordPress Security Plugin

    Plugin Contributor redsand

    (@redsand)

    @reidbusi

    Thank you.

    We’ve received a number of reports about this and we’re investigating.

    We have reached out to Sucuri to find out why they did not add any explanation that the fake plugin is in no way related to the real plugin, and why they are deleting user comments that mention the real plugin.

    If there is any kind of negativity on their end, it would be news to us.

    – Scott

    @ddsucurinet: Perhaps you can provide some insight into this?

    Plugin Contributor redsand

    (@redsand)

    @jeffmcneill

    You said your piece. You don’t like the plugin. Got it. No problem.

    You’re just trolling and harassing us now. Way over the line. You need to stop.

    Plugin Contributor redsand

    (@redsand)

    Hi @mistral7-wporg!

    Thanks for taking the time share about all the spam blocked on your site! πŸ™‚

    We’ll keep working hard to provide the best WordPress spam protection out there.

    Keep spreading the word so we can put all spammers out of business. Have a great week!

    – Scott

    Glad to help! πŸ™‚

    @davisadmin, @blplaques, @clarkevans7,

    I’m not associated with Contact Form 7, but I can definitely help here. I’m the lead developer of WP-SpamShield (which does provide spam protection for CF7), and we’ve been using CF7 for a very long time, almost since it was released.

    The issue you’re talking about is a common one among contact form plugins. It’s not specific to CF7. The issue has a lot to do with email being sent from the server, instead of using SMTP on a real email account. In the past few years a lot of developments have been made to combat spam emails, and @blplaques hit on that a bit mentioning SPF, DKIM, DMARC.

    In a nutshell SPF adds a layer of protection by specifying which servers are allowed to send mail for your domain. DKIM and DMARC each take that a step further. Then you have email service providers like Google and Yahoo adding in their own rules about what they will and will not accept.

    The CF7 docs have a couple FAQs that address this issue:

    There is a lot more to it, but TL;DR: Sending email from your website’s server is not reliable, so the only reliable way to do it is to use SMTP on your site to send email from an actual email account on your domain (or on gmail.com, etc.)

    Basically you set up a real email account for your site, and use a secure API to transmit email from this account’s SMTP server. (We find Gmail to be an easy one for most people to use, but there are a number of others.) The nice thing too, is that all of these emails will be in the Sent folder of that account if you ever need to track one down.

    There are a number of plugins to do implement this. Just search the plugin directory for “SMTP”. Easy WP SMTP is a good one, but there are others as well. It just replaces the stock functionality of the WordPress wp_mail() function, and instead of using the server’s mail functionality, it uses SMTP. Boom….reliable.

    I definitely recommend adding SPF records, DKIM, and DMARC, but all those take time, and if you want to fix this problem fast, use an SMTP plugin. (As others mentioned Flamingo is handy as well for making sure you don’t lose any data if an email does not arrive.) That will fix the immediate issue, and you can work on the other steps later.

    We use CF7 heavily, and rely on it. Using this method to send WP’s email is the most reliable method possible, and for years, we have zero issues on our sites or client sites.

    If you want more detailed info on this type of issue, we have an FAQ about it with more info:

    That was initially written for WP-SpamShield’s built-in contact form, but since it’s a universal issue, the FAQ applies to all contact form plugins really.

    Hope that helps!

    – Scott

    Plugin Contributor redsand

    (@redsand)

    I’m sorry if I have offended you and by no means did I mean to troll you or anyone else involved.

    Well, intention or not, the way you have been coming at us on the forums and the way you have treated our tech support team, it is definitely has been unfriendly behavior.

    However, you failed to persuade me or provide examples/proof of how standalone Nginx is not enough to run WordPress and WP-Spamshield flawlessly.

    Part of the problem is that you don’t have the experience level with Nginx and Apache to be arguing as aggressively as you are. I’m sorry that you don’t understand the technical aspects from the info we’ve provided, but that kind of expertise is up to you to develop. That’s not on us. We have provided you specific examples and explanations, and if it still does not make sense, then I’m sorry, but there is nothing more we can do for you. That may only come with more experience.

    Again: .htaccess support is not required by this plugin, only enforced for some weird reason.

    Please stop pushing this false opinion — that is the definition of trolling. You’re just repeating the same thing, over and over, and even after 50 times, it still is not true.

    Also, I am running standalone Nginx, have not ported any .htaccess instructions of this plugin to my nginx config and it is all running without any issues for well over a year now, blocking all that awful spam flawlessly.

    As our tech support previously explained: it may seem like things are working flawlessly on the surface with your particular setup, but under the surface, there are features of the plugin that are not working as they should. If we ran diagnostics on your site, we could show you that. When we say that standalone Nginx is not compatible, we do that for a reason.

    If you don’t understand all the nuances of it, then that’s ok. However, to repeatedly come online and aggressively contradict us, that’s not exactly friendly behavior. For the last five months, the only thing you’ve posted on the forums here is about this topic…do you understand how that is trolling?

    It’s time to put it to rest.

    P.S. In the end, despite all this nginx-stuff, thank you for the plugin!

    You’re welcome. Take care and best of luck.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Thanks for taking a minute to let others know about your experience with the plugin. Have a great week! πŸ™‚

    – Scott

    Forum: Reviews
    In reply to: [WP-SpamShield] Thank you!
    Plugin Contributor redsand

    (@redsand)

    You’re very welcome! πŸ™‚

    Forum: Reviews
    In reply to: [WP-SpamShield] thanks
    Plugin Contributor redsand

    (@redsand)

    Hi @brionace,

    You’re very welcome! We’re glad to help you keep spam away from your site! πŸ™‚

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Please see above:

    Please note (from the sticky post and from the plugin’s settings page) that we do not provide support through the forums here, so please direct all further support requests to the WP-SpamShield Support page and we’ll be happy to help.

    Plugin Contributor redsand

    (@redsand)

    Awesome info @fierevere! πŸ™‚ Thanks for posting this.

    Plugin Contributor redsand

    (@redsand)

    Hi April,

    Awesome! That’s what we like to hear…site owners should never have to deal with spam. Glad we could help! πŸ™‚

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi @motor721,

    I just wanted to follow up. We definitely appreciate the work you did helping to translate into Russian. Thank you! πŸ™‚

    After reviewing it, we see that it’s only about 40% complete, so we would not be able to include it with the plugin yet. However, your work can still become part of the plugin’s Russian translation. What I’d recommend is joining the plugin’s Russian Translation Project here on WordPress.org. (See the plugin’s Translation Project homepage.) It allows for different users to do partial translations — as little or as much as they like. Whatever you don’t do, others can work on. If you enter your work there, then you can make an important contribution. Once the translation reaches a certain percent complete, it will automatically download the appropriate language pack when the plugin is installed.

    Thank you again!

    – Scott

    Hey Mitch,

    WP-SpamShield does stop spam registrations…in fact it’s one of the best at it. It will do exactly what you need. You mentioned having an anti-spam plugin – if you are using Akismet, it will work together with it. (If you are using a CAPTCHA-based plugin, then the two won’t be compatible.) Let us know if you have any questions, and we’ll be happy to help. If it doesn’t meet your needs, then no problem…just ignore this. πŸ™‚

    – Scott

Viewing 15 replies - 31 through 45 (of 1,410 total)