Smtp ошибка 454 ошибка авторизации roundcube

Wondering how to fix Roundcube SMTP error (454) authentication failed? We can help you!

This error is often seen while trying to send emails via Roundcube. Here at Bobcares, we often handle requests from our customers to fix similar Roundcube errors.

Today we will see how our support engineers fix this for our customers as a part of our Server Management Services.

What causes Roundcube ‘SMTP error (454) authentication failed’

Before going into the steps for fixing this error, we will see what causes this error and how it looks like.

A typical error may look like the one given below:

SMTP Error: Authentication failure: Invalid response code received from server (Code: 454)

The following warnings will appear in the /var/log/maillog if we get this error :

Mar 20 22:13:01 postfix/smtpd[28890]: warning: SASL authentication failure: no secret in database
Mar 20 22:13:01 postfix/smtpd[28890]: warning: localhost[::1]: SASL DIGEST-MD5 authentication failed: authentication failure

Following are the two main causes for this error:

  •  Broken Postfix configuration.
  •  The pc-remote service is stopped.

Methods to fix Roundcube ‘SMTP error (454) authentication failed’

Now we will see how our Support engineers fi this error for our customers.

1. Fixing Broken Postfix configuration.

Here we will reinstall Postfix by switching to Qmail and back to Postfix.

This can the done in the following ways.

Using Plesk Installer:

The steps to follow are given below:

  1. Firstly, go to Plesk and take Tools & Settings.
  2. Then go to Updates and Upgrades.
  3. And take Add/Remove Components then go to Mail hosting.
  4. After that take SMTP servers and select the Qmail server.
  5. Next, we have to click Continue to start the installation.
  6. Once the installation is complete click Ok.
  7. Now go to Add/Remove Components and take Mail hosting.
  8. From Mail hosting go to SMTP servers.
  9. Select Postfix mail server and click Continue to start the installation.
  10. Once the installation is complete click Ok.
Using Command Line Interface (CLI):

We can use the following steps for fixing this via CLI:

  1. First, we have to connect to the server via SSH;
  2. Then execute the following commands:
# plesk installer --select-release-current --install-component qmail
# plesk installer --select-release-current --install-component postfix

2. Starting pc-remote service

This error can also occur if the pc-remote service is stopped. However, the error in the /var/log/maillog appears a little different as shown below:

warning: connect to Milter service inet:127.0.0.1:12768: Connection refused NOQUEUE: milter-reject: CONNECT from example.com[203.0.113.2]: 451 4.7.1 Service unavailable – try again later; proto=SMTP

Following are the steps to fix this:

  1. First, we have to log in to Plesk.
  2. Then go to Tools & Settings and Scheduled Tasks.
  3. From there take Add Task.
  4. After that select Task Type as Run a command
  5. In the Command * field paste the line below:
/usr/sbin/service pc-remote start

6. Now we have to select root from the drop-down menu System user

7. Finally click the Run Now button to start the pc-remote service.

[Need assistance? We can help you]

Conclusion

In short, we saw how our Support Engineers fix Roundcube ‘SMTP error (454) authentication failed’ issue for our customers.

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.

GET STARTED

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Источник

Roundcube SMTP Error (454) Authentication Failed happens while trying to send emails via Roundcube. It generally occurs as a result of PostFix configuration issues.

Here at Ibmi Media, as part of our Server Management Services, we regularly help our Customers to handle requests relating to Roundcube errors.

In this context, we shall look into how to resolve this SMTP Error.

Nature of Roundcube ‘SMTP error (454) authentication failed’

Roundcube ‘SMTP error (454) authentication failed’ error may look like the one given below:

SMTP Error: Authentication failure: Invalid response code received from server (Code: 454)

The following warnings will appear in the /var/log/maillog if we get this error :

Mar 20 22:13:01 postfix/smtpd[28890]: warning: SASL authentication failure: no secret in database
Mar 20 22:13:01 postfix/smtpd[28890]: warning: localhost[::1]: SASL DIGEST-MD5 authentication failed: authentication failure

The main causes for this error are:

  • Broken Postfix configuration.
  • The pc-remote service is stopped.

How to fix Roundcube ‘SMTP error (454) authentication failed’ ?

1. Fixing Broken Postfix configuration.

