Conversation
supportI was using your plugin on my websites up until today when I realized that I had not received ANY email submissions in the past three days since updating the plugin to v2.6.0. I have since deactivated the plugin until this issue can be resolved. I had been using the “Universal” blacklist settings across all my forms and rejecting submissions based on specific domains and email addresses I had identified. It was working as expected up until the version update. Today, I tried to submit a form using my own email address (which is not on the block list), and it was rejected as spam. I tried two other personal email addresses that are also not on the block list, and they were also rejected. At that point I deactivated the plugin. I was able to verify that unblocked form entries are successfully submitting on v2.5.6 as I had not gotten around to updating the plugin on one of my websites. I was able to submit a test form using my email address that was being blocked on the other websites. I was happy with your product until it started blocking all form requests. If an update can be provided that resolves this issue quickly I will consider reactivating.
Sorry to hear that you are having issues with the updated version of the plugin. We have tested this exact scenario you have indicated and the updated version should not have changed the behavior of it. Are you able to share your exact settings that you used for the plugin so we are able to take a look to see if we can reproduce the issue with your settings? If you have information in your settings that you do not wish to send on this public forum then you can contact us directly through our support form: https://www.crosspeaksoftware.com/support/
I replied directly to the link you have provided last week and received no response. Please advise, we are getting hit pretty hard with spam emails again while the plugins are off.
Hi, thanks for the update. I just checked and it looks like submission was flagged as spam so we hadn’t seen it. I’ll review that now.
Thank you for responding to the support ticket on your website and finding the issue that the unattached wildcard symbol that ended up in my list of blocked domains caused the problem. Also thank you for explaining that the reason this popped up now is that the previous versions of the plugin it was ignoring that wildcard. I appreciate you resolving the issue. This reply was modified 1 year, 3 months ago by northstargabe . Reason: Marking as resolved
Thanks for your followup here. For others reading this, we determined that in the long list of blacklists there was a mistaken * meaning wildcard block all. For a simplified example: *.example, *, *.test In 2.5.6 this wildcard was ignore as invalid but since 2.6.0 now supports * for wildcards it now resulted in block all.
Sorry to hear that you are having issues with the updated version of the plugin. We have tested this exact scenario you have indicated and the updated version should not have changed the behavior of it. Are you able to share your exact settings that you used for the plugin so we are able to take a look to see if we can reproduce the issue with your settings? If you have information in your settings that you do not wish to send on this public forum then you can contact us directly through our support form: https://www.crosspeaksoftware.com/support/
I replied directly to the link you have provided last week and received no response. Please advise, we are getting hit pretty hard with spam emails again while the plugins are off.
Hi, thanks for the update. I just checked and it looks like submission was flagged as spam so we hadn’t seen it. I’ll review that now.
Thank you for responding to the support ticket on your website and finding the issue that the unattached wildcard symbol that ended up in my list of blocked domains caused the problem. Also thank you for explaining that the reason this popped up now is that the previous versions of the plugin it was ignoring that wildcard. I appreciate you resolving the issue. This reply was modified 1 year, 3 months ago by northstargabe . Reason: Marking as resolved
Thanks for your followup here. For others reading this, we determined that in the long list of blacklists there was a mistaken * meaning wildcard block all. For a simplified example: *.example, *, *.test In 2.5.6 this wildcard was ignore as invalid but since 2.6.0 now supports * for wildcards it now resulted in block all.