Roundcube smtp ошибка 250 ошибка авторизации - Не ошибается лишь тот, кто ничего не делает!

Authentication errors are always annoying, especially when you’re sure the logins are correct.

One such error in Roundcube is “SMTP error 250 authentication failed“.

This usually happens when customers try to send emails from their Roundcube webmail client.

At Bobcares, we resolve these email errors as part of Dedicated Support Services to our customers.

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

Roundcube SMTP error 250 authentication failed – A Brief idea

Most web hosts now use SMTP AUTH on their servers. This prevents the server from being used as open relays and spam.

SMTP authentication allows the email sender to login to the email server using an authentication mechanism. In other words, only trusted users can send data via the SMTP server.

Customers usually see this error when they try to send emails using Roundcube email client. For instance, the complete error looks like this:

An error has occurred!
SMTP Error (250): Authentication failed.

So, our Support Experts check the mail server logs(/var/log/maillog or /var/log/exim_mainlog) and roundcube error logs. In addition to that, we enable SMTP debugging in roundcube configuration file. For example, on Plesk servers, we add the following code in the roundcube configuration file /usr/share/psa-roundcube/config/defaults.inc.php to enable SMTP debugging.

$config['debug_level'] = 1;
$config['smtp_debug'] = true;

This helps us to identify the origin of the issue.

Roundcube SMTP error 250 authentication failed – Causes & Fixes

Now, let’s see the common reasons for this error and how our Dedicated Engineers fix them.

1) Incorrect authentication settings in SMTP server

Roundcube SMTP error 250 authentication failed usually occurs when there is incorrect SMTP authentication setting in the email server configuration.

For example, one of the common mistakes that we see on Postfix servers is that users enable complex authentication methods such as CRAM MD5 in Postfix mail server. But, Roundcube doesn’t support this authentication. That is, users set the following authentication option in Postifx configuration file /etc/postifx/main.cf.

smtpd_sasl_security_options = noanonymous, noplaintext

This means that the server won’t support normal authentication mechanisms such as LOGIN, PLAIN, etc and roundcube throws this error.

Similarly, on Plesk servers, we’ve seen instances where Postifx is configured for SMTP authentication over TLS, but it’s not configured correctly. This can also create problems.

How we fix?

In such cases, our Support Engineers fix this by enabling PLAIN and LOGIN authentication mechanisms. For example, on Postfix servers, we add the following line.

smtpd_sasl_security_options = noanonymous

Customers can then login and send emails via Roundcube using the username and password.

Moreover, on Plesk servers, we ensure that SMTP authentication is enabled from Tools & Settings > Mail Server Settings > Relay options > Relaying.

In addition to that, we enable SMTP service on port 587 for all IPs from Tools & Settings > Mail Server Settings.

Also, we make sure that the following parameters are disabled in the Postifx configuration file.

smtpd_tls_exclude_ciphers
smtpd_sasl_security_options
smtpd_tls_auth_only
tls_ssl_options

2) Certificate mismatch issues

This usually happens when the mail server is configured to use SSL/TLS, but roundcube is not configured to use the proper certificate.

For example, one of the common mistakes that we see on cPanel servers is that customers setup Roundcube to use TLS for sending.

$config['smtp_server'] = 'tls://localhost;

However, this can sometimes conflicts with the SSL host value in /etc/exim.cert file and create problems.

How we fix?

In such case, our Support Engineers add the server hostname in the Rouncube configuration file.

$config['smtp_server'] = 'tls://serverhostname.com';

Therefore, we confirm that the hostname matches the SSL host in /etc/exim.cert file.

3) Roundcube configuration issues

Most web hosts use port 587 for SMTP authentication. We’ve seen instances where roundcube configuration settings aren’t properly configured to support SMTP authentication.

How we fix?

Here, our Support Engineers ensure that Roundcube is configured properly to support SMTP authentication. Most importantly, we make sure that the following parameters in Roundcube configuration file config.inc.php are set correctly.

$config['default_host'] = 'tls://server.hostname.com';
$config['smtp_port'] = 587;
$config['smtp_auth_type'] = 'LOGIN';

In addition to that, we tweak the following entries in Roundcube configuration file.

