Error of command sending rcpt to

Всем привет,
использую стандартный класс для отправки через yandex smtp, письма которые приходят:
в адресе Кому:undisclosed-recipients:;
как обойти это?

Класс отправки:

<?php
namespace module;

class SendMail {

public $smtp_username;
public $smtp_password;
public $smtp_host;
public $smtp_from;
public $smtp_port;
public $smtp_charset;

public function __construct($smtp_username, $smtp_password, $smtp_host, $smtp_from, $smtp_port = 25, $smtp_charset = "utf-8") {
    $this->smtp_username = $smtp_username;
    $this->smtp_password = $smtp_password;
    $this->smtp_host = $smtp_host;
    $this->smtp_from = $smtp_from;
    $this->smtp_port = $smtp_port;
    $this->smtp_charset = $smtp_charset;
}

function send($mailTo, $subject, $message, $headers) {
    $contentMail = "Date: " . date("D, d M Y H:i:s") . " UTrn";
    $contentMail .= 'Subject: =?' . $this->smtp_charset . '?B?'  . base64_encode($subject) . "=?=rn";
    $contentMail .= $headers . "rn";
    $contentMail .= $message . "rn";
    
    try {
        if(!$socket = @fsockopen($this->smtp_host, $this->smtp_port, $errorNumber, $errorDescription, 30)){
            throw new Exception($errorNumber.".".$errorDescription);
        }
        if (!$this->_parseServer($socket, "220")){
            throw new Exception('Connection error');
        }
        
        $server_name = $_SERVER["SERVER_NAME"];
        fputs($socket, "HELO $server_namern");
        if (!$this->_parseServer($socket, "250")) {
            fclose($socket);
            throw new Exception('Error of command sending: HELO');
        }
        
        fputs($socket, "AUTH LOGINrn");
        if (!$this->_parseServer($socket, "334")) {
            fclose($socket);
            throw new Exception('Autorization error');
        }
        
        
        
        fputs($socket, base64_encode($this->smtp_username) . "rn");
        if (!$this->_parseServer($socket, "334")) {
            fclose($socket);
            throw new Exception('Autorization error');
        }
        
        fputs($socket, base64_encode($this->smtp_password) . "rn");
        if (!$this->_parseServer($socket, "235")) {
            fclose($socket);
            throw new Exception('Autorization error');
        }
        
        fputs($socket, "MAIL FROM: <".$this->smtp_username.">rn");
        if (!$this->_parseServer($socket, "250")) {
            fclose($socket);
            throw new Exception('Error of command sending: MAIL FROM');
        }
        
        $mailTo = ltrim($mailTo, '<');
        $mailTo = rtrim($mailTo, '>');
        fputs($socket, "RCPT TO:<".$mailTo.">rn");     
        if (!$this->_parseServer($socket, "250")) {
            fclose($socket);
            throw new Exception('Error of command sending: RCPT TO');
        }
        
        fputs($socket, "DATArn");     
        if (!$this->_parseServer($socket, "354")) {
            fclose($socket);
            throw new Exception('Error of command sending: DATA');
        }
        
        fputs($socket, $contentMail."rn.rn");
        if (!$this->_parseServer($socket, "250")) {
            fclose($socket);
            throw new Exception("E-mail didn't sent");
        }
        
        fputs($socket, "QUITrn");
        fclose($socket);
    } catch (Exception $e) {
        return  $e->getMessage();
    }
    return true;
}

private function _parseServer($socket, $response) {
    while (@substr($responseServer, 3, 1) != ' ') {
        if (!($responseServer = fgets($socket, 256))) {
            return false;
        }
    }
    if (!(substr($responseServer, 0, 3) == $response)) {
        return false;
    }
    return true;
    
}
}

Скрипт отправки

$mailSMTP = new SendMail($m, $p, 'ssl://smtp.yandex.ru', $m, 465);
$headers= "MIME-Version: 1.0rn";
$headers .= "Content-type: text/html; charset=utf-8rn";
$headers .= "From: Hello <mail@mail.com>rn";
$headers .= "Reply-To: mail@mail.comrn";
$result =  $mailSMTP->send('to@mail.com' 'Title', 'text body', $headers);

