Contact form not sending mail

BPS does not interfere with emailing itself and works with all popular WordPress Contact form plugins. Being honest here and not evasive – Most of what the support person told you I have never heard before from anyone and honestly it does not really make any sense to me logically. Not going to say anything else about that. ??

So let’s start from square on to get on the right troubleshooting track. Personally I do not think the problem is related to the BPS plugin. I took a look at the judybuswell.com website and looked at the Source Code (FYI – disabling right mouse clicks does not really stop someone from viewing the Source Code of a website ?? )

Not a likely cause of the problem: WP Content Copy Protection script by Rynaldo Stoltz Ends

Very likely cause of the problem: her Contact page is being cached and minified using the W3TC plugin – W3TC: Minified using disk | Page Caching using disk: enhanced. Website pages that should never be cached or minified are: Login pages and Contact Form pages.
Solution: Create a page exclude rule in the W3TC plugin to not cache or minify the Contact page. Delete/flush all current W3TC cache. Then create the Contact page exclude rule.

[Edited – The Jetpack Grunion Contact Form has been tested and BPS does not block anything in this Jetpack Module|Plugin]

If there is still a problem after fixing these things above then let me know.

hmm even more interesting is the Grunion Contact Form plugin is an Automattic plugin. Kind of odd that it has not been updated in so long. ?? I will install the Grunion Contact Form plugin and test it just in case.

Ahh ok I see what is going on now. The Grunion Contact Form plugin is bundled in Jetpack now. Testing now and will post results shortly.

Works fine. BPS does not block anything in the Jetpack Grunion Contact Form.

Test email sent and received:

Name: Ed
Email: xxxx @ ait-pro.com
Comment: Testing Jetpack Grunion Contact Form

Time: March 5, 2015 at 6:53 pm
IP Address: xxx.xxx.xxx.xxx
Contact Form URL: https://bulletproof-security-pro.com/bpspro/contact-form-test/

Sent by a verified “Demo Site” user.

Thank you so much for the time you’ve put into helping me with this! Frankly the support guy’s statement about the htaccess file didn’t really make sense to me either, but it was good to hear you thought so too.

I will modify the caching settings after a cup of coffee and let you know how it goes…

PS, I know the no right-click thing doesn’t protect her images from anyone determined to have them and really neither does anything else since anyone who knows how can take a screenshot, but it makes her feel better.

Personally I think what the support person said was a “Pass the buck” thing. I am guilty of making that same mistake when I was a newbie to the technical scene a couple of decades ago. ??

Yep, sometimes “feel good” things are what is required with customers. Whether that “feel good” thing actually really does anything is not really relevant in those cases. ??

Hi there, good morning! I think you might be right about passing the buck.

So, I added /contact-judy-buswell/ to the pages to be excluded from the cache, flushed the page cache, refreshed the form page and tried sending a message. It shows up in the “Feedback” in the back end, but does not make it to the mailbox on the server. Tried several other attempts with no success. Removed the front and trailing slashes from the URI, flushed ALL caches, refreshed and tried again. Same thing – message shows up in Feedback, but does not get delivered to the mailbox. So I flushed all caches again and deactivated W3TC entirely, looked at the current root htaccess file in BPS to verify that there was no W3TC code in it (but did not re-create/activate the secure htaccess file) and double checked the htaccess file in the host server’s files – no W3TC code. Tried again – and again, the message is found in the Feedback section, but does not make it to the mailbox on the server. Am I doing something wrong, or have we just eliminated this as the root cause of the email delivery failures?

Thanks!

Ok completely eliminate the BPS plugin by doing the steps below. I think the problem is going to be on the host Mail Server itself then, but it could be something else that you have installed on the site. Since I tested the Grunion Contact Form on a test/demo site and it worked fine for me then most likely BPS does not have anything to do with this problem.

1. Click the Create default.htaccess File button on the Security Modes page to ensure that you have a good default.htaccess file for this particular website.
2. Select the Deactivate Root Folder BulletProof Mode (Default Mode) Radio button on the Security Modes page and click the Activate|Deactivate button.
3. Select the Deactivate wp-admin Folder BulletProof Mode Radio button on the Security Modes page and click the Activate|Deactivate button.

BTW, for some odd reason (and a weird coincidence) I am logged in and have the “Notify me of follow-up posts via email” box checked, but I have not received any email notifications from this thread! I’ll keep the window open and refreshed to look for new messages from you. Thanks so much for your help.

Hannah

Yep, I have noticed similar and exactly the same issues with the WP forum recently in the last couple of weeks (and maybe up to 1 month). I believe WP is doing some backend work on the WP forum site and obviously also on Plugin Stats (last few days) section of the WP forum site.

After deactivating the wp-admin folder I’ve been locked out of the site and the site is down. I’ll go check the htaccess file on the server now…

root htaccess is completely blank and locked down with 404 file permission. hang on…

Changed htaccess file permission to 644 and put the standard wordpress rewrite rules for fancy permalinks. site is still down, still locked out of admin

Oops yeah you have W3TC installed so I left out a step to deactivate the W3TC plugin first. Edit the wp-config.php file and comment out any W3TC code. It will look something like this: Define Cache and will be at the very top of the wp-config.php file. Add 2 forward slashes to comment out the W3TC code: //the W3TC code.