It’s likely that the WAF is preventing the plugin from making self-pings to the server. BPGES triggers the sending of email batches by making an HTTP request to self, of the form: POST wp-admin/admin-ajax.php?action=bpges_send_queue. If possible, you may want to check Securi’s systems for evidence that these requests are being bounced.
Thread Starter
welsh10
(@welshlamb10)
Hi @boonebgorges,
I have asked them to check this and they are saying ‘POST 200 /wp-admin/admin-ajax.php?action=wp_bpges_send_queue&nonce=a4951b6cfd CACHES:-/WHITELISTED’
Apparently there is no issue their end.
Is there anything else that may be the cause?
Appreciate the help.
Thanks
I assume that their response means that the pings were *already* being whitelisted, not that they’re being whitelisted only after your support request?
Are other mails being sent on your system? Check password resets (which are handled by WP) and BP private messages or group membership requests (which are handled by BP) to rule out some other possibilities.
You can also set up BPGES debugging, by putting the following in your wp-config.php file:
define( 'BPGES_DEBUG', true );
A log file should be created in wp-content/uploads/bpges-debug.log after your first send. In a test group, make sure there are subscribed members, and then post some activity. Look at the log file to see what messages appear.
Thread Starter
welsh10
(@welshlamb10)
Hi @boonebgorges,
Found the issue.
Latest version of WP Mail SMTP Pro not playing nicely with any emails that should be handled by WP.
Thank you so much for getting back to me and this awesome plugin. Will give it a 5*.
Cheers
Great – thanks for reporting back!