Страницы

Промо

Поиск по сайту

Статистика

Мета

Функция mail() бывает блокируется на хостинге или самом сайте. Если писать в службу поддержки долго или не имеет смысла — придется отправлять письма через SMTP.

СПОСОБ 1 — просто вставляем этот код на сайте с некоторыми настройками:

<?php
$config[‘smtp_username’] = ‘support@yandeg.ru’; //Смените на имя своего почтового ящика. (ваш email)
$config[‘smtp_port’] = ’25’; // Порт работы. Не меняйте, если не уверены. На 2014 порт вроде 465. ЕСЛИ ВООБЩЕ НЕ РАБОТАЕТ — убрать кавычки в 25
$config[‘smtp_host’] = ‘smtp.yandex.ru’; //сервер для отправки почты
$config[‘smtp_password’] = ‘pass’; //Измените пароль (от вашего ящика)
$config[‘smtp_debug’] = true; //Если Вы хотите видеть сообщения ошибок, укажите true вместо false
$config[‘smtp_charset’] = ‘windows-1251’; //кодировка сообщений. (или UTF-8, итд) (меняется также в самом низу)
$config[‘smtp_from’] = ‘Leon1010’; //Ваше имя — или имя Вашего сайта. Будет показывать при прочтении в поле «От кого»
function smtpmail($mail_to, $subject, $message, $headers=») {
global $config;
$SEND = «Date: «.date(«D, d M Y H:i:s») . » UTrn»;
$SEND .= ‘Subject: =?’.$config[‘smtp_charset’].’?B?’.base64_encode($subject).»=?=rn»;
if ($headers) $SEND .= $headers.»rnrn»;
else
{
$SEND .= «Reply-To: «.$config[‘smtp_username’].»rn»;
$SEND .= «MIME-Version: 1.0rn»;
$SEND .= «Content-Type: text/plain; charset=»».$config[‘smtp_charset’].»»rn»;
$SEND .= «Content-Transfer-Encoding: 8bitrn»;
$SEND .= «From: «».$config[‘smtp_from’].»» <«.$config[‘smtp_username’].»>rn»;
$SEND .= «To: $mail_to <$mail_to>rn»;
$SEND .= «X-Priority: 3rnrn»;
}
$SEND .= $message.»rn»;
if( !$socket = fsockopen($config[‘smtp_host’], $config[‘smtp_port’], $errno, $errstr, 30) ) {
if ($config[‘smtp_debug’]) echo $errno.»<br>».$errstr;
return false;
}

if (!server_parse($socket, «220», __LINE__)) return false;

fputs($socket, «HELO » . $config[‘smtp_host’] . «rn»);
if (!server_parse($socket, «250», __LINE__)) {
if ($config[‘smtp_debug’]) echo ‘<p>Не могу отправить HELO!</p>’;
fclose($socket);
return false;
}
fputs($socket, «AUTH LOGINrn»);
if (!server_parse($socket, «334», __LINE__)) {
if ($config[‘smtp_debug’]) echo ‘<p>Не могу найти ответ на запрос авторизаци.</p>’;
fclose($socket);
return false;
}
fputs($socket, base64_encode($config[‘smtp_username’]) . «rn»);
if (!server_parse($socket, «334», __LINE__)) {
if ($config[‘smtp_debug’]) echo ‘<p>Логин авторизации не был принят сервером!</p>’;
fclose($socket);
return false;
}
fputs($socket, base64_encode($config[‘smtp_password’]) . «rn»);
if (!server_parse($socket, «235», __LINE__)) {
if ($config[‘smtp_debug’]) echo ‘<p>Пароль не был принят сервером как верный! Ошибка авторизации!</p>’;
fclose($socket);
return false;
}
fputs($socket, «MAIL FROM: <«.$config[‘smtp_username’].»>rn»);
if (!server_parse($socket, «250», __LINE__)) {
if ($config[‘smtp_debug’]) echo ‘<p>Не могу отправить комманду MAIL FROM: </p>’;
fclose($socket);
return false;
}
fputs($socket, «RCPT TO: <» . $mail_to . «>rn»);

if (!server_parse($socket, «250», __LINE__)) {
if ($config[‘smtp_debug’]) echo ‘<p>Не могу отправить комманду RCPT TO: </p>’;
fclose($socket);
return false;
}
fputs($socket, «DATArn»);

if (!server_parse($socket, «354», __LINE__)) {
if ($config[‘smtp_debug’]) echo ‘<p>Не могу отправить комманду DATA</p>’;
fclose($socket);
return false;
}
fputs($socket, $SEND.»rn.rn»);

if (!server_parse($socket, «250», __LINE__)) {
if ($config[‘smtp_debug’]) echo ‘<p>Не смог отправить тело письма. Письмо не было отправленно!</p>’;
fclose($socket);
return false;
}
fputs($socket, «QUITrn»);
fclose($socket);
return TRUE;
}