$config['smtp_user'] = '%u';
$config['smtp_pass'] = '%p';

In the above setting, Rouncube uses the current user and current user’s password for logging in. This can sometimes create problems. So, for a safer side, we set blank entries for these parameters.

$config['smtp_user'] = ' ';
$config['smtp_pass'] = ' ';

[Need an Expert to look into your annoying email errors? Our Support Engineers are here 24/7].

Conclusion

In short, roundcube SMTP error 250 authentication failed can mainly occur due to SMTP authentication settings in the mail server or in the Roundcube email client. Today, we’ve discussed the main reasons for this error and how our Dedicated Engineers fix them.

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»;

Источник

Доброго дня!

Обустраиваю почтовый сервер на FreeBSD 10.1. Поставил Postfix+Courier+Cyrus+Postfixadmin+Roundcube.

В Roundcube логинюсь нормально, читаю тестовые сообщения отправленные Postfixadmin’ом.

Но не могу отправить ни одного письма. Выдает в интерфейсе: «SMTP ошибка (250): Ошибка авторизации,» — и вот такое в логе Roundcube:

[24-Apr-2015 08:35:26 +0300]: <8ndcaelq> SMTP Error: Authentication failure: SMTP server does not support authentication (Code: ) in /usr/local/www/roundcube/program/lib/Roundcube/rcube.php on line 1714 (POST /rc/?_task=mail&_unlock=loading1429853732832&_lang=undefined&_framed=1?_task=mail&_action=send)

При этом из Windows Live Mail, подключаясь к этому серверу под теми же аккаунтами, спокойно посылаю письма как с авторизацией по SSL, так и без SSL.

В чем может быть проблема, где копать?

Логи:

/var/log/maillog

Apr 24 12:48:13 imap authdaemond: Authenticated: sysusername=<null>, sysuserid=125, sysgroupid=125, homedir=/var/virtualmail, address=valery.krizhevich, fullname=V.K, maildir=metalurgs.lv/valery.krizhevich/, quota=0, options=<null>

Apr 24 12:48:13 imap authdaemond: Authenticated: clearpasswd=12345, passwd=$1$2729ec51$OTSLqnvfyZsQO89JPx6CU0

Apr 24 12:48:13 imap imapd: LOGIN, user=valery.krizhevich, ip=[::ffff:127.0.0.1], port=[25454], protocol=IMAP

Apr 24 12:48:13 imap imapd: LOGOUT, user=valery.krizhevich, ip=[::ffff:127.0.0.1], headers=0, body=0, rcvd=49, sent=340, time=0
Apr 24 12:48:13 imap authdaemond: Authenticated: sysusername=<null>, sysuserid=125, sysgroupid=125, homedir=/var/virtualmail, address=valery.krizhevich, fullname=V.K, maildir=metalurgs.lv/valery.krizhevich/, quota=0, options=<null>

Apr 24 12:48:13 imap authdaemond: Authenticated: clearpasswd=12345, passwd=$1$2729ec51$OTSLqnvfyZsQO89JPx6CU0

Apr 24 12:48:13 imap imapd: LOGIN, user=valery.krizhevich, ip=[::ffff:127.0.0.1], port=[17483], protocol=IMAP

Apr 24 12:48:13 imap imapd: LOGOUT, user=valery.krizhevich, ip=[::ffff:127.0.0.1], headers=0, body=0, rcvd=96, sent=620, time=0

Apr 24 12:48:14 imap authdaemond: Authenticated: sysusername=<null>, sysuserid=125, sysgroupid=125, homedir=/var/virtualmail, address=valery.krizhevich, fullname=V.K, maildir=metalurgs.lv/valery.krizhevich/, quota=0, options=<null>

Apr 24 12:48:14 imap authdaemond: Authenticated: clearpasswd=12345, passwd=$1$2729ec51$OTSLqnvfyZsQO89JPx6CU0

Apr 24 12:48:14 imap imapd: LOGIN, user=valery.krizhevich, ip=[::ffff:127.0.0.1], port=[45124], protocol=IMAP

Apr 24 12:48:14 imap authdaemond: Authenticated: clearpasswd=12345, passwd=$1$2729ec51$OTSLqnvfyZsQO89JPx6CU0

