Quantcast
Channel: WordPress.org Forums » [WP Mail SMTP by WPForms - The Most Popular SMTP and Email Log Plugin] Support
Viewing all 4993 articles
Browse latest View live

block sending email to a specific address

$
0
0

Replies: 0

Hi,

I use I use WP Mail SMTP plugin to send WordPress emails.

I sell digital products. When a customer buys something, he gets automatically an email with his files and another email about his account. Sometimes people type a wrong email by mistake like xxx@gnail.com or xxx@yaho.com.

I use amazon ses stmp to send emails and when someone types a wrong email, I get a notification from amazon ses in my bounce email address that the email is not sent.
This email goes automatically in amazon see global suppression list and after 14 days Amazon SES automatically removes the address from the global suppression list and WordPress tries to send again emails to this wrong address.

This impacts my bounce rate on amazon ses, so I want to know how to block WordPress from sending emails to specific email addresses. I want to take those wrong emails and put them somewhere so WordPress never sends them emails in the future.
Thanks


Problem sending the test email.

$
0
0

Replies: 0

Error: There was a problem while sending the test email.
Host: MediaTemple WordPress
SMTP provider: MailJet

Versions:
WordPress: 5.4
WordPress MS: No
PHP: 7.3.12
WP Mail SMTP: 1.9.0

Params:
Mailer: smtp
Constants: No
ErrorInfo: SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
Host: in-v3.mailjet.com
Port: 587
SMTPSecure: tls
SMTPAutoTLS: bool(true)
SMTPAuth: bool(true)

Server:
OpenSSL: OpenSSL 1.0.1e 11 Feb 2013
SMTP Debug:
2020-04-17 10:31:59 Connection: opening to in-v3.mailjet.com:587, timeout=300, options=array ()

2020-04-17 10:32:00 Connection failed. Error #2: stream_socket_client(): unable to connect to in-v3.mailjet.com:587 (Connection refused) [/var/www/wp-includes/class-smtp.php line 298]

2020-04-17 10:32:00 SMTP ERROR: Failed to connect to server: Connection refused (111)

SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting

Mail with Two Factor Authentification blocked after instilling plugin

$
0
0

Replies: 0

Help!
Suddenly I didn’t receive any messages from my website anymore. After reading that installing a SMTP plugin could help resolve the problem, I installed WP Mail SMTP to try.
But now I don’t receive the emails with the code from my Two Authentification plugin anymore! And without it I am locked out from my WP dashboard…
The WP Mail SMTP plugin must be blocking the Two Authentification mails. How do I disable the WP Mail SMTP plugin when I’m not able to access my WP dashboard anymore??

Gmail Authorization Failure

$
0
0

Replies: 0

Hello,

I was having a few issues here, so I started from scratch. I went all through the gmail settings and was essentially done; however, when I click the big friendly orange “Allow plugin to send emails using your Google Account” button, it pops up with this error:

Authorization Error
Error 400: invalid_request
Invalid parameter value for redirect_uri: Raw IP addresses not allowed:

It looks like it is pulling the authorized redirect URI from above this orange button. I think it would work fine if I could edit that to my domain URL instead of the IP address; however, that field is not editable. Is there any way around this?

cURL error 2: easy handle already used in multi handle

$
0
0

Replies: 4

I’ve had WP Mail SMTP installed and activated on a website I manage using Google
as a mailer for sometime, and just today I am seeing the following error:

Mailer: Gmail
cURL error 2: easy handle already used in multi handle (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)

This error appears every time I try to send a test email using Google as a mailer. I have several other websites using this plugin with Google as a mailer all functioning without issue. Here is the debug error in full:

Versions:
WordPress: 5.4
WordPress MS: No
PHP: 7.3.16
WP Mail SMTP: 1.9.0

Params:
Mailer: gmail
Constants: No
Client ID/Secret: Yes
Auth Code: Yes
Access Token: Yes

Server:
OpenSSL: OpenSSL 1.1.1f 31 Mar 2020
PHP.allow_url_fopen: Yes
PHP.stream_socket_client(): Yes
PHP.fsockopen(): Yes
PHP.curl_version(): 7.69.1