Here we will reinstall Postfix by switching to Qmail and back to Postfix.

This can the done in the following ways.

i. Using Plesk Installer:

The steps to follow are given below:

  • Firstly, go to Plesk and take Tools & Settings.
  • Then go to Updates and Upgrades.
  • And take Add/Remove Components then go to Mail hosting.
  • After that take SMTP servers and select the Qmail server.
  • Next, we have to click Continue to start the installation.
  • Once the installation is complete click Ok.
  • Now go to Add/Remove Components and take Mail hosting.
  • From Mail hosting go to SMTP servers.
  • Select Postfix mail server and click Continue to start the installation.
  • Once the installation is complete click Ok.

ii. Using Command Line Interface (CLI):

We can use the following steps for fixing this via CLI:

a. First, we have to connect to the server via SSH;

b. Then execute the following commands:

# plesk installer --select-release-current --install-component qmail
# plesk installer --select-release-current --install-component postfix

2. Starting pc-remote service

This error can also occur if the pc-remote service is stopped. However, the error in the /var/log/maillog appears a little different as shown below:

warning: connect to Milter service inet:127.0.0.1:12768: Connection refused NOQUEUE: milter-reject: CONNECT from example.com[203.0.113.2]: 451 4.7.1 Service unavailable – try again later; proto=SMTP

To fix this SMTP Connection error:

i. First, we have to log in to Plesk.

ii. Then go to Tools & Settings and Scheduled Tasks.

iii. From there take Add Task.

iv. After that select Task Type as Run a command

v. In the Command * field paste the line below:

/usr/sbin/service pc-remote start

vi. . Now we have to select root from the drop-down menu System user.

vii. Finally click the Run Now button to start the pc-remote service.

[Need assistance in fixing SMTP errors? We can help you. ]

Источник


0

1

Всем привет. Я полный линуксонуб, но так вышло, что я админю сервер, на котором крутятся сайты, ну как админю, на нем установлена панель управления plesk, и почти все сводится к настройкам через нее,но не в этот раз.
Ни с того ни с сего перестала работать почта на сервере. До этого два года работал без всяких проблем. Всё, что я менял, это для одного из доменов прописывал A запись на внешнюю яндекс почту, но это даже другой домен. Веб-приложение roundcube, которое используется для отправки почты, стало выдавать такую ошибку при отправке: «SMTP Error (454): Ошибка авторизации»
Я усердно гуглил, как бы это исправить, но ничего не нагуглил.
Я даже не могу найти конфиг rouncube, какие-то конфиги нахожу, но они совсем не похожи на то, что пишут на форумах.
В логах roundcube(/var/log/plesk-roundcube/errors) сплошные ворнинги, не вижу там никаких ошибок, а может это не тот лог, вот последний кусок 

[15-Feb-2016 18:45:39 UTC] PHP Warning:  date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /usr/share/psa-roundcube/program/lib/Roundcube/rcube_db.php on line 758

Нашел еще лог maillog (usr/local/psa/var/log)
Пишет, что какой-то сервис не доступен 

Feb 15 20:48:28 km20833-24 postfix/cleanup[29971]: warning: connect to Milter service unix:/var/spool/postfix/ctmilter/ctmilter.sock: No such file or directory
Feb 15 20:48:28 km20833-24 postfix/cleanup[29971]: 996BB8FE25F3: milter-reject: CONNECT from localhost[127.0.0.1]: 4.7.1 Service unavailable - try again later; from=<root@km20833-24.keymachine.de>
Feb 15 20:48:28 km20833-24 postfix/pickup[28439]: warning: 9996A8FE25F3: message has been queued for 1 days
Feb 15 20:48:28 km20833-24 postfix/pickup[28439]: 9996A8FE25F3: uid=0 from=<root>
Feb 15 20:48:28 km20833-24 postfix/cleanup[29971]: warning: connect to Milter service unix:/var/spool/postfix/ctmilter/ctmilter.sock: No such file or directory
Feb 15 20:48:28 km20833-24 postfix/cleanup[29971]: 9996A8FE25F3: milter-reject: CONNECT from localhost[127.0.0.1]: 4.7.1 Service unavailable - try again later; from=<root@km20833-24.keymachine.de>
Feb 15 20:48:28 km20833-24 postfix/pickup[28439]: warning: 99BA48FE25F3: message has been queued for 4 days
Feb 15 20:48:28 km20833-24 postfix/pickup[28439]: 99BA48FE25F3: uid=10000 from=<volfilarmonia>
Feb 15 20:48:28 km20833-24 postfix/cleanup[30003]: warning: connect to Milter service unix:/var/spool/postfix/ctmilter/ctmilter.sock: No such file or directory
Feb 15 20:48:28 km20833-24 postfix/cleanup[30003]: 99BA48FE25F3: milter-reject: CONNECT from localhost[127.0.0.1]: 4.7.1 Service unavailable - try again later; from=<volfilarmonia@km20833-24.keymachine.de>

