554 код ошибки

Если отправка сообщений через SMTP не удается, SMTP сервер сообщает код ошибки, по нему можно определить, в чем проблема и как ее исправить. Наиболее распространенные ошибки указаны в списке ниже.

Код ошибки	Значение	Описание
450	Requested mail action not taken: mailbox unavailable. Требуемые почтовые действия, не предприняты: почтовый ящик недоступен (например, почтовый ящик занят).	Сервер не может получить доступ к почтовому ящику для доставки сообщения. Это может быть вызвано процессом чистки мертвых адресов на сервере, почтовый ящик может быть поврежден, или почтовый ящик может находиться на другом сервере, который в настоящее время не доступен. Также сетевое соединение могло быть разорвано во время отправки, или удаленный почтовый сервер не хочет принимать почту с вашего сервера по некоторым причинам (IP-адрес, черные списки и т.д.). Повторная попытка отправки письма на этот почтовый ящик может оказаться успешной.
451	Requested action aborted: local error in processing. Требуемое действие прерывалось: ошибка в обработке.	Эта ошибка, как правило, возникает из-за перегрузки вашего Интернет провайдера или через ваш SMTP-релей отправлено слишком много сообщений. Следующая попытка отправить письмо может оказаться успешной.
500	Syntax error, command unrecognized. Синтаксическая ошибка, неправильная команда (Это может включать ошибки типа слишком длинная командная строка).	Ваш антивирус/брандмауэр блокирует входящие/исходящие соединения SMTP. Вам следует настроить антивирус/брандмауэр для решения проблемы.
501	Syntax error in parameters or arguments. Синтаксическая ошибка в параметрах или переменных.	Недопустимые адреса электронной почты или доменное имя почтового адреса. Иногда указывает на проблемы соединения.
503	Bad sequence of commands or this mail server requires authentication. Неправильная последовательность команд.	Повторяющая ошибка 503 может свидетельствовать о проблемах соединения. Отклик 503 SMTP-сервера чаще всего является показателем того, что SMTP-сервер требует аутентификации, а Вы пытаетесь отправить сообщение без аутентификации (логин + пароль). Проверьте Общие настройки, чтобы убедиться в правильности настроек SMTP-сервера.
512	The host server for the recipient’s domain name cannot be found (DNS error).	У одного из серверов на пути к серверу назначения есть проблема с DNS-сервером либо адрес получателя не верный. Проверьте адрес получателя на правильность доменного имени (орфографические ошбки в доменном имени или несуществующее доменное имя).
513	Address type is incorrect or authentication required.	Убедитесь, что адрес электронной почты получателя верный, не содержит ошибок. Затем попробуйте повторно отправить сообщение. Другой причиной может быть то, что SMTP-сервер требует аутентификации, а Вы пытаетесь отправить сообщение без аутентификации (обычно аутентификация ESMTP, логин + пароль). Проверьте Общие настройки, чтобы убедиться в правильности настроек SMTP-сервера.
523	The Recipient’s mailbox cannot receive messages this big.	Размер сообщения (сообщение + все его вложения) превышает ограничения по размеру на сервере получателя. Проверьте размер сообщения, которое Вы подготовили для отправки, в частности, размер вложений, возможно, стоит разбить сообщения на части.
530	Access denied.	SMTP-сервер вашего провайдера, требует аутентификации, а Вы пытаетесь отправить сообщение без аутентификации (логин + пароль). Проверьте Общие настройки, чтобы убедиться в правильности настроек SMTP-сервера. Другой причиной может быть то, что ваш SMTP-сервер находится в черном списке сервера получателя. Или почтовый ящик получателя не существует.
535	Username and Password not accepted.	Проверьте настройки SMTP-сервера. Убедитесь в том, что логин и пароль введены правильно.
541	Recipient Address Rejected – Access denied.	Этот ответ почти всегда отправляется Антиспам фильтром на стороне получателя. Проверьте ваше сообщение соспам чекером или попросите получателя добавить вас в белый список.
550	Mailbox unavailable. Требуемые действия, не предприняты: почтовый ящик недоступен (например, почтовый ящик, не найден, нет доступа).	Отклик 550 SMTP-сервера означает, что емейл-адреса получателя нет на сервере. Свяжитесь с получателем устно, чтобы получить его емейл-адрес.  Ошибка 550 иногда может быть отправлена Антиспам фильтром. Другим случаем возврата отклика 550 может быть, когда сервер получателя не работает.
552	Requested mail action aborted: exceeded storage allocation or size of the incoming message exceeds the incoming size limit. Требуемые почтовые действия прервались: превышено распределение памяти.	Почтовый ящик получателя достиг своего максимально допустимого размера. Другим случаем возврата отклика 552 может быть, когда размер входящего сообщения превышает лимит указанный администратором сети.
553	Requested action not taken – Mailbox name invalid. Требуемые действия, не предприняты: имя почтового ящика, недопустимо (например, синтаксис почтового ящика неправильный).	Неверный адрес электронной почты получателя. Отклик 553 SMTP-сервера иногда возвращает почтовый сервер вашего Интернет провайдера. Это происходит, если у Вас нет подключения к Интернету у этого провайдера.
554	Transaction failed. Передача данных не удалась	Отклик 554 SMTP-сервера возвращает антиспам-фильтр в случае, если не нравится емейл-адрес отправителя, или IP-адрес отправителя, или почтовый сервер отправителя (к примеру, они находятся в RBL). Вам нужно либо попросить отправителя добавить Вас в белый список, либо Вы должны принять меры, чтобы Ваш IP-адрес или ISP сервер был удален из RBL (Realtime Blackhole List).