function server_parse($socket, $response, $line = __LINE__) {
global $config;
while (@substr($server_response, 3, 1) != ‘ ‘) {
if (!($server_response = fgets($socket, 256))) {
if ($config[‘smtp_debug’]) echo «<p>Проблемы с отправкой почты!</p>$response<br>$line<br>»;
return false;
}
}
if (!(substr($server_response, 0, 3) == $response)) {
if ($config[‘smtp_debug’]) echo «<p>Проблемы с отправкой почты!</p>$response<br>$line<br>»;
return false;
}
return true;
}
?>

Использовать код можно так-же как и обычную функцию mail:
<?php
$headers = ‘MIME-Version: 1.0’ . «rn»;
$headers .= ‘Content-type: text/html; charset=»windows-1251«‘ . «rn»;
$headers .= ‘From: vasya@pupkin.ru’. «rn»;
smtpmail(’email-получателя@mail.ru’, ‘Тема письма’, ‘Текст письма’, $headers);
?>

СПОСОБ 2 — просто копируем его на сайт и нечего не настраиваем

<?php
/**
* SendMailSmtpClass
*
* Класс для отправки писем через SMTP с авторизацией
*
* @author Ipatov Evgeniy <admin@ipatov-soft.ru>
* @version 1.0
*/
class SendMailSmtpClass {

/**
*
* @var string $smtp_username — логин
* @var string $smtp_password — пароль
* @var string $smtp_host — хост
* @var string $smtp_from — от кого
* @var integer $smtp_port — порт
* @var string $smtp_charset — кодировка
*
*/
public $smtp_username;
public $smtp_password;
public $smtp_host;
public $smtp_from;
public $smtp_port;
public $smtp_charset;

public function __construct($smtp_username, $smtp_password, $smtp_host, $smtp_from, $smtp_port = 25, $smtp_charset = «utf-8») {
$this->smtp_username = $smtp_username;
$this->smtp_password = $smtp_password;
$this->smtp_host = $smtp_host;
$this->smtp_from = $smtp_from;
$this->smtp_port = $smtp_port;
$this->smtp_charset = $smtp_charset;
}

/**
* Отправка письма
*
* @param string $mailTo — получатель письма
* @param string $subject — тема письма
* @param string $message — тело письма
* @param string $headers — заголовки письма
*
* @return bool|string В случаи отправки вернет true, иначе текст ошибки *
*/
function send($mailTo, $subject, $message, $headers) {
$contentMail = «Date: » . date(«D, d M Y H:i:s») . » UTrn»;
$contentMail .= ‘Subject: =?’ . $this->smtp_charset . ‘?B?’ . base64_encode($subject) . «=?=rn»;
$contentMail .= $headers . «rn»;
$contentMail .= $message . «rn»;

try {
if(!$socket = @fsockopen($this->smtp_host, $this->smtp_port, $errorNumber, $errorDescription, 30)){
throw new Exception($errorNumber.».».$errorDescription);
}
if (!$this->_parseServer($socket, «220»)){
throw new Exception(‘Connection error’);
}

fputs($socket, «HELO » . $this->smtp_host . «rn»);
if (!$this->_parseServer($socket, «250»)) {
fclose($socket);
throw new Exception(‘Error of command sending: HELO’);
}

fputs($socket, «AUTH LOGINrn»);
if (!$this->_parseServer($socket, «334»)) {
fclose($socket);
throw new Exception(‘Autorization error’);
}

fputs($socket, base64_encode($this->smtp_username) . «rn»);
if (!$this->_parseServer($socket, «334»)) {
fclose($socket);
throw new Exception(‘Autorization error’);
}

fputs($socket, base64_encode($this->smtp_password) . «rn»);
if (!$this->_parseServer($socket, «235»)) {
fclose($socket);
throw new Exception(‘Autorization error’);
}

fputs($socket, «MAIL FROM: «.$this->smtp_username.»rn»);
if (!$this->_parseServer($socket, «250»)) {
fclose($socket);
throw new Exception(‘Error of command sending: MAIL FROM’);
}

fputs($socket, «RCPT TO: » . $mailTo . «rn»);
if (!$this->_parseServer($socket, «250»)) {
fclose($socket);
throw new Exception(‘Error of command sending: RCPT TO’);
}

fputs($socket, «DATArn»);
if (!$this->_parseServer($socket, «354»)) {
fclose($socket);
throw new Exception(‘Error of command sending: DATA’);
}

fputs($socket, $contentMail.»rn.rn»);
if (!$this->_parseServer($socket, «250»)) {
fclose($socket);
throw new Exception(«E-mail didn’t sent»);
}

fputs($socket, «QUITrn»);
fclose($socket);
} catch (Exception $e) {
return $e->getMessage();
}
return true;
}

private function _parseServer($socket, $response) {
while (@substr($responseServer, 3, 1) != ‘ ‘) {
if (!($responseServer = fgets($socket, 256))) {
return false;
}
}
if (!(substr($responseServer, 0, 3) == $response)) {
return false;
}
return true;

}
}

