ramseyb

Thanks for the repy Brian. Great plugin! Hope all goes smooth with the updates.

Thanks for the quick reply Brian. Is there a release date for the block editor?

Hi Slava,

Below are the extra steps necessary to mitigate the PHP Warning caused by WP Mail SMTP, without disable (setting to none) open_basedir, which is a security concern. If you’re able to supply me with a open_basedir directive that would be great.

Because of inconsistency absolute path to the WordPress plugin localization .mo file is concatenated with the path to the plugin directory and, as result, restricted by open_basedir PHP parameter.

To resolve the issue install the Loco Translate plugin and created a wp-mail-smtp-en_US.po file via the plugin. Place the wp-mail-smtp-en_US.mo file in the /languages/plugins/ directory.

Good luck resolving the issue, Ramsey

• This reply was modified 6 years, 10 months ago by ramseyb.

Hi Slava,

Below is the reply from Plesk, which path would I add to the open_basedir directive to mitigate the PHP Warning and resolve this issue? As noted, it’s not an option to disable (set to none) open_basedir.

=== Plesk Reply ===

Yes, if the open_basedir option is set to “none” PHP scripts have access to all directories on the server.

Also as was mentioned by my colleague, if the code will be compromised and open_basedir is set to “none” value, this will lead to the bigger damage.

I reproduced the issue in my test environment with “WP Mail SMTP plugin” and also get the following error after mail sending:

PHP Warning: is_readable(): open_basedir restriction in effect. File(C:\Inetpub\vhosts\plesk888.com\httpdocs/wp-content/plugins/C:\Inetpub\vhosts\plesk888.com\httpdocs\wp-content\plugins\wp-mail-smtp/languages/wp-mail-smtp-en_US.mo) is not within the allowed path(s): (C:\) in C:\Inetpub\vhosts\plesk888.com\httpdocs\wp-includes\l10n.php on line 584
From the error above I can conclude that the path duplicates itself, which is not correct.

For further investigation I recommend you to contact “WP Mail SMTP” plugin developers and clarify which path is supposed to be added to the PHP directive. They are experts in this product and will help you to resolve the issue effectively and in short time.

Best regards,
Ivan Kamnev
Technical Support Engineer
Plesk

===

Thanks, Ramsey

Thanks for the reply, I’ll have Plesk look into the issue as you’re telling me this is a server wide miss configuration.

Thanks for the reply Slava,

I’ve tested WP Mail SMTP on a couple of other websites and it throws the same PHP warnings the minute it’s enabled. This does not happen with any other plugs or an alternative SMTP plugin.

The issue maybe correlated to the Plesk Onyx WordPress Tool Kit as each website was install with this tool. The issue seems to be a restriction on .mo file extension.

Path…\wp-includes\l10n.php on line 584

Code on Line 584
if ( !is_readable( $mofile ) ) return false;

===

Additionally, wp-mail-smtp-en_US.mo does not exist at the given path or when I download WP Mail SMTP package directly from https://www.ads-software.com/plugins/wp-mail-smtp/

Path …\wp-content\plugins\wp-mail-smtp/languages/wp-mail-smtp-en_US.mo

===

Hopefully, your able to get this resolved, the plugin works great other then this issue.

• This reply was modified 6 years, 10 months ago by ramseyb.

Hi Matt,

Thanks for looking into this, we recommend WordFence to our clients who have been running it our IIS shared hosting servers without issue for sometime. This issue is already starting to become a problem on our end as we deal with our client’s concerns about why they’re unable to impenitent the new firewall.

I’m not sure exactly how the firewall configuration works, however .htaccess files don’t work and shared hosting accounts run on global server wide php.ini file which they do not have access to, more below in my original post.

https://www.ads-software.com/support/topic/how-to-enable-wordfence-web-application-firewall-on-iis78?replies=2#post-8275348

Ramsey

Thanks for the reply and direction, Brian

Thanks Matt,

“Alert when someone is locked out from login” should hopefully do the trick.

Thanks for the reply Brian,

Email filtering is a good work around, however it would be a great additional to be able to manage an option in WordFence as may clients find it difficult to configure email filtering let alone just the WordFence options.