tony.localword

Yes, it works now, thank you!

Just sent you the URL. Thanks.

Thank you, that worked.

Here is an example, but all of the products has the same problem:

https://dev.raggssupply.com/product/block-ice/

Thank you

I downloaded the plugin from your link and looked at the aws folder. It appears to be about 20MB, so a bit smaller than the 30 MB I see on my sites, but still seems quite large. Just to be clear, are you saying that this is the normal size?

The path is vendor/aws/aws-sdk-php/src/data, but I couldn’t find any large file in that folder. It appears there are hundreds of smaller files (<100kb) in that directory, all totaling some 20-30 MB.

I have looked at several different websites and they all show almost exact same issue.

Thanks

• This reply was modified 1 year, 8 months ago by tony.localword.

Hi,

Thank you but I don’t understand your reply. Do you mean that you can’t figure out what the problem is? Do you need more information?

I have duplicated the problem on another website, so I think the problem is not unusual.

If it’s helpful, I can send you screenshots of the email header I receive showing the error, and also the plugin Email Log. Let me know where to send it.

I am happy to assist in debugging in any way.

Thanks

Do you mean the Diagnostic test found in Dashboard-> Troubleshooting -> Diagnostic Test? Here is the output:

Mailer: postsmtp
HostName: jandspartyrental.com
cURL Version: 7.84.0
OpenSSL Version: OpenSSL/1.1.1q
OS: Linux cloudvpsserver.host.localword.net 3.10.0-1160.49.1.el7.x86_64 #1 SMP Tue Nov 30 15:51:32 UTC 2021 x86_64
PHP: Linux 7.4.30 en_US.UTF-8
PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=No, zlib_encode=Yes
WordPress: 5.9.4 en_US UTF-8
WordPress Theme: JandS-Party-Rental
WordPress Plugins: ManageWP - Worker, Autoptimize, Formidable Forms, CAOS, Plugin Organizer, Post SMTP, W3 Total Cache, Wordfence Security, Yoast SEO, WPS Hide Login
WordPress wp_mail Owner: /home/jandspartyrental/public_html/wp-content/plugins/post-smtp/Postman/PostmanWpMailBinder.php
WordPress wp_mail Filter(s): PostsmtpMailer->get_mail_args
WordPress wp_mail_from Filter(s): wordfence::fixWPMailFromAddress
WordPress phpmailer_init Action(s): PostsmtpMailer->phpmailer_smtp_init
Postman: 2.1.7
Postman Sender Domain (Envelope|Message): jandspartyrental.com | jandspartyrental.com
Postman Prevent Message Sender Override (Email|Name): Yes | Yes
Postman Active Transport: SMTP (smtps:plain://mail.jandspartyrental.com:465)
Postman Active Transport Status (Ready|Connected): Yes | Yes
Postman Deliveries (Success|Fail): 459 | 7

Hi, any updates on this?

Hi, thanks for the response.

Yes, I have set the email address and enabled the “Prevent plugins/themes from changing this”

Somehow, it appears the Post SMTP plugin is using the wp admin email as the From Address, but ONLY for notifications. Actual form submissions are sent with the correct From Address.

I also see that under Settings -> Notifications, the notification service is set to WP Admin Email, but that should only affect the To Address, not the From Address. Unless the plugin has a bug here?

Clearing the cache did not help. I disabled the cache, which cleared the error, but when I re-enabled the cache the error came back.

I just realized the message about w3total cache being incompatible is probably the error message, because it’s all in red? But since SpamFirewall is disabled, there should be no error or message.

If that’s true, maybe you should update that so there’s no error?

Thanks

I ran across the exact same problem today. Using incognito mode, for whatever reason, I went to the login page, closed the browser, opened again, 3 times within a pretty short period. The third time I got the anti-crawler screen.

After seeing the above post, now I’m wondering how many other visitors are getting this error?

Actually, I added all the correct IP’s needed. However, there must have been some glitch somewhere in the plugin because I deactivated/deleted it and reinstalled and it seems to be working fine now.

I will report back if I see a problem again.

Thank you.

I forgot to mention I’m also using wp fastest cache and the preload bot is also getting 403 errors. The ip is the same as the host, and I also whitelisted that ip.

Hi Rolf, update: I didn’t realize till later that many other important pages on my website were deleted using that process, so I guess I can’t use it after all. I’ll have to live with all those orphans ??