BPS behavior is different between parent and child on a Network/Multisite subdirectory type.

[o6asan]

Hello,

Since three or four weeks ago I suddenly haven’t got notify emails from some of my sites which are on a Network/Multisite subdirectory type of WordPress. I’ve used BPS since 2013.11.30. I had no problem until three or four weeks ago and made no change to BPS settings at the time.

BPS behavior is different between parent and child.

I use an email plugin named WP Mail SMTP Plugin by Mail Bank. When I send an email from the main site, the email can be sent. But from the child sites, I got 334 SMTP error and the email cannot be sent.

At the point, BPS gives the log like below:

[403 GET Request: 2019/02/10 - 9:51 AM]
BPS: 3.3
WP: 5.0.3
Event Code: WPADMIN-SBR
Solution: https://forum.ait-pro.com/forums/topic/security-log-event-codes/
REMOTE_ADDR: 192.168.1.4
Host Name: 192.168.1.4
SERVER_PROTOCOL: HTTP/2.0
HTTP_CLIENT_IP: 
HTTP_FORWARDED: 
HTTP_X_FORWARDED_FOR: 
HTTP_X_CLUSTER_CLIENT_IP: 
REQUEST_METHOD: GET
HTTP_REFERER: https://accounts.google.com/signin/oauth/consentsummary?～～～
REQUEST_URI: /child-e/wp-admin/admin-ajax.php?state=wp-mail-bank&code=～～～&scope=https://mail.google.com/
QUERY_STRING: state=wp-mail-bank&code=～～～&scope=https://mail.google.com/
HTTP_USER_AGENT: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

On my sites, the mail plugin use Gmail account and OAuth 2.0 for itself. The plugin also use the file ‘admin-ajax.php’ for redirecting.

How can I fix this issue?

[AITpro Admin]

I believe this is the solution, let me know if this works or not:  https://forum.ait-pro.com/forums/topic/wp-mail-smtp-plugin-403-error/

[o6asan]

Sorry for my late reply.

Today, I had time. So, I updated the wp-admin htaccess file, and I does not have 403 error any more. But I still have the issue.

The differences between before and after in the file are like below:
Before

RewriteCond %{QUERY_STRING} [a-zA-Z0-9_]=(http|https):// [NC,OR]
RewriteCond %{QUERY_STRING} [a-zA-Z0-9_]=/([a-z0-9_.]//?)+ [NC,OR]
RewriteCond %{QUERY_STRING} (http|https)\: [NC,OR]

After

#RewriteCond %{QUERY_STRING} [a-zA-Z0-9_]=(http|https):// [NC,OR]
#RewriteCond %{QUERY_STRING} [a-zA-Z0-9_]=/([a-z0-9_.]//?)+ [NC,OR]
#RewriteCond %{QUERY_STRING} (http|https)\: [NC,OR]

Now, I think this issue is not caused by the plugin. It is probably related with Google API Scope changed.

[AITpro Admin]

Yep, that is the correct solution to fix the WP MAIL SMTP plugin 403 error.  Glad it worked to fix the problem.  I’ve never used the Google API Scope before.  So probably would not be of any help to you to figure out any issues with the Google API Scope.

[Author]

Posts