Online store owners using Yandex corporate email on their own domain may encounter a situation where emails from OpenCart suddenly stop being sent, even though the SMTP settings previously worked fine.
For example, a store uses an address like:
info@site.ru
or:
sale@site.ru
The domain email is hosted in Yandex 360, and emails through the website were sent using Yandex's SMTP server. However, at some point, OpenCart starts returning an authorization error or simply stops sending order notifications. The cause may not be in OpenCart or the website settings. Yandex 360 for Business has become a paid service. Starting July 14, 2025, Yandex began disabling the free version of Yandex 360 for Business. Existing customers are being transitioned to the new terms gradually: organizations receive a notification, after which they must select and pay for a suitable plan. If the plan is not paid, the capabilities of the corporate account will be limited. In particular, using a corporate email address to send emails from the site via SMTP stops working properly.
Therefore, the situation where OpenCart email, which has been working for years, suddenly stops sending emails via Yandex could very well be related to a change in Yandex 360's terms.
There are two main options.
This is the simplest option if you want to continue using a corporate address like this:
sale@site.ru
as the company's primary mailbox and simultaneously send emails from OpenCart from it.
After activating a paid plan, corporate email can again be used via standard mail protocols, including SMTP.
If you don't want to buy Yandex 360 just for SMTP, you can use a different mailbox for automated emails from your online store.
For example, create a regular Yandex mailbox:
site-notify@yandex.ru
and use it to send notifications from OpenCart.
In this case, to set up the site, you will need:
You don't need to share your regular email password.
A separate password is created for the site, specifically for connecting email programs and SMTP.
First, you need to log in to the Yandex account that the site will use to send emails.
Site Mail.Yandex showsThe application password is only set upon creation, so it's best to save it immediately.
This is the password you must specify in the SMTP password field in the OpenCart settings.
You can use the following parameters to send emails:
SMTP server: smtp.yandex.ru
Port: 465
Encryption: SSL
Login: full email address
Password: application password
Port 587 with the appropriate encryption method can also be used, but for OpenCart, it's usually more convenient to use SSL and port 465.
You don't need your primary Yandex account password for this.
This is also more secure: if you later need to block a site's access to email, simply delete the corresponding application password. You won't need to change your primary account password.
There is an important limitation here.
If a site logs into Yandex SMTP using the address:
site-notify@yandex.ru
Don't simply specify the sender as:
sale@site.ru
The SMTP server may reject such a sending, since the account used is not authorized to send emails on behalf of another address.
Therefore, it is better to use the technical email address as the sender address.
You can leave your corporate address to receive customer responses.
For example:
Sender:
site-notify@yandex.ru
Reply-to address:
sale@site.ru
In this case, the automatic email is sent via the working SMTP account, and when the customer clicks the " button, the email can be forwarded to the store's corporate address.
If corporate email is used regularly and an address like sale@site.ru should remain the full sender's address, it's easier to connect to the paid Yandex 360.
If SMTP is needed primarily for automatically sending OpenCart notifications, and you don't want to pay for a separate corporate account just for this, you can use a separate regular Yandex email address.
After changing the settings, it is recommended to check:
This way, you can verify that the online store is indeed sending all the necessary notifications and the SMTP issue has been completely resolved.