Debug:
Mailer: Gmail
cURL error 2: easy handle already used in multi handle (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)

I haven’t been able to find any previous support requests or discussion topics for this specific error message, and I can’t find any information about what specifically might have caused this error message to suddenly appear in the first place.

Thanks in advance for any help troubleshooting this issue.

for commercial purpose

$
0
0

Replies: 0

can we use this WP Mail SMTP for commercial purpose?

Hide the password

$
0
0

Replies: 0

Hi!

I have the same issue stated here: https://wordpress.org/support/topic/hide-password-in-wp-config-blocks-sending/

I am configuring the emails, and with the password on the field it works, and when I add it to the wp-config.php file it doesn’t work. I am trying with the plugin Test email.

Here are the info details (I edited the domain) when I try to send the test email with the wp-config option:

Versions:
WordPress: 5.4
WordPress MS: No
PHP: 7.3.17
WP Mail SMTP: 1.9.0

Params:
Mailer: smtp
Constants: Yes
ErrorInfo: SMTP Error: Could not authenticate.
Host: send.one.com
Port: 465
SMTPSecure: ssl
SMTPAutoTLS: bool(true)
SMTPAuth: bool(true)

Server:
OpenSSL: OpenSSL 1.1.1 11 Sep 2018
SMTP Debug:
2020-04-18 16:13:58 Connection: opening to ssl://send.one.com:465, timeout=300, options=array ()

2020-04-18 16:13:58 Connection: opened

2020-04-18 16:13:58 SERVER -> CLIENT: 220 mailout1.pub.mailoutpod1-cph3.one.com ESMTP

2020-04-18 16:13:58 CLIENT -> SERVER: EHLO (Mi dominio).com

2020-04-18 16:13:58 SERVER -> CLIENT: 250-mailout1.pub.mailoutpod1-cph3.one.com250-PIPELINING250-SIZE 104857600250-AUTH LOGIN PLAIN250-ENHANCEDSTATUSCODES250 8BITMIME

2020-04-18 16:13:58 CLIENT -> SERVER: AUTH LOGIN

2020-04-18 16:13:58 SERVER -> CLIENT: 334 VXNlcm5hbWU6

2020-04-18 16:13:58 CLIENT -> SERVER: YWNhZGVtaWFAZW1wcmVuZGVkb3Jhc3ltYWRyZXMuY29t

2020-04-18 16:13:58 SERVER -> CLIENT: 334 UGFzc3dvcmQ6

2020-04-18 16:13:58 CLIENT -> SERVER: KE1tPl9tZ19pbXhfZ2dReGU3

2020-04-18 16:13:58 SERVER -> CLIENT: 535 5.7.8 Authentication failed

2020-04-18 16:13:58 SMTP ERROR: Password command failed: 535 5.7.8 Authentication failed

SMTP Error: Could not authenticate.

2020-04-18 16:13:58 CLIENT -> SERVER: QUIT

2020-04-18 16:13:58 SERVER -> CLIENT:

2020-04-18 16:13:58 SMTP ERROR: QUIT command failed:

2020-04-18 16:13:58 Connection: closed

SMTP Error: Could not authenticate.

  • This topic was modified 33 minutes ago by taisa1984.

AWS SES certificate error

$
0
0

Replies: 0

Mailer: Amazon SES
{“curl”:true,”code”:77,”message”:”error setting certificate verify locations:\n CAfile: \/etc\/ssl\/certs\/ca-certificates.crt\n CApath: \/etc\/ssl\/certs”}

root@ip-xxx.xxx.xxx.xxx:/etc/ssl/certs# ls ca-certificates.crt
ca-certificates.crt

This error goes away if I send a test email. The error is reported after sending a newsletter, which is sent using a plugin which we have written.
All the newsletter emails are delivered OK.


compatible with WP 5.4?

$
0
0

Replies: 0

Has this been tested to work succesfully with WordPress 5.4?

Can’t send email

$
0
0

Replies: 0

Here is the error log:

Versions:
WordPress: 5.3.1
WordPress MS: No
PHP: 7.3.15
WP Mail SMTP: 1.8.1