Email errors are difficult to deal with, particularly if there is no specific information about the error.

One such error is “554 permanent problems with the remote server“.

At Bobcares, we help customers resolve email errors as part of our Server Support Services for web hosts.

Today, we’ll discuss the top 4 reasons for this error and how we fix them.

554 SMTP error – General definition

In the email bounce back message, website owners often see a vague error code like 554.

What’s does this 554 error code mean? A confusing query, always.

554 error code means that the receiving server sees something in the From or To Headers of the message, that it doesn’t like.

This can be caused by a spam filter identifying your machine as a relay, or as a machine not trusted to send emails from your domain.

Error ‘554 permanent problems with the remote server’ – Causes and Fixes

Now, we have a general idea of 554 SMTP errors.

Let’s now move on to the main reasons for the error “554 permanent problems with the remote server” and how our Server Support Engineers fix them.

1) Sender IP blacklisted

One of the main reasons for this error is the poor reputation of the sender’s IP address.

The IP address of the sender can usually be blacklisted because of continuous spam instances, open relays, etc.

Consequently, the mail server IP will be blacklisted by major spam monitoring systems like SpamHaus, DNSSBL, SORBS, etc.

Major email providers like Gmail, Yahoo, Hotmail monitor the reputation of the IPs before accepting the connection, and if any problems are noted, they will reject the emails.

How we fix?

Firstly, our Server Support Engineers check and ensure that the IP address of the sender doesn’t appear in any of the RBLs. Online tools like https://mxtoolbox.com/blacklists.aspx comes handy here.

And if the IP is blacklisted, we identify the source of the spam, fix it, take preventive measures and finally submit delist request to the RBLs.

At Bobcares, we always take necessary steps to secure the server and to prevent outgoing spam. Some of the main things we do are setting outgoing limits, disable pop before smtp, etc.

2) Sender flagged as Spam

The recipient server sometimes uses custom blacklists or filters that use strict rules for monitoring the incoming messages.

So, the emails that violate these rules will be blocked at the recipient end.

For example, if the message body contains spam words or sender trying to send to more addresses allowed at one time, the recipient filter will considers it as suspicious and blocks the connection.

Similarly, major email providers such as Yahoo have a number of best practices to send bulk emails, email sending limits, etc. If any of these rules are breached, the message is blocked.

And, users see errors like 554 permanent problems with the remote server.

How we fix?

Our Server Support Engineers first analyze the nature of the message sent. If we note unsupported file format, spam contents, etc. in the message, we suggest the customer to remove it and send again.

And, if it’s a valid message, then the sender domain must be whitelisted at the recipient end to allow mail flow.

3) Bad DNS records

Likewise, recipient server can reject emails because of the bad DNS records of the sender domain.

The recipient server usually checks the DNS records such as  RDNS(PTR), SPF, DKIM, etc. to verify the sender, and emails will be rejected if any discrepancies are noted in these records.

Result is users see errors like 554 permanent problems with the remote server.

Now, let’s take a look at these 4 records in detail.

a) RDNS(PTR) record

Reverse DNS or PTR records translates sending IP address into it’s domain name.

This ensures that the IP address is linked to a real domain name.

In addition to that, it confirms that emails don’t come from dial up connections or dynamic IPs that are common methods used by spammers.

Many email providers such as Yahoo, Gmail, etc. block emails from servers with a bad RDNS record or no RDNS records.

b) SPF record

Many email providers use SPF(Sender Policy Framework) record to prevent spammers from sending unauthorized emails from their domain.

In other words, SPF record contains server IP addresses that can send emails on behalf of the domain. And, if the email doesn’t originate from any of these IPs, it will reject that email. In this way, it fight against email spoofing.

However, we’ve seen cases where the mail server IP has changed and this new IP address hasn’t been added to the SPF record.

As a result, the recipient sees the mails originate from a server that is not added in the SPF record and hence rejects the email.

c) DKIM record

Similarly, DKIM(Domain Keys Identified Mail) records sign your emails in a way that allows the recipient server to check whether the sender is valid or not.

If there are no DKIM records, some mail servers reject the emails considering the sender as fake.

d) DMARC record

Like SPF and DKIM, DMARC(Domain Message Authentication Reporting & Conformance) records also help the recipient server to verify the authenticity of the sender by validating that an email originates from the specified source.

Sometimes, a missing DMARC record can lead to email rejections.

How we fix?

Firstly, our Support Engineers cross check the DNS records such as PTR, SPF, DKIM, DMARC, etc. of the sender domain.

And, if any mismatch is found, we’ll immediately correct it by making the required changes in the records.

At Bobcares, we always make sure to configure critical email records like PTR, SPF, DKIM, DMARC, etc. to ensure reliable email deliveries.

4) Recipient errors

Another reason for the error is the problems at the recipient mail server.

This can be caused by incorrect MX record of the recipient domain, disabled/suspended domain, and more.

How we fix?

Our Support Engineers check the recipient domain and it’s MX records with the below command.

dig domain.com MX

Further, we check the connection to the recipient mail server with the following command.

telnet domain.com 25

If we notice missing MX entries or connectivity problems, this must be corrected at the recipient end.

Conclusion

In short, ‘554 permanent problems with the remote server’ can happen due to bad DNS records, poor IP reputation and more. Today, we’ve discussed the top 4 reasons for this error and how our Server Support Engineers fix them.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Dealing with email problems may be challenging, especially if there is no clear description of the mistake. “554 persistent difficulties with the remote server” is one of these SMTP errors. As part of our server support services for web providers, Bobcares helps clients fix roadrunner email issues. We’ll talk about the top four causes of this problem today and their solutions.

What is the 554 SMTP error?

Website owners frequently observe an ambiguous error number, such as 554, in the email bounce-back message. What does the error code 554 indicate? A perplexing question, always. The From or To headers of the message includes something the receiving server doesn’t like, according to the 554 error code. This can happen if a spam filter flags your computer as a relay or a device that shouldn’t be trusted to send emails from your domain.

How to Fix SMTP Error “554 Permanent Problems With the Remote Server”

Now that we understand the basics of 554 SMTP failures. The primary causes of the error “554 persistent difficulties with the remote server” and how our Server Support Engineers resolve them are discussed below.

• IP Blacklist for the Sender

The sender’s IP address’s bad reputation is one of the primary causes of this issue. Continual spam incidents, open relays, etc. frequently lead to the IP address of the sender being blacklisted. As a result, important spam monitoring systems like SpamHaus, DNSSBL, SORBS, etc. will ban the mail server IP. Before allowing the connection, major email providers like Gmail, Yahoo, and Hotmail check the reputation of the IPs, and if any issues are found, they will refuse the emails.

