Smtp error rcpt to command failed

PHPmailer appears not to be attempting to authenticate SMTP #880

I am tearing my hair out trying to get SMTP authentication to work. It appears PHPmailer is making no attempt to send the username/password specified. I’ve closely followed the examples, and am using the latest PHPmailer.

The SMTP server, authentication username/password, port 465 for SSL encryption, are exactly the same as used by my mail server which runs perfectly. I have tried setting $mail->SMTPAutoTLS = false & true, no difference.

I would appreciate any comments that might help me resolve the problem

SETTINGS no TLS:

Host = [host2.axxesslocal.co.za]
SMTPAuth = [1]
SMTPsecure = []
Port = [25]
Username = [neilf@megapulsesa.com]
Password = [xxxxxxx]
Hostname = []
SetFrom = [neilf@megapulsesa.com]
AddReplyTo = [NeilF@megapulsesa.com]
AddAddress = [neilafraser@gmail.com]
SMTPDebug = [2]

CLIENT -> SERVER: EHLO www.megapulsesa.com
SERVER -> CLIENT: 250-host2.axxesslocal.co.za Hello axxess33.dedicated.co.za [154.0.168.117]250-SIZE 52428800250-8BITMIME250-PIPELINING250-AUTH PLAIN LOGIN250-STARTTLS250 HELP
CLIENT -> SERVER: MAIL FROM:neilf@megapulsesa.com
SERVER -> CLIENT: 250 OK
CLIENT -> SERVER: RCPT TO:neilafraser@gmail.com
SERVER -> CLIENT: 550-Please turn on SMTP Authentication in your mail client. 550-axxess33.dedicated.co.za (www.megapulsesa.com) [154.0.168.117]:55882 is not550 permitted to relay through this server without authentication.
SMTP ERROR: RCPT TO command failed: 550-Please turn on SMTP Authentication in your mail client. 550-axxess33.dedicated.co.za (www.megapulsesa.com) [154.0.168.117]:55882 is not550 permitted to relay through this server without authentication.
CLIENT -> SERVER: QUIT
SERVER -> CLIENT: 221 host2.axxesslocal.co.za closing connection
SMTP Error: The following recipients failed: neilafraser@gmail.com: Please turn on SMTP Authentication in your mail client. axxess33.dedicated.co.za (www.megapulsesa.com) [154.0.168.117]:55882 is notpermitted to relay through this server without authentication.

SETTINGS with TLS:

Host = [host2.axxesslocal.co.za]
SMTPAuth = [1]
SMTPsecure = [tls]
Port = [587]
Username = [neilf@megapulsesa.com]
Password = [xxxxxxx]
Hostname = []
SetFrom = [neilf@megapulsesa.com]
AddReplyTo = [NeilF@megapulsesa.com]
AddAddress = [neilafraser@gmail.com]
SMTPDebug = [2]

SERVER -> CLIENT: 220-host2.axxesslocal.co.za ESMTP Exim 4.87 #1 Fri, 11 Nov 2016 09:42:52 +0200 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.
CLIENT -> SERVER: EHLO www.megapulsesa.com
SERVER -> CLIENT: 250-host2.axxesslocal.co.za Hello axxess33.dedicated.co.za [154.0.168.117]250-SIZE 52428800250-8BITMIME250-PIPELINING250-AUTH PLAIN LOGIN250-STARTTLS250 HELP
CLIENT -> SERVER: MAIL FROM:neilf@megapulsesa.com
SERVER -> CLIENT: 250 OK
CLIENT -> SERVER: RCPT TO:neilafraser@gmail.com
SERVER -> CLIENT: 550 SMTP AUTH is required for message submission on port 587
SMTP ERROR: RCPT TO command failed: 550 SMTP AUTH is required for message submission on port 587
CLIENT -> SERVER: QUIT
SERVER -> CLIENT:
SMTP ERROR: QUIT command failed:
SMTP Error: The following recipients failed: neilafraser@gmail.com: SMTP AUTH is required for message submission on port 587

$pop = new POP3() ;
$pop->Authorise ($Host, 110, 30, $EUsername, $EPassword, 1);
// alternatively this does the same as the above, but makes no difference:
// $pop = POP3::popBeforeSmtp($Host, 110, 30, $EUsername, $EPassword, 1);

