Why doesn't Yandex send emails? Why aren't my emails being sent? Why don't I receive emails?

When working with the Yandex.Mail email client, users may encounter unexpected errors. To avoid any confusion, today we’ll tell you about error Code: 3, which appears when you try to send a letter. This failure may also be accompanied by the text “The letter cannot be sent because it appears to be spam.” In both cases, the essence of the problem is the same, so first we will tell you about the possible causes of this error, and below we will give instructions on how to fix it.

Reasons for the error

If you receive error code 3 or spam messages, there are several options: your mail was hacked to send messages, there was an error in the work of the mail robot that accidentally mistook the letter for Spam, or you yourself are abusing the mailing. In any case, blocking occurs if you have violated one or more rules:

  • Identical or template letters are being sent to different addresses;
  • You have sent a large number of emails in the last 24 hours;
  • The mail robot considered your letter suspicious;
  • You are trying to send an email to a non-existent address;
  • Users are complaining about your account due to emails being sent from your address.

The first thing you should check is the sender address field. The address must not contain Cyrillic characters or unacceptable characters. And also end with the correct address mail client. For example: “@yandex.ru”, “@gmail.com”, “@mail.ru” “@rambler.ru”, “@list.ru”. If you copied the address into the sender field, try typing it manually. Perhaps there was an extra Cyrillic letter.

Mistakes are wonderful, we are given a hint that something went wrong, and this is a signal to action. After all, it’s easier to solve the problem; it will be worse if your email is delivered to an existing or incorrect address, and you won’t even know about it. Now let's listen to Yandex's recommendations in solving this problem.

Since search robot algorithms are constantly updated, your email could be mistaken for spam. To avoid this in the future, you will need to go to the desktop web mail interface.

Desktop interface means using the email client website, not mobile application or programs for working with letters.

To do this, from your computer or phone, go to: https://mail.yandex.ru, log into your account and send any letter for the test. This will tell the email robot that our account is good.

What to do if your email is blocked?

If a mass mailing was carried out from your account, the email could be blocked for subsequent sending. In this case, only sent messages are blocked. You are allowed to receive and view letters. The blocking itself is removed automatically after 24 hours. If you send emails during this time, it will last another day. While the blocking is expected to be lifted, it is recommended to perform a number of standard actions:

  1. Change your email client password.
  2. Fill in your personal information: first name, last name, date of birth.
  3. Link the correct number mobile phone.
  4. Scan your computer for viruses, for example free program by Dr.Web CureIt.

Write in the comments whether you managed to fix the problem, and whether the information was useful. If you encounter other errors, please use the “Report a problem” form in the side column of the site.

Despite all the advantages Email, difficulties often arise when sending letters. Either the letter is not sent, or the post office cannot deliver it to the addressee.

Let's try to figure out why such problems can arise and how to deal with them.

Invalid email address

The most common cause of problems with sending letters is an error in the mailbox address (the “To” field). Although usually the user thinks of anything, but not of this.

If you miss or type at least one “wrong” letter in the mail name, the letter will not be delivered!

In the best case, the mail site will immediately report this, that is, the corresponding inscription will appear, and you simply will not be able to send the letter.

But it could also be different: the letter is sent, but then a notification arrives that it was not delivered (see Undelivered message).

And there is a third option: the letter will “go” to the address, but not to the one needed. This is the most unpleasant thing, because you may not even know about it.

For example, I need to send a letter to the address

But when typing, I accidentally miss one letter in the name. It turns out not, but.

If I do not notice the error and send this letter, then at best it will not be delivered and I will immediately receive a notification about it.

And in the worst case, my message will still be sent, but it will go to another person. To someone who has a box with a name

Common mistakes

The most common address errors that cause problems with shipping and delivery:

Another common mistake is an incorrectly typed email site (the part after the @ sign). That is, if instead of the yandex .ru part you type yandeks .ru or simply yandex (without .ru), then the letter will not be delivered. And again, we may not even know about it.

Here's how to spell the most popular email sites:

  • yandex.ru
  • gmail.com
  • mail.ru
  • bk.ru
  • inbox.ru
  • list.ru
  • rambler.ru

Undelivered message

If the post office was unable to deliver your letter, it will inform you about this in a special notification.

It happens like this: some time after sending, a letter arrives in which it is written in Russian or English that your message was not delivered.