Вызываем теперь класс с параметрами

require_once «SendMailSmtpClass.php»; // подключаем класс

$mailSMTP = new SendMailSmtpClass(‘zhenikipatov@yandex.ru’, ‘****’, ‘smtp.yandex.ru’, ‘Evgeniy’); // создаем экземпляр класса
// $mailSMTP = new SendMailSmtpClass(‘логин’, ‘пароль’, ‘хост’, ‘имя отправителя’);

// заголовок письма
$headers= «MIME-Version: 1.0rn»;
$headers .= «Content-type: text/html; charset=utf-8rn»; // кодировка письма
$headers .= «From: Evgeniy <admin@vk-book.ru>rn»; // от кого письмо
$result = $mailSMTP->send(‘zhenikipatov@yandex.ru’, ‘Тема письма’, ‘Текст письма’, $headers); // отправляем письмо
// $result = $mailSMTP->send(‘Кому письмо’, ‘Тема письма’, ‘Текст письма’, ‘Заголовки письма’);
if($result === true){
echo «Письмо успешно отправлено»;
}else{
echo «Письмо не отправлено. Ошибка: » . $result;
}

Материал взят частично с сайтов:

http://i-leon.ru/smtp-php/

Отправка писем через SMTP с авторизацией на php

| 2014-09-01 | Отправка писем через SMTP на PHP 2 способа | Функция mail() бывает блокируется на хостинге или самом сайте. Если писать в службу поддержки долго или не имеет смысла — придется отправлять письма ч |

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:<user@domain.com>:
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:<user@domain.com>:
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:<user@domain.com>:
host mx.domain.com [xx.xx.xx.xx]: 554 5.7.1 <unknown[yy.yy.yy.yy]>:
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: <user@domain.com>:
552 5.1.1 <user@domain.com> 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:<user@domain.com>:
550 5.1.1 <user@domain.com> Recipient not found.

SMTP error from remote mail server after RCPT TO:<user@domain.com>:
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:<user@domain.com>:
host host.domain.com [xx.xx.xx.xx]: 554 5.1.8  <user1@domain1.com>:
Sender address rejected: Domain not found

SMTP error from remote mail server after RCPT TO:<user2@domain2.com>:
host mx.server.com [xxx.xxx.xxx.xxx]: 550-Verification failed for <user1@domain1.com>
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»;

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.