Array
(
[error] => Connecting to the POP3 server raised a PHP warning:
[errno] => 2
[errstr] => fsockopen(): php_network_getaddresses: getaddrinfo failed: Name or service not known
[errfile] => /home/megapuls/public_html/PHPMailer-master/class.pop3.php
[errline] => 229
)
Array
(
[error] => Failed to connect to server on port 110
[errno] => 0
[errstr] => php_network_getaddresses: getaddrinfo failed: Name or service not known
)

The text was updated successfully, but these errors were encountered:

Источник

Command RCPT failed

This Error Event is part of Send Email Events.

Event ID · 50461

Overview

The error indicates that the SMTP server has not accepted the recipient’s email address.

Cause

The Command RCPT failed error indicates that the SMTP server has not accepted the email recipient’s address. Some possible causes are that:

• The email address is not in valid format.
• The SMTP server is limiting the scope of allowed recipients.
• Provided FROM address is not allowed.
• Most likely, the user authentication is required.

Event examples

See some examples of the Command RCPT failed Event messages:

• Couldn’t send message, Server Response: 550 Relaying is prohibited.
• 550 5.7.1 Unable to relay.
• 550 Relaying denied.
• 554 Relay access denied.
• 554 5.2.252 STOREDRV.Submission.Exception:SendAsDeniedException.MapiExceptionSendAsDenied; Failed to process message due to a permanent exception with message Cannot submit message … [Hostname=EC9R981NB1000.USRP198.PROD.OUTLOOK.COM] 250 2.1.0

Solution

If the error returns an error message similar to those above, it means that authentication with the SMTP server is required and thus has to be configured properly. Go to the Email tab of Automation Workshop Options (accessible from the Tools menu) and make sure that a Username, Password and Authentication method are correctly specified.

If unsure about SMTP server parameters or would like to use Gmail as SMTP, read more on SMTP server configuration.

Summary

Common causes of the SMTP error:

• FROM address not allowed (you must use the same address as for authentication).
• TO address not permitted.
• Authentication required to send outside your organization.
• SSL or TLS encrypted connection required to send emails.

Источник

5 causes for “SMTP error from remote mail server after RCPT TO” error, and the fixes

Email errors can be really bothersome – they can hit you hard and unexpected, when you attempt to send an urgent mail.

As part of our Server Support services for web hosting providers, we resolve email errors faced by website owners.

One commonly encountered email error is “SMTP error from remote mail server after RCPT TO”. It shows up when users try to send mails to other email accounts.

What is the error “SMTP error from remote mail server after RCPT TO”?

This error message is a very confusing one, as it can be triggered due to a number of causes. But usually the bounce message that arrives contains the details about the error.

The RCPT command is used to tell the sender mail server, who the recipient of your message is. The error message denotes that the sending mail server faced an error during that command, while trying to send mails.

To know the exact reason for the error, we examine the entire bounce message that the sender receives. And here are some of the major causes we’ve identified.

“SMTP error from remote mail server after RCPT TO” error – Causes & Fixes!

Mail server configuration issue or blacklisting, anything can cause a mail delivery error. We’ll see how to relate to the cause, from the error message we get.

1. Configuration errors

Cause: The authentication errors mostly occur due to mail client or mail form configuration settings. If you try to send mails without proper authentication of your mail account, the mail server throws this error.

The authentication error also occurs when there is any mail server configuration issue – like domain not present in localdomains file or MX record mismatches.

Fix: The mail client settings should be properly configured with mail account details, SMTP server and port number. For PHP mail forms, using SMTP authentication to send out mails can help resolve this error.

To resolve mail server configuration errors, we examine the mail logs, MX records and related configuration files, and fix the discrepancies that are found in them.

2. Domain blacklists

Cause: RBLs aka blacklists are used by mail servers to prevent inbound spamming. When blacklist providers such as Spamhaus suspect your mail server as a spam origin, they will blacklist your server IP.

Getting blacklisted indicates that your server had a spammer or someone who is sending mass mails. Many times, server owners get to know about it only when users complain about mail errors.