Apr 24 12:48:14 imap imapd: LOGIN, user=valery.krizhevich, ip=[::ffff:127.0.0.1], port=[58540], protocol=IMAP

Apr 24 12:48:14 imap imapd: LOGOUT, user=valery.krizhevich, ip=[::ffff:127.0.0.1], headers=0, body=0, rcvd=178, sent=612, time=0

Apr 24 12:48:14 imap imapd: LOGOUT, user=valery.krizhevich, ip=[::ffff:127.0.0.1], headers=816, body=0, rcvd=320, sent=2130, time=0

Apr 24 12:48:19 imap authdaemond: Authenticated: sysusername=<null>, sysuserid=125, sysgroupid=125, homedir=/var/virtualmail, address=valery.krizhevich, fullname=V.K, maildir=metalurgs.lv/valery.krizhevich/, quota=0, options=<null>

Apr 24 12:48:19 imap authdaemond: Authenticated: clearpasswd=12345, passwd=$1$2729ec51$OTSLqnvfyZsQO89JPx6CU0

Apr 24 12:48:19 imap imapd: LOGIN, user=valery.krizhevich, ip=[::ffff:127.0.0.1], port=[49903], protocol=IMAP

Apr 24 12:48:19 imap imapd: LOGOUT, user=valery.krizhevich, ip=[::ffff:127.0.0.1], headers=0, body=0, rcvd=40, sent=155, time=0

Apr 24 12:48:19 imap authdaemond: Authenticated: clearpasswd=12345, passwd=$1$2729ec51$OTSLqnvfyZsQO89JPx6CU0

Apr 24 12:48:19 imap imapd: LOGIN, user=valery.krizhevich, ip=[::ffff:127.0.0.1], port=[63388], protocol=IMAP

Apr 24 12:48:19 imap imapd: LOGOUT, user=valery.krizhevich, ip=[::ffff:127.0.0.1], headers=0, body=0, rcvd=52, sent=396, time=0

Apr 24 12:48:38 imap postfix/smtpd[1627]: connect from localhost[127.0.0.1]

Apr 24 12:48:38 imap postfix/smtpd[1627]: disconnect from localhost[127.0.0.1]

logs/errors (roundcube)

[24-Apr-2015 12:48:38 Europe/Riga] PHP Deprecated: Non-static method PEAR::isError() should not be called statically, assuming $this from incompatible context in /usr/local/www/roundcube/vendor/pear/net_smtp/Net/SMTP.php on line 448

[24-Apr-2015 12:48:38 Europe/Riga] PHP Deprecated: Non-static method PEAR::raiseError() should not be called statically, assuming $this from incompatible context in /usr/local/www/roundcube/vendor/pear/net_smtp/Net/SMTP.php on line 615

[24-Apr-2015 12:48:38 Europe/Riga] ERROR: SMTP server does not support authentication ()

[24-Apr-2015 12:48:38 +0300]: <snhegkbl> SMTP Error: Authentication failure: SMTP server does not support authentication (Code: ) in /usr/local/www/roundcube/program/lib/Roundcube/rcube.php<==FILE::error==>array (
‘label’ => ‘smtpautherror’,
‘vars’ =>
array (
‘code’ => 250,
),
)::<==sent::LINE==>1714<==LINE::response==>array (
0 => ‘Authentication failure: SMTP server does not support authentication (Code: )’,
) on line 0 (POST /?_task=mail&_unlock=loading1429868925852&_lang=undefined&_framed=1?_task=mail&_action=send)

(Пытался отлаживать раундкьюб, вывел дамп переменных $error и $response в лог.)

Источник

Topic: Can’t send — smtp error 250 (Read 16000 times)

Hello,

I’m doing some testing with roundcube and hoping that it will prove to be a solid webmail client that I can roll out to my users (I administer an email server for a small ISP). I’m really liking what I see so far, but I’m having some issues getting mail to send.

I am able to log in and access my emails. When I try to send a message, though, I get an smtp error 250: authentication failed. The strange part is that my test messages sent out no problem with the installer.

Anyone have thoughts on where I should start with this? The server is running postfix, and does not require authentication to send.

Any tips are greatly appreciated!

Joe