Here's what it looks like in Yandex.Mail:

And so - in Mail.ru:

So - in Gmail.com:

And so - in Rambler:

Thus, the mail tells us that the sending was unsuccessful - no one received the letter.

This happens for two reasons:

1. The address does not exist

This means that such an address does not exist in nature. It may have been deleted, or perhaps you made a typing error.

Quite often it happens that when they left you an email address, it was accidentally entered with an error. That is, it was not even you who made the mistake, but the one who left it.

2. Box is not available

Unavailable - this means that it is working, but for some reason cannot currently receive mail.

This is usually due to overcrowding. That is, there are too many letters in the mailbox and there is simply no room for new ones. In this case, the recipient should delete at least one or two letters from the mailbox.

Another reason: problems with the mail site. That is, the site on which the box is located has stopped working. This is usually a temporary phenomenon that goes away within a few hours.

What to do. It is impossible to independently determine what exactly happened. Therefore, if such a notification arrives, you just need to repeat the sending after some time.

If resending fails, then nothing can be done about it - you will have to contact the recipient in some other way.

How to avoid problems with sending and delivering mail

According to statistics, the most common cause of problems with mail delivery is an incorrectly specified address. That is, in essence, it is not the one who receives the letter who is to blame, but the one who writes it.

Therefore, you must be very careful not only when typing the address in the “To” field, but also in the process of “receiving” it.

If, for example, an address is dictated to you over the phone, do not hesitate to clarify whether you understood this or that letter correctly. It is advisable, of course, to receive it in text form, and not try to understand it by ear (via SMS, via a social network, etc.).

You should also remember that email addresses have a specific syntax. That is, there is, so to speak, a set of rules by which each mailbox address on the Internet is formed.

  • Any address consists only from English letters , numbers and some characters (dot, hyphen, underscore). No Russian letters!
  • It cannot contain spaces.
  • In him there is always an @ sign(approximately in the middle) and this sign is only one.
  • After the @ sign there is always the name of a site. And in this title there is always a point, followed by a few more English letters (for example, mail.ru, gmail.com).
  • There is no period at the end of the address.

It is advisable, of course, to remember these rules. Then you will not receive the “Invalid email address” error.

Problems with receiving mail on a domain may occur if:

  • domain registration has expired;
  • the domain is blocked by the registrar;
  • the domain has not been delegated or has been withdrawn from delegation by the registrar;
  • delegation settings are not configured correctly;
  • DNS records for Yandex.Mail are not configured or configured incorrectly.

To resolve problems with receiving emails, contact your domain administrator. It was he who provided you with mailboxes. The Mail for Domain support service will not be able to help you in this situation.

If you registered your mailbox on a specific site, then contact the support service of that site.

DNS records

Most often, problems with receiving mail are caused by incorrect MX record settings.

The MX record points to the server that accepts mail for your domain. In order for your mail to be processed by the Yandex server, the MX record must point to it. For more information about setting up an MX record, see the MX record section.

You can check whether the MX record is configured correctly using the dig utility:

    Select the MX record type and run the request.

If the MX record is configured correctly, the response will be something like this:

Yourdomain.tld. 21521 IN MX 10 mx.yandex.net.

Possible problems:

    The server does not respond to the request or the value does not match the desired one. This means that either the changes did not take effect, or the MX record was configured incorrectly.

    In addition to the Yandex MX record, the request was responded to by MX records pointing to third-party servers.

    To resolve this issue, remove entries for third-party servers. To do this, go to the DNS management section in which you configured the Yandex MX record.

    The entry in the server response looks like "mx.yandex.net.yourdomain.tld.". You must add a dot at the end of the MX record value: “mx.yandex.net.” .

Domain registration has expired

After the domain registration period expires, the registrar removes the domain from delegation or delegates it to blocking servers.

You can check domain delegation information using the service http://www.whois.com or http://www.whois-service.ru.

    state: (Status: or Domain Status:) you can check the domain status;

    Name Server: or nserver: (there must be two or more) - to which servers the domain is delegated;

    Expiration Date: (paid-till: , Domain Expiration Date: or Expires On:) - when the domain registration expires.

If NS servers are specified:

NS1.VERIFICATION-HOLD.SUSPENDED-DOMAIN.COM NS2.VERIFICATION-HOLD.SUSPENDED-DOMAIN.COM