Params:
Mailer: smtp
Constants: No
ErrorInfo: SMTP Error: Could not authenticate.
Host: smtp.aptfd.org
Port: 587
SMTPSecure: string(0) “”
SMTPAutoTLS: bool(false)
SMTPAuth: bool(true)

Server:
OpenSSL: OpenSSL 1.0.2m 2 Nov 2017
SMTP Debug:
2020-04-20 18:57:17 Connection: opening to smtp.aptfd.org:587, timeout=300, options=array ()

2020-04-20 18:57:17 Connection: opened

2020-04-20 18:57:27 SERVER -> CLIENT:

2020-04-20 18:57:27 SMTP NOTICE: EOF caught while checking if connected

2020-04-20 18:57:27 Connection: closed

SMTP Error: Could not authenticate.

SMTP Error: Could not authenticate.

Unable to Send Test Email

$
0
0

Replies: 0

I was able to successfully apply the settings, but when I went to send a test email, I received an error: “There was a problem while sending the test email.”

Error Log
Versions:
WordPress: 5.4
WordPress MS: Yes
PHP: 7.4.4
WP Mail SMTP: 1.9.0

Params:
Mailer: gmail
Constants: No
Client ID/Secret: Yes
Auth Code: Yes
Access Token: Yes

Server:
OpenSSL: OpenSSL 1.0.2k 26 Jan 2017
PHP.allow_url_fopen: Yes
PHP.stream_socket_client(): Yes
PHP.fsockopen(): Yes

PHP Errors in the plugin

$
0
0

Replies: 0

Hi,
I have was not able to use your plugin because I have a site on a server that does a code review using PHP Code Sniffer first. I just wanted to let you know that some errors came back that I think would be pretty easy to solve. In multiple places this is the error we are seeing:

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks)

an example location would be on lines 281 – 284 of plugins/wp-mail-smtp/src/Admin/Pages/SettingsTab.php

code wp config

$
0
0

Replies: 0

hello good this code where would go in wp config???
define( ‘WPMS_SMTP_PASS’, ‘your_old_password’ );

EMAIL DELIVERY ERROR

$
0
0

Replies: 2

Hello,

I’m getting this error and can’t seem to fix it:

===
EMAIL DELIVERY ERROR: the plugin WP Mail SMTP v1.9.0 logged this error during the last time it tried to send an email:

Mailer: Gmail
cURL error 2: easy handle already used in multi handle (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)
Please review your WP Mail SMTP settings in plugin admin area. Consider running an email test after fixing it.
===

I’ve tried recreating the plugin configurations from scratch, but it makes no difference.

Can you help?

Mailgun Api – Reply-to not set?

$
0
0

Replies: 1

Hello,
I use WPForms together with WP Mail SMTP and I am connected to my Mailgun account via WP Mail SMTP.

When eMails are sent via Mailgun, the Reply-To is not set to the field from my Form. However, when I remove the Mailgun integration in WP Mail Smtp and send the contact form again, I can clearly see that the Reply-to field is set.

Does WP Mail SMTP does not set the Reply-To correctly in the Mailgun API connection?

http://documentation.mailgun.com/en/latest/api-sending.html#sending

-> h:X-My-Header h: prefix followed by an arbitrary value allows to append a custom MIME header to the message (X-My-Header in this case). For example, h:Reply-To to specify Reply-To address.

Thanks.


Error 404 Test Mail

Unable to send emails

$
0
0

Replies: 1

P.S.: I have double-checked the password multiple times.

Error log:

Versions:
WordPress: 5.4
WordPress MS: No
PHP: 7.4.2
WP Mail SMTP: 1.9.0

Params:
Mailer: smtp
Constants: No
ErrorInfo: SMTP Error: Could not authenticate.
Host: smtp.gmail.com
Port: 465
SMTPSecure: ssl
SMTPAutoTLS: bool(true)
SMTPAuth: bool(true)

Server:
OpenSSL: OpenSSL 1.0.2o 27 Mar 2018
Apache.mod_security: No
SMTP Debug:
2020-04-23 14:46:38 Connection: opening to ssl://smtp.gmail.com:465, timeout=300, options=array ()

2020-04-23 14:46:38 Connection: opened

2020-04-23 14:46:38 SERVER -> CLIENT: 220 smtp.gmail.com ESMTP o15sm2294220pgj.60 – gsmtp