« Last Edit: August 05, 2010, 10:13:35 AM by jgijanto »

Logged

Try changing $rcmail_config[‘smtp_auth_type’] in

/config/main.inc.php to PLAIN if you have no authentication, if that doesn’t work try using LOGIN.

Logged

Hi Skaero,

I tried what you suggested but that doesn’t seem to help, either with PLAIN or LOGIN. I found in the rc/logs folder the following error message:

SMTP Error: SMTP error: Authentication failure: SMTP server does not support authentication (Code: ) in /var/www/rc/program/steps/mail/func.inc on line 1365 (POST /rc/?_task=mail&_action=send)

So it seems like its still trying to use some type of SMTP authentication?

Logged

Enable smtp_debug option and attach logs/smtp file here.

Logged

Ok, with the SMTP debug added here’s what I get from a single attempt to send email:

[06-Aug-2010 08:13:22 -0400]: Recv: 220 mail3.primelink1.net ESMTP server ready.
[06-Aug-2010 08:13:22 -0400]: Send: EHLO 10.100.0.75
[06-Aug-2010 08:13:22 -0400]: Recv: 250-mail3.primelink1.net
[06-Aug-2010 08:13:22 -0400]: Recv: 250-PIPELINING
[06-Aug-2010 08:13:22 -0400]: Recv: 250-SIZE 20240000
[06-Aug-2010 08:13:22 -0400]: Recv: 250-ETRN
[06-Aug-2010 08:13:22 -0400]: Recv: 250 8BITMIME
[06-Aug-2010 08:13:22 -0400]: Send: RSET
[06-Aug-2010 08:13:22 -0400]: Recv: 250 Ok
[06-Aug-2010 08:13:22 -0400]: Send: QUIT
[06-Aug-2010 08:13:22 -0400]: Recv: 221 Bye

I also verified that the server this is running on has relay access to the mail server. Strange too, I looked up the smtp codes and 250 isn’t even an error.

Logged

Your SMTP server doesn’t returns AUTH response. If you really would like to send mail without authentication then you should set smtp_user, smtp_pass and smtp_auth_type to null.

Logged

Same error for me : SMTP ERROR (250) : authentication problem

I just want to tell that if i use the previous version roundcubemail-0.3-stable (always installed) everything works well.
With the new version roundcubemail-0.4 I can’t send an email

An authentication error. Logs enabled in roundcube tells :
SMTP Error: SMTP error: Authentication failure: SMTP server does not support authentication (Code: ) in /var/wws/roundcubemail-0.4/program/steps/mail/func.inc on line 1425 (POST /mail/?_task=mail&_action=send)

I cheked the main.inc.php file twice; put the previous main.inc.php (0.3-stable)
Nothing works.

I have to use the old version 0.3-stable.
I’m disapointed because I would like to use the very interesting feature : threaded view in messages boxes.

Thanks for your help

Logged

Can you post a imap_debug log?

Logged

From my mail.log. Ask me if you want more

With roundcube4 (send an email failure) :

Sep 7 09:03:56 net1 dovecot: imap-login: Login: user=

, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:03:56 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=23/398
Sep 7 09:03:56 net1 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:03:56 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=31/1836
Sep 7 09:03:56 net1 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:03:56 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=408/17090
Sep 7 09:03:56 net1 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:03:56 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=2305/18353
Sep 7 09:03:59 net1 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:03:59 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=34/359
Sep 7 09:03:59 net1 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:03:59 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=31/1836
Sep 7 09:04:10 net1 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:04:10 net1 postfix/smtpd[7207]: connect from net1.domain.net[192.168.0.111]
Sep 7 09:04:10 net1 postfix/smtpd[7207]: disconnect from net1.domain.net[192.168.0.111]
Sep 7 09:04:10 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=8/331

Logged

With roundcube3-stable (send an email to gmail successfull)

Sep 7 09:05:39 net1 dovecot: imap-login: Login: user=

, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:05:39 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=23/398
Sep 7 09:05:39 net1 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:05:40 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=368/18164
Sep 7 09:05:40 net1 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:05:40 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=2455/18703
Sep 7 09:05:44 net1 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:05:44 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=8/331
Sep 7 09:05:44 net1 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:05:44 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=31/1836
Sep 7 09:05:56 net1 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:05:56 net1 postfix/smtpd[7207]: connect from net1.domain.net[192.168.0.111]
Sep 7 09:05:56 net1 postfix/smtpd[7207]: setting up TLS connection from net1.domain.net[192.168.0.111]
Sep 7 09:05:56 net1 postfix/smtpd[7207]: net1.domain.net[192.168.0.111]: TLS cipher list «ALL:+RC4:@STRENGTH»
Sep 7 09:05:56 net1 postfix/smtpd[7207]: SSL_accept:before/accept initialization
Sep 7 09:05:56 net1 postfix/smtpd[7207]: SSL_accept:SSLv3 read client hello B
Sep 7 09:05:56 net1 postfix/smtpd[7207]: SSL_accept:SSLv3 write server hello A
Sep 7 09:05:56 net1 postfix/smtpd[7207]: SSL_accept:SSLv3 write certificate A
Sep 7 09:05:56 net1 postfix/smtpd[7207]: SSL_accept:SSLv3 write key exchange A
Sep 7 09:05:56 net1 postfix/smtpd[7207]: SSL_accept:SSLv3 write server done A
Sep 7 09:05:56 net1 postfix/smtpd[7207]: SSL_accept:SSLv3 flush data
Sep 7 09:05:56 net1 postfix/smtpd[7207]: SSL_accept:SSLv3 read client key exchange A
Sep 7 09:05:56 net1 postfix/smtpd[7207]: SSL_accept:SSLv3 read finished A
Sep 7 09:05:56 net1 postfix/smtpd[7207]: SSL_accept:SSLv3 write session ticket A
Sep 7 09:05:56 net1 postfix/smtpd[7207]: SSL_accept:SSLv3 write change cipher spec A
Sep 7 09:05:56 net1 postfix/smtpd[7207]: SSL_accept:SSLv3 write finished A
Sep 7 09:05:56 net1 postfix/smtpd[7207]: SSL_accept:SSLv3 flush data
Sep 7 09:05:56 net1 postfix/smtpd[7207]: Anonymous TLS connection established from net1.domain.net[192.168.0.111]: TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)
Sep 7 09:05:56 net1 postfix/smtpd[7207]: 6CF146E043: client=net1.domain.net[192.168.0.111], sasl_method=PLAIN, sasl_username=jc2010@domain.net
Sep 7 09:05:56 net1 postfix/cleanup[7211]: 6CF146E043: message-id=<9f068022cf61699d0c59ff3fd9a591bf@localhost>
Sep 7 09:05:56 net1 postfix/qmgr[1524]: 6CF146E043: from=, size=828, nrcpt=1 (queue active)
Sep 7 09:05:56 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=605/1894
Sep 7 09:05:56 net1 postfix/smtpd[7207]: disconnect from net1.domain.net[192.168.0.111]
Sep 7 09:05:56 net1 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:05:56 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=368/18164
Sep 7 09:05:56 net1 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:05:56 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=368/18164
Sep 7 09:05:57 net1 dovecot: imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
Sep 7 09:05:57 net1 dovecot: IMAP(jc2010@domain.net): Disconnected: Logged out bytes=2455/18727
Sep 7 09:05:57 net1 postfix/smtp[7272]: 6CF146E043: to=, relay=gmail-smtp-in.l.google.com[209.85.227.27]:25, delay=0.66, delays=0.01/0.02/0.3/0.33, dsn=2.0.0, status=sent (250 2.0.0 OK 1283843157 v14si8128784weq.13)
Sep 7 09:05:57 net1 postfix/qmgr[1524]: 6CF146E043: removed

Logged

Better use imap_debug and smtp_debug options in Roundcube. Also what do you have in smtp configuration section in main.inc.php?

Logged

// SMTP username (if required) if you use %u as the username RoundCube
// will use the current username for login
$rcmail_config[‘smtp_user’] = ‘jc@domain.net’;

// SMTP password (if required) if you use %p as the password RoundCube
// will use the current user’s password for login
$rcmail_config[‘smtp_pass’] = ‘Mypassword’;