Подскажите, плиз, куда копать? Саппорт хостинга меня посылает и просит подписку купить, чтобы они мне помогали в таких вопросах.

Источник

Roundcube is a free and open source webmail tool. That’s why it’s adopted by many admins as part of email management practice. But as with other tools, you’re likely to come across a few errors from time to time. And one of them is the SMTP (454) Error. You’ll get this error when trying to send emails using Roundcube. If you’re stuck with this error, you might be looking for ways to fix it. In this article, learn how to solve the SMTP authentication failed error in Roundcube.

Why this Error Occurs?

Before fixing the error, it’s worth learning about the cause.

When you see this error, you’ll receive a message that reads, “SMTP Error: Authentication failure: Invalid response code received from server (Code: 454)”

If you get the following error, then you can access it at /var/log/maillog:

Code: 

“Jun 20 21:10:02 postfix/smtpd[28890]: warning: SASL authentication failure: no secret in database
Jun 20 21:10:03 postfix/smtpd[28890]: warning: localhost[::1]: SASL DIGEST-MD5 authentication failed: authentication failure”

The two main reasons behind this error are:

  • Postfix configuration is broken
  • Pc-remote service is stopped

How to Fix the Error?

How to fix the error will depend on the reason behind the error. So you need to follow the appropriate solution.

  • Fixing the Broken Postfix config

When the postfix configuration is broken, you’d have to reinstall Postfix. You can do this by first moving to Qmail briefly and then jump back to Postfix. This can be done in a couple of ways.

Use Plesk Installer

Here are the steps to follow:

  • Go to Plesk and then take Tools & Settings
  • Then navigate into Updates.

plesk1.png

  • Take Add/Remove Components and then navigate into Mail hosting.

plesk2.png

  • Take SMTP servers and then select Qmail server
  • Select “Continue” to initiate the installation process
  • After the process is done, click on OK
  • Navigate into Add/Remove Components and take Mail hosting
  • Then navigate into SMTP servers to select Postfix mail
  • Click on Continue to begin the installation process
  • Once done, click on OK

Using CLI

You can use the Command Line Interface as well. Here are the steps involved:

  • Connect to your server using SSH terminal
  • Run the below commands:

Code: 

# plesk installer --select-release-current --install-component qmail
# plesk installer --select-release-current --install-component postfix

Pc-remote Service is Stopped

If this is the reason, then you have to start the service.

Another thing to note is that there will be a difference in the error message you get. If you open the /var/log/maillog file, you’ll notice the following message:

Code: 

warning: connect to Milter service inet:127.0.0.1:12768: Connection refused NOQUEUE: milter-reject: CONNECT from example.com[203.0.113.2]: 451 4.7.1 Service unavailable – try again later; proto=SMTP

To fix this, you’d have to follow these steps:

  • Log in to your Plesk account
  • Open Tools & Settings and then Scheduled Tasks

plesk3.png

  • Take Add Task

plesk4.png

  • Select Task Type as Run a Command
  • When you see the Command* section, paste this line —

Code: 

/usr/sbin/service pc-remote start

  • For the section “System User” select “root” from the drop down menu
  • Tap on the “Run Now” button to start the service

So that’s how you fix the SMTP (454) error.

Источник

Virtualmin Community

Loading

Источник

Понравилась статья? Поделить с друзьями:
  • Smtp ошибка 450
  • Smtp ошибка 220 ошибка авторизации roundcube
  • Smtp код ошибки 535
  • Slui exe ошибка приложения
  • Smtp yandex ошибка 535