2020-04-23 14:46:38 CLIENT -> SERVER: EHLO localhost

2020-04-23 14:46:38 SERVER -> CLIENT: 250-smtp.gmail.com at your service, [115.99.82.152]250-SIZE 35882577250-8BITMIME250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH250-ENHANCEDSTATUSCODES250-PIPELINING250-CHUNKING250 SMTPUTF8

2020-04-23 14:46:38 CLIENT -> SERVER: AUTH LOGIN

2020-04-23 14:46:39 SERVER -> CLIENT: 334 VXNlcm5hbWU6

2020-04-23 14:46:39 CLIENT -> SERVER: aW5mb0B1bHRyYXdpcmVkLmlu

2020-04-23 14:46:39 SERVER -> CLIENT: 334 UGFzc3dvcmQ6

2020-04-23 14:46:39 CLIENT -> SERVER: VWx0cmFXaXJlZDE1JQ==

2020-04-23 14:46:39 SERVER -> CLIENT: 535-5.7.8 Username and Password not accepted. Learn more at535 5.7.8 https://support.google.com/mail/?p=BadCredentials o15sm2294220pgj.60 – gsmtp

2020-04-23 14:46:39 SMTP ERROR: Password command failed: 535-5.7.8 Username and Password not accepted. Learn more at535 5.7.8 https://support.google.com/mail/?p=BadCredentials o15sm2294220pgj.60 – gsmtp

SMTP Error: Could not authenticate.

2020-04-23 14:46:39 CLIENT -> SERVER: QUIT

2020-04-23 14:46:40 SERVER -> CLIENT: 221 2.0.0 closing connection o15sm2294220pgj.60 – gsmtp

2020-04-23 14:46:40 Connection: closed

SMTP Error: Could not authenticate.

Error sending email WP v5.4.0

$
0
0

Replies: 0

Hi,

I’m having a problem sending an email out from my site. It seems like there is something wrong with the sender’s email. It worked fine when checking Force From Email.

Thanks

Versions:
WordPress: 5.4
WordPress MS: No
PHP: 7.3.17
WP Mail SMTP: 1.9.0

Params:
Mailer: smtp
Constants: No
ErrorInfo: Invalid address: (setFrom) wordpress@
Host: localhost
Port: 25
SMTPSecure: string(0) “”
SMTPAutoTLS: bool(true)
SMTPAuth: bool(false)

Server:
OpenSSL: OpenSSL 1.1.1d 10 Sep 2019
SMTP Debug:
Invalid address: (setFrom) wordpress@

  • This topic was modified 3 hours, 48 minutes ago by jayakornk.
  • This topic was modified 3 hours, 47 minutes ago by jayakornk.

Unable to send an email

$
0
0

Replies: 0

Hi,

I couldn’t send an email out from my site. But it worked if I checked Force From Email.

Thank you.

Versions:
WordPress: 5.4
WordPress MS: No
PHP: 7.3.17
WP Mail SMTP: 1.9.0

Params:
Mailer: smtp
Constants: No
ErrorInfo: Invalid address: (setFrom) wordpress@
Host: localhost
Port: 25
SMTPSecure: string(0) “”
SMTPAutoTLS: bool(true)
SMTPAuth: bool(false)

Server:
OpenSSL: OpenSSL 1.1.1d 10 Sep 2019
SMTP Debug:
Invalid address: (setFrom) wordpress@

Site down

$
0
0

Replies: 0

Uncaught Error: Call to undefined method WPMailSMTP\Core::get_site_health() in /var/www/html/wp-content/plugins/wp-mail-smtp/src/Core.php:195

wp-config.php


<?php
define('WP_CONTENT_DIR', '/var/www/html/wp-content');
$table_prefix = getenv('TABLE_PREFIX') ?: 'wp_';
foreach ($_ENV as $key => $value) {
    $capitalized = strtoupper($key);
    if (!defined($capitalized)) {
        define($capitalized, $value);
    }
}

// wp-smtp
define( 'WPMS_ON', true );
define( 'WPMS_MAIL_FROM_FORCE', true );
Viewing all 4993 articles
Browse latest View live