// SMTP AUTH type (DIGEST-MD5, CRAM-MD5, LOGIN, PLAIN or empty to use
// best server supported one)
$rcmail_config[‘smtp_auth_type’] = »;

I also tryed with PLAIN or LOGIN unsuccessfully.

I turned on imap_debug and smtp_debug
And the log is :
[07-sept.-2010 17:21:24] SMTP server does not support authentication ():
[07-Sep-2010 17:21:24 +0200]: SMTP Error: SMTP error: Authentication failure: SMTP server does not support authentication (Code: ) in /var/wws/roundcubemail-0.4/program/steps/mail/func.inc on line 1425 (POST /mail/?_task=mail&_action=send)

Nothing more
Don’t hesitate to ask me more.
Regards

Logged

Have you tried with it with a blank $rcmail_config[‘smtp_user’] and $rcmail_config[‘smtp_pass’]

Logged

OK it works when i leave
$rcmail_config[‘smtp_user’] and $rcmail_config[‘smtp_pass’] blank

But if i understand wenn there’s no more smtp authentication.
It’s not really a problem because mail server accept to relay mail from localhost but the feature is no more.
Am I wrong ?

Regards.

Logged

OK i had some time to watch carefully the problem.
And activating tls
$rcmail_config[‘smtp_server’] = ‘tls://net1.domain.net’;
smtp authentication work properly.

tls protocol was optionnal in 0.3-stable release and must be noted on 0.4 config.

Logged

Источник

So, say you find yourself, somehow having the following error in the roundcube logs:

[27-Sep-2019 12:44:48 +0000]: <f930f680> PHP Error: SMTP server does not support authentication (POST /?_task=mail&_unlock=loading1569588324419&_framed=1&_lang=es&_action=send)
[27-Sep-2019 12:44:48 +0000]: <f930f680> SMTP Error: Authentication failure: SMTP server does not support authentication (Code: ) in /roundcube/program/lib/Roundcube/rcube.php on line 1674 (POST /correo/?_task=mail&_unlock=loading 1569588324419&_framed=1&_lang=es&_action=send)

You have tried everything, but still can’t seem to be able to send email from roundcube, you keep getting this annoying “SMTP (250) authentication failed” notification, every time you click “Send”.

Well… Make sure that your server is connecting to the right place. It took me a while to realize that roundcube was trying to connect to localhost, but somehow the authentication mechanism stopped working (it was before upgrading).

Since I don’t really want to debug too much today (it’s friday after all), and because my configuration/use case is over ssl/tls, the solution to the probem was simply:

$config['smtp_server'] = 'tls://services.host.co';

Et voilà, ma chérie!

Источник

git-pulled from master here. and not sure how to enable debug mode.

and yes, using STARTTLS here. having these config entries for that:

$config['default_host'] = 'tls://myserver.com';
$config['smtp_port'] = 587;
$config['smtp_user'] = '%u';
$config['smtp_pass'] = '%p';

again, seeing these log lines

[12-Mar-2017 09:18:26 Pacific/Auckland] ERROR: SMTP server does not support authentication ()
[12-Mar-2017 09:18:26 Pacific/Auckland] ERROR: Invalid response code received from server (530)
[12-Mar-2017 09:18:26 +1300]: <c2q08p5f> SMTP Error: Authentication failure: SMTP server does not support authentication (Code: ) in /usr/share/roundcubemail/program/lib/Roundcube/rcube.php on line 1657 (POST /?_task=mail&_unlock=loading1489263503734&_lang=en_GB&_framed=1&_action=send)

makes me wonder why brackets are empty in does not support authentication () and why there is no code number in does not support authentication (Code: )

any clues?

Источник

Roundcube SMTP error 250 authentication failed – A Brief idea

Roundcube SMTP error 250 authentication failed – Causes & Fixes

1) Incorrect authentication settings in SMTP server

How we fix?

2) Certificate mismatch issues

How we fix?

3) Roundcube configuration issues

How we fix?

Conclusion

PREVENT YOUR SERVER FROM CRASHING!

<img decoding="async" src="https://www.roundcubeforum.net/Themes/rc/images/topic/hot_post.gif" alt /> Topic: Can’t send — smtp error 250 (Read 16000 times)

Topic: Can’t send — smtp error 250 (Read 16000 times)