Fix: Once blacklisted, getting de-listed is a time-consuming procedure. Pinpointing the source of spam and fixing it is the most important step. Then you need to request RBL to remove you from the list.

To ensure seamless mail delivery, it is important to avoid getting blacklisted. At Bobcares, we proactively secure the mail server and keep constant vigil on them to avoid all spamming activities that can cause the server to get blacklisted.

3. RDNS misconfiguration

Cause: RDNS pointer records are used to map IP to hostname and it helps to validate a server. Many mail servers reject incoming mails from servers without proper RDNS records.

Fix: Setting RDNS records for the sending mail server helps to avoid such errors. At Bobcares, we configure critical mail records such as RDNS, SPF, DKIM, etc to ensure that mail delivery errors are avoided.

4. Recipient errors

Cause: The mail delivery error ‘SMTP error from remote mail server after RCPT TO:’, can be caused by a range of issues at the recipient mail server.

These include missing or suspended recipient email account, incorrect MX records, custom blacklists or filters configured at the recipient email account, which cause mails to bounce back to sender.

Fix: The MX records of the recipient domain should be tested and confirmed to be working fine. For resolving issues at recipient end, you need to contact the remote mail server with these inputs.

5. Sender errors

Cause: A sender error can be caused due to many factors. The prominent reasons we have seen in our role as Website Support Techs for web hosting companies, include:

a. Duplicate sender account present in the recipient server
b. Misconfigured mail configuration settings
c. Sender email account doesn’t exist or cannot be detected
d. Permission issues caused by server migrations, updates or custom scripts

Fix: To resolve sender errors, we examine the mail server logs, sender email account settings, folder permissions, mail server configuration, etc. and resolve any issues related to that.

At Bobcares, our custom checklists for migrations and updates enable us to avoid any related issues that may pop up. We also audit the mail server settings periodically and reconfigure the ‘Email Routing’ as appropriate.

Conclusion

“SMTP error from remote mail server after RCPT TO” error is a common error that affects email delivery. Here we’ve discussed five major causes our Server Support Engineers have seen and how we fix it.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

I can’t seem to fix this error and it’s really disturbing me

Hello Joseph,
Our experts can fix the error for you. We’ll be happy to talk to you on chat (click on the icon at right-bottom).

Hello
I met the same issue and hope to fix this,
Please contact me and let me know how to fix this issue.
thanks

Hello,
We need to take a closer look at your Mail server settings. If you still have errors and need help, we’ll be happy to talk to you on chat (click on the icon at right-bottom).

Hello
I facing the 421 and 550.1 error and hope to fix this,
Please contact me and let me know how to solve this issue.
thanks

Our Experts can help you with the issue, we’ll be happy to talk to you on chat (click on the icon at right-bottom).

Источник

command failed: 454 4.7.1 #329

I’m using this script on my site hosted on unoeuro.com. They told me to disable SMTPAuth which I did, and it works fine when I’m sending an e-mail to myself (the e-mail belonging to the domain).

When I tried to send a mail to mail-tester.com’s service or any other e-mail not from the domain I get command fail: 454 4.7.1.

I’ve tried to Google it, but didn’t find any solution how to resolve it on PHPMailer, so I hope that someone in here can help me.

Best regards
Jonathan

The text was updated successfully, but these errors were encountered:

4.7.1 is a temporary failure due to spam filtering or other policy — it’s likely that this is an authentication problem as allowing to send from anywhere to anywhere is effectively a spam gateway. Can you show the SMTP transcript (set SMTPDebug = 2 )?

OK, that does look like a normal trying to send without authenticating. Notice that the server capability list does not include AUTH, but does include STARTTLS? I would guess that if you set SMTPSecure = ‘tls’ and Port = 587 , you will find that authentication works. This is because after sending STARTTLS, the client issues EHLO again, and the server typically only allows authentication after an encrypted connection has been established.

My host told me that the port should be 25.

But i tried this (correct?):