Contact your registrar's support team. The registrar blocked the domain because the administrator did not confirm the contact email address.

If NS servers are specified:

Blocked1.nic.ru. (ns1.expired.r01.ru. or exp1.nameself.com.) blocked2.nic.ru. (ns2.expired.r01.ru. or exp2.nameself.com.)

Find out from the registrar why the domain is blocked. As a rule, this is due to the expiration of the domain registration period.

If your domain has been delegated and its registration period has not yet expired, you can proceed to checking the DNS.

Delegation settings

If the domain registration has not expired and the domain is delegated, check the DNS using the dig utility (for example, http://www.ip-ping.ru or http://www.digwebinterface.com):

    Make sure that the "NS" request is answered by the same NS servers that are listed in the Whois information about the domain.

    Enter your domain name (“yourdomain.tld”) as the site address.

    Select the NS record type and run the query.

If the NS servers specified at the registrar respond, then the delegation settings are correct.

If there is no response or other NS servers respond, it means the changes have not yet taken effect or the delegation settings have not been completed correctly. For example, when delegating a domain, an error was made in the names of the NS servers at the registrar or the zone for your domain was not configured on the servers to which the domain was delegated.

If not only the NS servers specified by the registrar respond, it means that third-party NS records have been added to the servers to which the domain is delegated. For correct operation Mail for a domain, the domain should be delegated to the servers of only one company. Delegation should only be done in the Registrar control panel.

Domain settings are correct

If you are sure that the domain registration has not expired and all its settings are correct, look for a possible reason in the Yandex.Mail Help section.

Notification letters from the site do not arrive in mailboxes

    Check your domain settings according to the instructions above.

    Contact the administrator of the server on which the site is located. Ask to configure the server correctly. The server on which the site is located may recognize the domain as local and try to send letters to the internal directory.

    Check to see if your hosting provider or registrar has activated email service for your domain. For Mail to work correctly for a domain, this service must be disabled.

You can configure sending emails via the Yandex SMTP server - “smtp.site”. To do this use:

    port “465” with data encryption via SSL;

    mandatory authentication on the server (you must specify the full address of the mailbox that will be used for sending).

To avoid problems with the delivery of letters, you need to take into account:

The modern user has a huge selection of browsers. Often, owners of PCs, laptops, tablets or smartphones prefer to use several applications simultaneously, choosing the best one for certain tasks. Yandex browser is one of them. Despite the stability and constant improvement of the product, sometimes users encounter errors. Today we will tell you what to do if a failure occurs: “An error has occurred, Yandex browser cannot continue working. Restart?".

Yandex.Browser cannot continue working.

Why is this happening?

First of all, there is damage necessary files or their conflict with Windows. There are a lot of reasons for this:

  • installation of illegal plugins, viruses and other malware;
  • incorrect update or user intervention (deleting or changing work values);
  • blocking by security means and much more.
  • Don’t exclude errors from the developers themselves, for example, after the latest updates, a crash appears when trying to synchronize an account.

It is noteworthy that even reinstallation does not help solve the problem, and many users begin to blame the equipment, damage to the operating system and other defects. This is not so, therefore there is reason to panic, and even more so Windows reinstallation, No.

What should be done?

Let's start with standard methods troubleshoot computer problems that are important in any situation.



Update

After all the cleaning and optimization of the system, try updating the program itself. Here brief instructions by updating without deleting.



If the problem is suddenly not solved, then you will have to act more radically.

Reinstalling the browser

Please note that traditional uninstallation and reinstallation is not enough. Some software files remain on the computer even after deletion, and they are often the reason why the error window appears. However, nothing prevents you from trying to uninstall through the control panel and install the browser again, but to save time we recommend a more reliable option.



Conclusion

Finally, I advise you to add this browser to your antivirus and firewall exceptions. After such manipulations, the program should work normally. If this does not happen, then we advise you to contact support, where you will describe in detail: what you did to eliminate the error “Yandex.Browser cannot continue working.” The last option is that the problem is in Windows itself - try to update to the current build and install new components of the Visual C++ and .NET Framework redistribution.

Below are the reasons and solutions to typical problems why mail may not be sent from ePochta Mailer. Even to your own mailing address!

Error Description and solution
Connecting to: smtp.server.ru:25
Disconnected.
Disconnected.
Socket Error #10051
Network is unavailable
There may be two reasons for the problem:
1 - connection is blocked by security programs
2 - port 25 is closed by the Internet provider.
In the first case - disable security programs and resend the test letter, in the second - contact your Internet provider and ask either to open this port, or use alternative ports for this SMTP server with which it can work and which are not blocked by your Internet -provider.
HELO/HELO rejected You need to open Settings/General Settings/Connection/HELO Value and click "Define".
After that, copy your HELO value and paste it into the appropriate field.
mail.ru blocks as spam Your mailing was accepted as spam on the mail.ru server. This most often happens when you send an empty letter.
You need to follow the link “http://mail.ru/notspam/” to receive details, or write a letter to « » .
Contact mail.ru and explain that your mailing list is not spam and demand to know why they are blocking it. Or use a different SMTP server
“Dispatching...” very long If the status "Dispatching..." has been hanging for quite a long time (more than a minute), please check the following:
1. The prepared message has big size and ePochta Mailer takes longer to send it.
2. ePochta Mailer is completely blocked from Internet access by an antivirus or firewall. Set an exception for ePochta Mailer.
Error 450: Requested mail action not taken: mailbox unavailable. The server cannot access the mailbox to deliver the message. This may be caused by the server's dead address purge process, the mailbox may be corrupted, or the mailbox may be on another server that is not currently accessible. Also, the network connection may have been broken during sending, or the remote mail server does not want to accept mail from your server for some reason (IP address, blacklists, etc.). A second attempt to send a letter to this mailbox may be successful.
Error 451: Requested action aborted: local error in processing. This error usually occurs due to your ISP being overloaded or too many messages being sent through your SMTP relay. The next attempt to send a letter may be successful.
Error 500: Syntax error, command unrecognized. Your antivirus/firewall is blocking incoming/outgoing SMTP connections. You should configure your antivirus/firewall to resolve the issue.
Error 501: Syntax error in parameters or arguments. Invalid email addresses or domain name of the mailing address. Sometimes indicates connection problems.
Error 503: Bad sequence of commands or this mail server requires authentication. Repeated 503 errors may indicate connection problems. A 503 response from the SMTP server is most often an indication that the SMTP server requires authentication, and you are trying to send a message without authentication (login + password). Check General Settings to ensure the SMTP server settings are correct.
Error 512: The host server for the recipient’s domain name cannot be found (DNS error). One of the servers on the path to the destination server has a problem with the DNS server or the recipient address is incorrect. Check the recipient's address for the correct domain name (spelling errors in the domain name or non-existent domain name).
Error 513: Address type is incorrect or authentication required. Make sure the recipient's email address is correct and free of errors. Then try resending the message. Another reason could be that the SMTP server requires authentication, and you are trying to send a message without authentication (usually ESMTP authentication, login + password). Check General Settings to ensure the SMTP server settings are correct.
Error 523: The Recipient's mailbox cannot receive messages this big. The message size (message + all its attachments) exceeds the size limits on the recipient's server. Check the size of the message you have prepared to send, in particular the size of the attachments; it may be worth splitting the messages into parts.
Error 530: Access denied. Your provider's SMTP server requires authentication, and you are trying to send a message without authentication (login + password). Check General Settings to ensure the SMTP server settings are correct. Another reason could be that your SMTP server is blacklisted by the recipient's server. Or the recipient's mailbox does not exist.
Error 535: Username and Password not accepted. Check your SMTP server settings. Make sure that the username and password are entered correctly. Open “Settings”/ “General Settings”/ “SMTP”, there double click on the SMTP server address, and in the window that appears, correct the username and password.
Note 1: Make sure CAPS LOCK is turned off - this is important!
Note 2: Some SMTP servers require a login « » instead of just "user", clarify these points.
Error 541: Recipient Address Rejected - Access denied. This response is almost always sent by the Antispam filter on the recipient's side. Check your message with a spam checker or ask the recipient to whitelist you.
Error 550: Mailbox unavailable. A 550 response from the SMTP server means that the recipient's email address is not on the server. Contact the recipient verbally to obtain their email address. Error 550 can sometimes be sent by the Antispam filter. Another case of a 550 response being returned would be when the recipient's server is down.
Error 552: Requested mail action aborted: exceeded storage allocation or size of the incoming message exceeds the incoming size limit. The recipient's mailbox has reached its maximum allowed size. Another case of a 552 response being returned is when the size of the incoming message exceeds the limit specified by the network administrator.
Error 553:Requested action not taken - Mailbox name invalid. Invalid recipient email address. SMTP server response sometimes returns 553 mail server your Internet provider. This happens if you do not have an Internet connection with this provider.
Error 554: Transaction failed. Response 554 from the SMTP server is returned by the antispam filter if the sender's email address, or the sender's IP address, or the sender's mail server is not liked (for example, they are located in RBL). You need to either ask the sender to add you to the whitelist, or you must take steps to have your IP address or ISP server removed from the RBL (Realtime Blackhole List).

From time to time, users complain that they do not receive letters to Yandex mail. Why might this happen? How to deal with this problem? Is everything really as dangerous as it seems at first glance? All this will be answered further. In fact, there can be a lot of problems. But there is clearly no need to panic. Most situations are resolved without much difficulty.

Network failure

Why don't I receive letters to Yandex mail? The whole issue may lie in the most common system failure of this service. This does not depend on the user. Occurs due to overload of the main server or during an update.

If the network fails, some users may receive emails, but others may not. There are also problems sending messages. There is no need to be afraid. It's enough just to wait a little. As soon as network failures and problems are corrected, mail will begin to work at full capacity.

Spam

But this is not the most common problem. Are your emails not coming to Yandex? Most often, the messages actually reach the user's mailbox. All letters are simply placed not in the “Inbox”, but in the “Spam” folder.

If you are expecting to receive a message, but it does not arrive for a long time, it is recommended to check the specified folder. Most likely, this is where the lost letter will be. A very common occurrence related to email settings and filters.

So it is advisable to check your Spam folder in advance. As practice shows, half of users stop complaining about the problem. But these are not all the options for the development of events. There is another reason why letters do not arrive at Yandex mail.

Blocking

It is likely that messages from certain domains or addresses will not reach the recipient. Moreover, it is not necessary to have mail on Yandex; the problem can happen with any hosting. The reason lies in automatic settings services that include blocking certain emails.

In this case, it is recommended to write to Yandex technical support. Although many users advise simply setting up an email account on a different hosting. Unblocking is not easy. But you can try to resolve the situation on your own. Are you not receiving emails from Yandex from GMail? Just try to work a little with the filters. Maybe it will be possible to remove the blocking without much difficulty.

Working with filters

If letters from a user are placed in the Spam folder or are not received by the user, it is recommended to enable the security filter settings in Yandex. How to do it?

Just follow the instructions:

  1. Log in via email. Next go to "Settings".
  2. Select "Mail Processing Rules" from the menu that appears.
  3. Go to the "White List" section and enter the required sender's address in the appropriate window.
  4. Click on "Add".

From now on, contacts from the White List will no longer be placed in the Spam folder. And they won’t be recognized as prohibited either. It is clear what to do if letters do not arrive at Yandex mail.

Overcrowding

But that is not all. Sometimes the reason that letters do not arrive at one or another email address is simply overcrowding with data. Each service has its own limit of incoming and outgoing documents. It is likely that it is exhausted.

Check if you have access to the Internet (without an Internet connection, the Yandex.Mail website will not open):

    Are you connected to mobile network?

    Do you have money in your mobile phone account?

    Can you use another internet connection, such as Wi-Fi?

Also check for errors and typos in the site address.

I see an error when sending

What message did you receive?

Through the mobile interface of Mail, you can send attachments with a total size of up to 25 MB. If you want to send more, upload files to and attach files from there.

This error may occur if you are logged out or logged into another tab in another tab. Clear , then sign in to Mail and try sending the email again.

If such a message appears, the contents of your letter have been recognized by Yandex.Mail as spam. To solve the problem, open Yandex.Mail and send any one letter as a test. This way you will prove to the system that the letters are not being sent by a robot.

Try sending the email again. If it doesn't work, write to support using the feedback form in the application.

Try sending the email again. If it doesn't work, write to support using the feedback form in the application.

I do not remember the password. What to do?

I don't remember my login. What to do?

If you have forgotten your login, try using the hint on. The hint may work if you have recently logged into your account on Yandex from the same phone.

Also try contacting those with whom you corresponded - your recipients may remind you from which address your letters came.

Letters have disappeared. How to restore them?

If you accidentally deleted emails or your emails are missing, try looking for them in the Deleted Items folder (mails in this folder are available for 7 days after deletion). To recover emails:

If the missing messages are not in the Deleted Items folder, then, unfortunately, they cannot be recovered.

If you have not deleted the emails, follow these steps:

How to switch to the full version of Mail?

To switch to the full version of Yandex.Mail, click the button in the upper left corner of the screen, and on the page that opens, click the Full button at the bottom of the page. To return to mobile Yandex.Mail, click the Light version link at the bottom of the page.

You cannot always download the full version of Mail automatically.

How to log out of your mailbox?

How do I switch to other services (for example, Search or News)?

Click the icon in the top left corner of the screen, then click the More services link.

No emails are arriving in my inbox

If you have not received an email or notification from social network or forum, follow these steps:

    Check whether you have entered the correct email address on the website from which the notification should come. Check with the sender to see if he has entered your address correctly.

    Look for the letter in your Spam folder - it might have ended up there. If this happens, select the email and click the Not Spam! button. - the letter will be moved to the Inbox folder.

    Make sure there is no rule that deletes such emails or moves them to Spam or another folder. If there is such a rule, disable it.

If you are sure that you have correctly specified your mailbox settings and address on the website, try requesting a letter from the website or from the sender again. If the letter does not arrive after a few hours, contact the site administration.

The letter may also not be delivered due to technical problems on the mail servers of the sender or recipient, the congestion of communication channels, etc. In this case, the sender will receive an automatic report in which it will be indicated. If the sender has not received the report, then to find out the reasons for the non-delivery, he needs to contact the technical support of the mail service from which the letter was sent.

Emails are not sent

There were problems with the operation of the site (not Yandex)

Unfortunately, Yandex support will not be able to answer some questions not related to the operation of Yandex itself. To resolve problems that arise when working with other sites, please contact the administration of these sites.

If your problem is related to the operation of any social network or forum, please contact the support team of this network or forum.

When sending a message to Yandex mail, an error may occur and the letter may not be sent. This issue can be dealt with quite simply.

There are few reasons why letters are not sent to Yandex mail. In this regard, there are several ways to solve them.

Reason 1: Browser problem

If an error window appears when you try to send a message, then the problem is in the browser.

To solve it, you will need to do the following:

Reason 2: Problem with Internet connection

One of the possible factors causing the message sending problem could be a poor or missing network connection. To figure this out, you'll need to reconnect or find a location with good connectivity.

Reason 3: Technical work on the site

One of the few options. However, this is quite possible, since any service may experience problems that will require users to restrict access to the site. To check if the service is available, go to and enter mail.yandex.ru in the check window. If the service is not available, you will have to wait until the work is completed.

Reason 4: Incorrect data entry

Quite often users make mistakes when entering "Destination" Incorrect e-mail, incorrectly placed signs, etc. In such a situation, you should double-check the printed data for accuracy. If such an error occurs, a corresponding notification from the service will be displayed.

Reason 5: The recipient cannot receive the message

In some cases, sending a letter to a specific person is not possible. This can happen due to banal overcrowding of the mailbox or a problem with the site (if the mail belongs to another service). The sender will only have to wait for the recipient to sort out the difficulties that have arisen.

There are a small number of factors that cause problems with sending emails. They can be resolved quite quickly and simply.

Below are the reasons and solutions to typical problems why mail may not be sent from ePochta Mailer. Even to your own mailing address!

Error Description and solution
Connecting to: smtp.server.ru:25
Disconnected.
Disconnected.
Socket Error #10051
Network is unavailable
There may be two reasons for the problem:
1 - connection is blocked by security programs
2 - port 25 is closed by the Internet provider.
In the first case - disable security programs and resend the test letter, in the second - contact your Internet provider and ask either to open this port, or use alternative ports for this SMTP server with which it can work and which are not blocked by your Internet -provider.
HELO/HELO rejected You need to open Settings/General Settings/Connection/HELO Value and click "Define".
After that, copy your HELO value and paste it into the appropriate field.
mail.ru blocks as spam Your mailing was accepted as spam on the mail.ru server. This most often happens when you send an empty letter.
You need to follow the link “http://mail.ru/notspam/” to receive details, or write a letter to « [email protected]» .
Contact mail.ru and explain that your mailing list is not spam and demand to know why they are blocking it. Or use a different SMTP server
“Dispatching...” very long If the status "Dispatching..." has been hanging for quite a long time (more than a minute), please check the following:
1. The prepared message is large in size and ePochta Mailer takes longer to send it.
2. ePochta Mailer is completely blocked from Internet access by an antivirus or firewall. Set an exception for ePochta Mailer.
Error 450: Requested mail action not taken: mailbox unavailable. The server cannot access the mailbox to deliver the message. This may be caused by the server's dead address purge process, the mailbox may be corrupted, or the mailbox may be on another server that is not currently accessible. Also, the network connection may have been broken during sending, or the remote mail server does not want to accept mail from your server for some reason (IP address, blacklists, etc.). A second attempt to send a letter to this mailbox may be successful.
Error 451: Requested action aborted: local error in processing. This error usually occurs due to your ISP being overloaded or too many messages being sent through your SMTP relay. The next attempt to send a letter may be successful.
Error 500: Syntax error, command unrecognized. Your antivirus/firewall is blocking incoming/outgoing SMTP connections. You should configure your antivirus/firewall to resolve the issue.
Error 501: Syntax error in parameters or arguments. Invalid email addresses or domain name of the mailing address. Sometimes indicates connection problems.
Error 503: Bad sequence of commands or this mail server requires authentication. Repeated 503 errors may indicate connection problems. A 503 response from the SMTP server is most often an indication that the SMTP server requires authentication, and you are trying to send a message without authentication (login + password). Check General Settings to ensure the SMTP server settings are correct.
Error 512: The host server for the recipient’s domain name cannot be found (DNS error). One of the servers on the path to the destination server has a problem with the DNS server or the recipient address is incorrect. Check the recipient's address for the correct domain name (spelling errors in the domain name or non-existent domain name).
Error 513: Address type is incorrect or authentication required. Make sure the recipient's email address is correct and free of errors. Then try resending the message. Another reason could be that the SMTP server requires authentication, and you are trying to send a message without authentication (usually ESMTP authentication, login + password). Check General Settings to ensure the SMTP server settings are correct.
Error 523: The Recipient's mailbox cannot receive messages this big. The message size (message + all its attachments) exceeds the size limits on the recipient's server. Check the size of the message you have prepared to send, in particular the size of the attachments; it may be worth splitting the messages into parts.
Error 530: Access denied. Your provider's SMTP server requires authentication, and you are trying to send a message without authentication (login + password). Check General Settings to ensure the SMTP server settings are correct. Another reason could be that your SMTP server is blacklisted by the recipient's server. Or the recipient's mailbox does not exist.
Error 535: Username and Password not accepted. Check your SMTP server settings. Make sure that the username and password are entered correctly. Open “Settings”/ “General Settings”/ “SMTP”, there double click on the SMTP server address, and in the window that appears, correct the username and password.
Note 1: Make sure CAPS LOCK is turned off - this is important!
Note 2: Some SMTP servers require a login « [email protected]» instead of just "user", clarify these points.
Error 541: Recipient Address Rejected - Access denied. This response is almost always sent by the Antispam filter on the recipient's side. Check your message with a spam checker or ask the recipient to whitelist you.
Error 550: Mailbox unavailable. A 550 response from the SMTP server means that the recipient's email address is not on the server. Contact the recipient verbally to obtain their email address. Error 550 can sometimes be sent by the Antispam filter. Another case of a 550 response being returned would be when the recipient's server is down.
Error 552: Requested mail action aborted: exceeded storage allocation or size of the incoming message exceeds the incoming size limit. The recipient's mailbox has reached its maximum allowed size. Another case of a 552 response being returned is when the size of the incoming message exceeds the limit specified by the network administrator.
Error 553:Requested action not taken - Mailbox name invalid. Invalid recipient email address. A 553 response from the SMTP server is sometimes returned by your ISP's mail server. This happens if you do not have an Internet connection with this provider.
Error 554: Transaction failed. Response 554 from the SMTP server is returned by the antispam filter if the sender's email address, or the sender's IP address, or the sender's mail server is not liked (for example, they are located in RBL). You need to either ask the sender to add you to the whitelist, or you must take steps to have your IP address or ISP server removed from the RBL (Realtime Blackhole List).

Top