How to fix it?

First, our Server Support Engineers verify that the sender’s IP address does not show up in any RBLs. Here, online resources are useful. Finally, we submit a delisting request to the RBLs if the IP is banned after locating the spam’s source, fixing it, and taking preventive steps.

• Spam-reported Sender

Sometimes the receiver server employs unique blacklists or filters with stringent guidelines to keep an eye on the incoming communications. Emails that don’t comply with these guidelines will thus be banned at the receiver end. For instance, the receiver filter will flag the connection as suspicious if the message content contains spam terms or the sender attempts to transmit to multiple permitted addresses at once. Similar to this, well-known email service providers like Yahoo offer a lot of guidelines for sending bulk emails, email sending restrictions, etc. The message is banned if any of these rules are broken. Users also encounter persistent issues with the remote server, such as error code 554.

How to Fix it? 

Firstly, consider the message’s content. We advise the customer to delete the message and submit it again if we discover an unsupported file type, spam, etc. in the message. Additionally, in order to allow mail flow, the sender domain must be whitelisted at the receiver end if the message is legitimate.

• Invalid DNS Records

Similar to how sender domain DNS records might cause recipient servers to refuse emails.  In order to validate the sender, the receiver server often verifies DNS records like RDNS(PTR), SPF, DKIM, etc. Emails will be discarded if any differences are found in these records.  As a result, users get errors like 554 that indicate ongoing issues with the remote server. Let’s now examine these 4 documents in further detail.

1. RDNS(PTR) record: The transmitting IP address is converted into the domain name via reverse DNS or PTR records. This guarantees that a legitimate domain name is associated with the IP address. Furthermore, it verifies that emails don’t originate from dial-up connections or changeable IPs, which are frequent tactics employed by spammers. Emails from servers with a poor RDNS record or no RDNS record are frequently blocked by email services like Yahoo, Gmail, and others.
2. SPF history: SPF (Sender Policy Framework) records are frequently used by email providers to stop spammers from sending illegal emails from their domain. In other words, the SPF record lists server IP addresses that are authorized to send emails on the domain’s behalf. Additionally, it will reject emails that don’t come from any of these IPs. By doing this, it combats email spoofing. We have observed instances when the IP address of the mail server has changed but the SPF record does not yet include the new IP address. The receiver rejects the email because they notice that it comes from a server that isn’t included in the SPF record.           
3. DKIM data: Similar to this, DKIM (Domain Keys Identified Mail) records sign your emails so that the destination server can verify the legitimacy of the sender. Some mail servers refuse emails if there are no DKIM records because they assume the sender is a phony.
4. Record for DMARC: Domain Message Authentication Reporting & Conformance (DMARC) records, like SPF and DKIM, assist the recipient server in confirming the sender’s legitimacy by confirming that an email comes from the stated source.  Email rejections can occasionally be caused by a missing DMARC record.

How to Fix it?

First, our support engineers double-check the sender domain’s DNS records, including PTR, SPF, DKIM, and DMARC. Additionally, we’ll instantly fix any discrepancies by updating the records as needed.

• Recipient Mistakes

The receiver mail server’s issues are another cause of the error. This may be brought on by the receiver domain’s erroneous MX record, a deactivated or suspended domain, and more.

How to Fix it?

Our support engineers use the below command, dig domain.com, to verify the recipient domain and its MX records. MX We next use the command telnet domain.com 25 to confirm that we are connected to the receiving mail server. It is necessary to fix any connection issues or missing X entries at the receiver end. The following command is used by our support engineers to check the recipient domain’s MX records: dig domain.com MX. We next use the command telnet domain.com 25 to confirm that we are connected to the receiving mail server. It is necessary to fix any connection issues or missing MX entries at the receiver end.

Conclusion

In other words, “554 persistent difficulties with the remote server” might occur for a variety of reasons, including incorrect DNS records, an unreliable IP address, and more. We’ve spoken about the top 4 causes of this problem today and how our server support engineers can repair them. If you have any problem with your Roadrunner email account, the Roadrunner or Spectrum email problems support team is available to help you with any such issues.