$mail->SMTPDebug = 2;
//Ask for HTML-friendly debug output
$mail->Debugoutput = ‘html’;
//Set the hostname of the mail server
$mail->Host = «mail.jaalumni.dk»;
//Set the SMTP port number — likely to be 25, 465 or 587
$mail->SMTPSecure = ‘tls’;
$mail->Port = 587;
//Whether to use SMTP authentication
$mail->SMTPAuth = false;

ect ect.

I get this error:

SMTP ERROR: Failed to connect to server: Connection refused (111)
SMTP connect() failed.
Mailer Error: SMTP connect() failed.

Hm. I’ve done a little experiment and it doesn’t look like they support authentication at all — starting TLS on that server does not show an an AUTH option.

Overall it looks like this is an inbound-only mail server, which is why it works for your own domain but not others. The only other way they can reasonably let you relay through here is if they trust your IP address. I think they must have a different server for authenticated outbound to arbitrary addresses.

Weird — it was them who suggested to use PHPMailer, so I guess there must be a solution somewhere.

I don’t think this is specific to PHPMailer — I expect you would have the same problem with any other sending software. Do you send through this server using other software, such as Outlook or Apple Mail?

Источник

Overview

The error indicates that the SMTP server has not accepted the recipient’s email address.

Cause

The Command RCPT failed error indicates that the SMTP server has not accepted the email recipient’s address. Some possible causes are that:

• The email address is not in valid format.
• The SMTP server is limiting the scope of allowed recipients.
• Provided FROM address is not allowed.
• Most likely, the user authentication is required.

Solution

If the error returns a message similar to those above, it means that authentication with the SMTP server is required and thus has to be configured properly. Go to the Email tab of Automation Workshop Options (accessible from the Tools menu) and make sure that a Username, Password and Authentication method are correctly specified.

If unsure about SMTP server parameters or would like to use Gmail as SMTP, read more on SMTP server configuration.

Summary

Common causes of the SMTP error:

• FROM address not allowed (you must use the same address as for authentication).
• TO address not permitted.
• Authentication required to send outside your organization.
• SSL or TLS encrypted connection required to send emails.

More relaying debugging…

• Test SMTP connection and send test email
• AW Event 50463 · An unexpected response after end-of-mail indicator
• AW Event 2501 · Could not send notification email
• Command Line Email relaying access denied
• Gmail Workspace SMTP error reference
• Microsoft Office 365 authentication issues

Need assistance?

If you have any questions, please do not hesitate to contact our support team.

I wrote an app based on PHPMailer that reads a CSV and retrieves the names and email addresses for the recipients (each recipient has a row) and sends emails to them and BCCs the emails to my work address (the same one as the one that sends the emails). It manages to send about 4-5 emails after which it starts returning errors, the most frequent being «SMTP connect() failed».

I use the SMTP server provided by Aruba Italy — smtp.aruba.it, the one set up for our company email . Its limitations were confirmed to me by the representatives of the company and are max 250 emails sent every 20 minutes and no more than 3-4 simultaneous SMTP connections. Every time I used the app, I sent less than 100 emails in one batch and delayed every other email by one second to not have multiple SMTP connections opened at the same time.

I turned on debugging and read the errors returned but I do not really know how to interpret them. I pasted a few below.

Could anyone please help me determine what my problem is and how to repair it?

Than you.

2016-12-21 14:19:24 CLIENT -> SERVER: MAIL FROM: 
2016-12-21 14:19:24 SERVER -> CLIENT: 250 2.1.0 sender ok 
2016-12-21 14:19:24 CLIENT -> SERVER: RCPT TO: 
2016-12-21 14:19:24 SERVER -> CLIENT: 250 2.1.5 recipient ok 
2016-12-21 14:19:24 CLIENT -> SERVER: RCPT TO:
2016-12-21 14:19:24 SERVER -> CLIENT: 452 4.1.1 NeKD1u00T1ustzm01eKRZu policy violation 
2016-12-21 14:19:24 SMTP ERROR: RCPT TO command failed: 452 4.1.1 NeKD1u00T1ustzm01eKRZu policy violation 
2016-12-21 14:19:24 CLIENT -> SERVER: DATA
2016-12-21 14:19:24 SERVER -> CLIENT: 
2016-12-21 14:19:24 SMTP ERROR: DATA command failed: 
2016-12-21 14:19:24 SMTP Error: data not accepted. 
Message could not be sent.
Mailer Error: SMTP Error: data not accepted.SMTP server error: DATA command failed
------------------------------------------------------------------------------

2016-12-21 14:36:30 CLIENT -> SERVER: MAIL FROM: 
2016-12-21 14:36:30 SERVER -> CLIENT: 250 2.1.0 sender ok 
2016-12-21 14:36:30 CLIENT -> SERVER: RCPT TO: 
2016-12-21 14:36:30 SERVER -> CLIENT: 452 4.1.1 Nec11u00u1ustzm01ecWgz policy violation 
2016-12-21 14:36:30 SMTP ERROR: RCPT TO command failed: 452 4.1.1 Nec11u00u1ustzm01ecWgz policy violation 2
016-12-21 14:36:30  CLIENT -> SERVER: RSET 
2016-12-21 14:36:30 SERVER -> CLIENT: 
2016-12-21 14:36:30 SMTP ERROR: RSET command failed: 
2016-12-21 14:36:30 SMTP Error: The following recipients failed: [recipient's email address]: Nec11u00u1ustzm01ecWgz policy violation 
Message could not be sent.
Mailer Error: SMTP Error: The following recipients failed: [recipient's email address]: Nec11u00u1ustzm01ecWgz policy violation SMTP server error: RSET command failed
------------------------------------------------------------------------------

2016-12-21 14:36:31 SMTP NOTICE: EOF caught while checking if connected 
2016-12-21 14:36:31 Connection: closed 
2016-12-21 14:36:31 Connection: opening to ssl://smtps.aruba.it:465, timeout=300, options=array ( ) 
2016-12-21 14:36:31 Connection: opened 
2016-12-21 14:36:31 SERVER -> CLIENT: 421 smtpcmd05.ad.aruba.it bizsmtp NecX1u00y1ustzm01 policy violation 
2016-12-21 14:36:31 CLIENT -> SERVER: EHLO localhost 
2016-12-21 14:36:31 SERVER -> CLIENT: 503 not available 
2016-12-21 14:36:31 SMTP ERROR: EHLO command failed: 503 not available 
2016-12-21 14:36:31 CLIENT -> SERVER: HELO localhost 
2016-12-21 14:36:31 SERVER -> CLIENT: 503 not available 
2016-12-21 14:36:31 SMTP ERROR: HELO command failed: 503 not available 
2016-12-21 14:36:31 SMTP Error: Could not authenticate. 
2016-12-21 14:36:31 CLIENT -> SERVER: QUIT 
2016-12-21 14:36:31 SERVER -> CLIENT: 221 2.0.0 smtpcmd05.ad.aruba.it bizsmtp closing connection 
2016-12-21 14:36:31 Connection: closed 
2016-12-21 14:36:31 SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting 
Message could not be sent.
Mailer Error: SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
------------------------------------------------------------------------------

2016-12-21 14:36:32 Connection: opening to ssl://smtps.aruba.it:465, timeout=300, options=array ( ) 
2016-12-21 14:36:33 Connection: opened 
2016-12-21 14:36:33 SERVER -> CLIENT: 421 smtpcmd05.ad.aruba.it bizsmtp NecZ1u00g1ustzm01 policy violation 
2016-12-21 14:36:33 CLIENT -> SERVER: EHLO localhost 
2016-12-21 14:36:33 SERVER -> CLIENT: 503 not available 
2016-12-21 14:36:33 SMTP ERROR: EHLO command failed: 503 not available 
2016-12-21 14:36:33 CLIENT -> SERVER: HELO localhost 
2016-12-21 14:36:33 SERVER -> CLIENT: 503 not available 
2016-12-21 14:36:33 SMTP ERROR: HELO command failed: 503 not available 
2016-12-21 14:36:33 SMTP Error: Could not authenticate. 
2016-12-21 14:36:33 CLIENT -> SERVER: QUIT 
2016-12-21 14:36:33 SERVER -> CLIENT: 221 2.0.0 smtpcmd05.ad.aruba.it bizsmtp closing connection 
2016-12-21 14:36:33 Connection: closed 
2016-12-21 14:36:33 SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting 
Message could not be sent.
Mailer Error: SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting
------------------------------------------------------------------------------

2016-12-21 14:40:46 CLIENT -> SERVER: MAIL FROM: 
2016-12-21 14:40:46 SERVER -> CLIENT: 
2016-12-21 14:40:46 SMTP ERROR: MAIL FROM command failed: 
2016-12-21 14:40:46 The following From address failed: [sender's email address] : MAIL FROM command failed,,,SMTP server error: MAIL FROM command failed 
Message could not be sent.
Mailer Error: The following From address failed: [sender's email address]: MAIL FROM command failed,,,SMTP server error: MAIL FROM command failedSMTP server error: MAIL FROM command failed

Basically I am trying to save an error log in my database table which recipients failed/reach is over quota/disabled etc. But I am unable to do that. As per your instruction and my knowledge I did it like below-
Step-1: I created a class file named MyPHPMailer.php and saved with your code.

<?php

require 'PHPMailer.php';

use PHPMailerPHPMailerPHPMailer;

class MyPHPMailer extends PHPMailer {
    public $bad_rcpt = array();
    protected function smtpSend($header, $body)
    {
        $this->bad_rcpt = array();

        if (!$this->smtpConnect()) {
            throw new phpmailerException($this->lang('smtp_connect_failed'), self::STOP_CRITICAL);
        }
        $smtp_from = ($this->Sender == '') ? $this->From : $this->Sender;
        if (!$this->smtp->mail($smtp_from)) {
            $this->setError($this->lang('from_failed') . $smtp_from . ' : ' . implode(',', $this->smtp->getError()));
            throw new phpmailerException($this->ErrorInfo, self::STOP_CRITICAL);
        }

        // Attempt to send to all recipients
        foreach ($this->to as $to) {
            if (!$this->smtp->recipient($to[0])) {
                $this->bad_rcpt[] = $to[0];
                $isSent = false;
            } else {
                $isSent = true;
            }
            $this->doCallback($isSent, array($to[0]), array(), array(), $this->Subject, $body, $this->From);
        }
        foreach ($this->cc as $cc) {
            if (!$this->smtp->recipient($cc[0])) {
                $this->bad_rcpt[] = $cc[0];
                $isSent = false;
            } else {
                $isSent = true;
            }
            $this->doCallback($isSent, array(), array($cc[0]), array(), $this->Subject, $body, $this->From);
        }
        foreach ($this->bcc as $bcc) {
            if (!$this->smtp->recipient($bcc[0])) {
                $this->bad_rcpt[] = $bcc[0];
                $isSent = false;
            } else {
                $isSent = true;
            }
            $this->doCallback($isSent, array(), array(), array($bcc[0]), $this->Subject, $body, $this->From);
        }

        // Only send the DATA command if we have viable recipients
        if ((count($this->all_recipients) > count($this->bad_rcpt)) and !$this->smtp->data($header . $body)) {
            throw new phpmailerException($this->lang('data_not_accepted'), self::STOP_CRITICAL);
        }
        if ($this->SMTPKeepAlive == true) {
            $this->smtp->reset();
        } else {
            $this->smtp->quit();
            $this->smtp->close();
        }
        if (count($this->bad_rcpt) > 0) { // Create error message for any bad addresses
            throw new phpmailerException(
                $this->lang('recipients_failed') . implode(', ', $this->bad_rcpt),
                self::STOP_CONTINUE
            );
        }
        return true;
    }
}
?>

Step-2: Next I included class file in sendemail.php like below

<?php
error_reporting(E_ALL);
ini_set('display_errors', true);

require 'PHPMailer/src/Exception.php';
require 'PHPMailer/src/SMTP.php';
require 'PHPMailer/src/MyPHPMailer.php';

use PHPMailerPHPMailerPHPMailer;
use PHPMailerPHPMailerException;

$bccz = array(
    array(
        'a@example.com' => array(
            'email' => 'a@example.com',
            'cFname' => 'firstname',
            'cLname' => 'lastname'
        ),
        'b@example-.com' => array(
            'email' => 'b@example-.com', //Deliberately invalid
            'cFname' => 'firstname',
            'cLname' => 'lastname'
        )
    ),
    array(
        'c@dfgsdfgdsfgsdfgsdfgsdfgs.com' => array(
            'email' => 'c@dfgsdfgdsfgsdfgsdfgsdfgs.com', //Non-existent domain
            'cFname' => 'firstname',
            'cLname' => 'lastname'
        ),
        'd@example.com' => array(
            'email' => 'd@example.com',
            'cFname' => 'firstname',
            'cLname' => 'lastname'
        )
    )
);

$mail = new MyPHPMailer;
$mail->IsSMTP();
$mail->Host = 'localhost';
$mail->Port = 25;
$mail->SMTPAuth = false;
$mail->CharSet = 'UTF-8';
$mail->setFrom('from@example.com', 'FromName');
$mail->addAddress('to@example.com', 'ToName');
$mail->msgHTML('This is the message body');
$mail->Subject = 'Subject';
$i = 0;

foreach ($bccz as $bcc) {
    $i++;
    echo '<h2>GROUP: ' . $i . '</h2>' . "n";
    foreach ($bcc as $key => $value) {
        try {
            $mail->AddBcc($value['email'], trim($value['cFname'] . ' ' . $value['cLname']));
        } catch (phpmailerException $e) {
            echo "Skipping invalid address: {$value['email']}n";
        }
    }
    try {
        $mail->Send();
        echo "message sent hurray!n";
    } catch (phpmailerException $e) {
        echo $e->errorMessage();
    }
    $mail->ClearBCCs();
}

var_dump($mail->bad_rcpt);
?>

I got the result below-

GROUP: 1

Fatal error: Uncaught Error: Class 'phpmailerException' not found in C:xampphtdocssendemailPHPMailersrcMyPHPMailer.php:14 Stack trace: #0 C:xampphtdocssendemailPHPMailersrcPHPMailer.php(1529): MyPHPMailer->smtpSend('Date: Mon, 4 Ma...', 'This is a multi...') #1 C:xampphtdocssendemailPHPMailersrcPHPMailer.php(1365): PHPMailerPHPMailerPHPMailer->postSend() #2 C:xampphtdocssendemailtest.php(62): PHPMailerPHPMailerPHPMailer->send() #3 {main} thrown in C:xampphtdocssendemailPHPMailersrcMyPHPMailer.php on line 14

What should I do now? I will be happy if you correction my mentioned code and clarify me.
Note: I am using latest version of PHPMailer 6.0.7
Thanks again.

Email errors can be really bothersome – they can hit you hard and unexpected, when you attempt to send an urgent mail.

As part of our Server Support services for web hosting providers, we resolve email errors faced by website owners.

One commonly encountered email error is “SMTP error from remote mail server after RCPT TO”. It shows up when users try to send mails to other email accounts.

What is the error “SMTP error from remote mail server after RCPT TO”?

This error message is a very confusing one, as it can be triggered due to a number of causes. But usually the bounce message that arrives contains the details about the error.

The RCPT command is used to tell the sender mail server, who the recipient of your message is. The error message denotes that the sending mail server faced an error during that command, while trying to send mails.

To know the exact reason for the error, we examine the entire bounce message that the sender receives. And here are some of the major causes we’ve identified.

“SMTP error from remote mail server after RCPT TO” error – Causes & Fixes!

Mail server configuration issue or blacklisting, anything can cause a mail delivery error. We’ll see how to relate to the cause, from the error message we get.

1. Configuration errors

SMTP error from remote mail server after RCPT TO::
host domain.com [xx.xx.xx.xx]: 550-Please turn on SMTP Authentication in your mail client.
550-(host.domain.com) [yy.yy.yy.yy]: __ is not permitted to relay through this server without authentication.

Cause: The authentication errors mostly occur due to mail client or mail form configuration settings. If you try to send mails without proper authentication of your mail account, the mail server throws this error.

The authentication error also occurs when there is any mail server configuration issue – like domain not present in localdomains file or MX record mismatches.

Fix: The mail client settings should be properly configured with mail account details, SMTP server and port number. For PHP mail forms, using SMTP authentication to send out mails can help resolve this error.

To resolve mail server configuration errors, we examine the mail logs, MX records and related configuration files, and fix the discrepancies that are found in them.

2. Domain blacklists

SMTP error from remote mail server after RCPT TO::
host domain.com [xx.xx.xx.xx]: 550-"JunkMail rejected - host.domain.com [yy.yy.yy.yy]: 
___ is in an RBL, see http://www.spamhaus.org/query/bl?ip=________"

SMTP error from remote mail server after RCPT TO:: host host.domain.com [xx.xx.xx.xx]: 
554 5.7.1 Service unavailable; Client host [yy.yy.yy.yy] blocked using zen.spamhaus.org; http://www.spamhaus.org

Cause: RBLs aka blacklists are used by mail servers to prevent inbound spamming. When blacklist providers such as Spamhaus suspect your mail server as a spam origin, they will blacklist your server IP.

Getting blacklisted indicates that your server had a spammer or someone who is sending mass mails. Many times, server owners get to know about it only when users complain about mail errors.

Fix: Once blacklisted, getting de-listed is a time-consuming procedure. Pinpointing the source of spam and fixing it is the most important step. Then you need to request RBL to remove you from the list.

To ensure seamless mail delivery, it is important to avoid getting blacklisted. At Bobcares, we proactively secure the mail server and keep constant vigil on them to avoid all spamming activities that can cause the server to get blacklisted.

3. RDNS misconfiguration

SMTP error from remote mail server after RCPT TO::
host mx.domain.com [xx.xx.xx.xx]: 554 5.7.1 :
Client host rejected: envelope policy RBL PTRNUL

Cause: RDNS pointer records are used to map IP to hostname and it helps to validate a server. Many mail servers reject incoming mails from servers without proper RDNS records.

Fix: Setting RDNS records for the sending mail server helps to avoid such errors. At Bobcares, we configure critical mail records such as RDNS, SPF, DKIM, etc to ensure that mail delivery errors are avoided.

4. Recipient errors

SMTP error from remote mail server after RCPT TO: :
552 5.1.1  Mailbox delivery failure policy error

SMTP error from remote mail server after RCPT TO:
550 5.1.1 xxxxxxxx Recipient Suspended (TT999)

SMTP error from remote mail server after RCPT TO::
550 5.1.1  Recipient not found.

SMTP error from remote mail server after RCPT TO::
host mx.domain.com [xx.xx.xx.xx]: 550 Requested action not taken: mailbox unavailable

Cause: The mail delivery error ‘SMTP error from remote mail server after RCPT TO:’, can be caused by a range of issues at the recipient mail server.

These include missing or suspended recipient email account, incorrect MX records, custom blacklists or filters configured at the recipient email account, which cause mails to bounce back to sender.

Fix: The MX records of the recipient domain should be tested and confirmed to be working fine. For resolving issues at recipient end, you need to contact the remote mail server with these inputs.

5. Sender errors

SMTP error from remote mail server after RCPT  TO::
host host.domain.com [xx.xx.xx.xx]: 554 5.1.8  :
Sender address rejected: Domain not found

SMTP error from remote mail server after RCPT TO::
host mx.server.com [xxx.xxx.xxx.xxx]: 550-Verification failed for 
550-No Such User Here : Sender verify failed

Cause: A sender error can be caused due to many factors. The prominent reasons we have seen in our role as Website Support Techs for web hosting companies, include:

a. Duplicate sender account present in the recipient server
b. Misconfigured mail configuration settings
c. Sender email account doesn’t exist or cannot be detected
d. Permission issues caused by server migrations, updates or custom scripts

Fix: To resolve sender errors, we examine the mail server logs, sender email account settings, folder permissions, mail server configuration, etc. and resolve any issues related to that.

At Bobcares, our custom checklists for migrations and updates enable us to avoid any related issues that may pop up. We also audit the mail server settings periodically and reconfigure the ‘Email Routing’ as appropriate.

Conclusion

“SMTP error from remote mail server after RCPT TO” error is a common error that affects email delivery. Here we’ve discussed five major causes our Server Support Engineers have seen and how we fix it.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;