SMTP - "Authentification failed" #1629
Comments
|
@Chialya some logs would be good to get the problem resolved: Enable logging by editing this file: /usr/local/lib/rainloop/data/data/default/configs/application.ini Logging will start, replicate the issue and attach the logs here Also if you can get a copy of your tail /var/log/mail.log or smtp server logs Feel free to strip them of IPs and usernames |
|
Hi djdill, thank you for you answer. I've searched the log bevore, but there is nothing I can do with it (no cause). [Bild1] Here is the current setting.
I guarantee that this setting will work for other programs! So only rainloop can reach the mail-server over localhost. Interesting is, that ssl://127.0.0.1:993 is working, although the certificate does not contain 127.0.0.1. [Bild2]
In the log i've stripped domain wih XXXXX, username with AAAAAAAAAA and password with BBBBBBBBBB.
535 5.7.8 Error: authentication failed: authentication failure\r\n Thanks for helping. |
everything seems to be correct but what is this ?:
|
|
First thing you need to delete your comments above (the logs) Second thing, Also one thing you can try is test to see if you can connect to the smtp server on cli via the host: openssl s_client -debug -starttls smtp -crlf -connect localhost:587 You can test it using your password (after you change it) and username |
|
Best recommendation to get this fixed is to move to another smtp server on the same box that supports auth using email address. you can run that side by side on another port if you don't want to remove your current server |
|
Hi Djdill, Trying an other mail-server ist not possible for me. That's technically very difficult! Nextcloud Apps -> Version 5.0.6 (https://apps.nextcloud.com/apps/rainloop) |
|
Good to see you have changed passwords, the way that SMTP works is it encodes the username / passwords in the PLAIN AUTH part, so both where readable. I am going to see if I can replicate your issue later and will post back if I can confirm this bug.
That is good, your log files show that too, I don't know why I was thinking you are on 1.11.2 |
|
So your rainloop install is broken - I have run testing, Checked the logs and found the line: The BASE64 encoded text above will be like this in plain text: \000ShortUserName\000Password Have a look here: https://www.base64decode.org/ Have a look at your logs again.. Try to auth (Fail) and then copy the Anyway two options: Remove rainloop from next cloud, then go to the data folder on the nextcloud install and delete the rainloop-data folder all together Create a new rainloop install outside of nextcloud by following this guide: Depending on your web server www localtion: mkdir /var/www/html/rainloop Then http://webmail.domain.com/?admin Setup again and test - let me know |
|
Hello, it's almost the end of 2019 and it seems like this issue is still alive... at least kind off. Testing the smtp and imap server works without any issue, logging in too. The problem is that if I try to send a Mail, I get the "authentification failed" warning as visible in the above post. I'm running RainLoop in Nextcloud 17 and even tried a drect install on my QNAP NAS showing the same problems. Thanks in advance! |
|
Hello Terra, While studying the connection-logs from nextcloud, I read out the detailed logs from my SMTP-Server too. So I set it to log-mode=5. But Attention /!\ There are more than 1000 lines in the log with only 1 connection attempt! I testet other clients like MS-Outlook and K9-Mail on phone, which worked great. I read out thousand of thousand lines in the logs. And in the depths of the records I found the reason why the SMTP-Server refused the connection. It was because the Base64 token had to contain the username and password both in 1 line! Rainloop tried to connect a 2-line authentication, and this was rejected by my SMTP-Server. I took the Rainloop-App apart and searched for the connection method - line by line! As I wanted to rewrite it, I found a simple switch: I have edited the file:
Then it works on my Synology NAS (probably also on your QNAP). I've done thousands of lines in the logs, several lines of source code and many experiments to work on the problem. So hope it helps you as well. Good luck |
|
Hey Chiala, Terra |
|
Yeah, setting $__USE_SINGLE_LINE_AUTH_PLAIN_COMMAND to true fixed this issue for me connecting to a dovecot mail server, too. Thanks! |
|
@djdill |
|
For me the problem was short login, I unselect and all solved.... |
Adding my $0.02....This was an issue for me, as well. I could get data from an email server, but could not send from my Nextcloud snap v19.0.2 with Rainloop 1.1.14 public $__USE_SINGLE_LINE_AUTH_PLAIN_COMMAND = false; Thnx for posting, @Chialya !!! |
|
I am also facing thre same problem but the above solution did not work for me. Anything else I should try? @Chialya Where did you set the log level ? |
|
I have this problem recurring.
|
|
@vtolenti89: and
|
|
@monzerfoda: setting is ?
First try modify:
OR try verify:
"auth_mechanisms" must be "plain" for 1-line and "login" for 2-line authentication to accept both. Rainloop uses 2-line authentication by default ! |
|
I debugged the code and found the error. Accurate login information Login information attempted by rainloop I fixed the error by modifying file(rainloop/v*/app/libraries/RainLoop/Model/Account.php). |
|
What did you changed exactly |
|
There is no "error"! |
While I'm here, * Switch to DISTVERSION * Pet portclippy * Re-format Makefile with portfmt Reference: RainLoop/rainloop-webmail#1629 PR: 257017 Reported by: pi Obtained from: RainLoop/rainloop-webmail#1629 (comment) MFH: 2021Q4
While I'm here, * Switch to DISTVERSION * Pet portclippy * Re-format Makefile with portfmt Reference: RainLoop/rainloop-webmail#1629 PR: 257017 Reported by: pi Obtained from: RainLoop/rainloop-webmail#1629 (comment) MFH: 2021Q4
While I'm here, * Switch to DISTVERSION * Pet portclippy * Re-format Makefile with portfmt Reference: RainLoop/rainloop-webmail#1629 PR: 257017 Reported by: pi Obtained from: RainLoop/rainloop-webmail#1629 (comment) MFH: 2021Q4
While I'm here, * Switch to DISTVERSION * Pet portclippy * Re-format Makefile with portfmt Reference: RainLoop/rainloop-webmail#1629 PR: 257017 Reported by: pi Obtained from: RainLoop/rainloop-webmail#1629 (comment) MFH: 2021Q4
While I'm here, * Switch to DISTVERSION * Pet portclippy * Re-format Makefile with portfmt Reference: RainLoop/rainloop-webmail#1629 PR: 257017 Reported by: pi Obtained from: RainLoop/rainloop-webmail#1629 (comment) MFH: 2021Q4
While I'm here, * Switch to DISTVERSION * Pet portclippy * Re-format Makefile with portfmt Reference: RainLoop/rainloop-webmail#1629 PR: 257017 Reported by: pi Obtained from: RainLoop/rainloop-webmail#1629 (comment) MFH: 2021Q4 (cherry picked from commit 09c2f9d)
RainLoop v1.11.3 App integrated in Nextcloud 12.0.4
System is running on Synology NAS using: Apache 2.4, PHP 7.0
Mail Server v1.6.4 from Synology on same machine (via localhost reachable)
I can't send mails, when SMTP-encryption (SSL/TLS) is used.
Error: Authentification failed
no matter what I choose:
only the way SMTP without encryption and without authentication works !
"other mail-clients" on the same machine (connect via localhost),
or apps on mobilephone (connect via domain) ect,
with the same login-data, works fine !!
the challenge is, that the mail-server request a username, not mail-address !
so I select the option: "use short usernames"
using IMAP with SSL and sending mails without SSL works also fine with my settings.
I think there is a problem with "use short username" on SMTP
so the mail-server doesn't get the correct login for authentication.
so please help me
thanks :)
1st picture shows the error message when SSL is enabled
2nd picture the only granted settings - but not using SSL/TLS !
3rd picture is a sample from Windows10 Mail-App with working settings.
The text was updated successfully, but these errors were encountered: