Submitted by Deepakkr3110 on Tue, 04/27/2021 - 06:30
Hello
I am getting the error:
warning: unknown[1.210.20.73]: SASL LOGIN authentication failed: authentication failure
but when I check
[root@ conf.d]# testsaslauthd -u alok@qbc.in -p qbc@123 0: OK “Success.”
Status:
Closed (won't fix)
Virtualmin version:
6.16
Webmin version:
1.973
Comments
Submitted by JamieCameron on Tue, 04/27/2021 - 18:09 Comment #1
Is anything else logged to /var/log/mail.log or /var/log/secure or /var/log/authlog ?
Submitted by Deepakkr3110 on Wed, 04/28/2021 - 00:43 Comment #2
In /var/log/maillog
Apr 28 11:09:07 web2 postfix/smtpd[4226]: warning: unknown[12.70.149.5]: SASL LOGIN authentication failed: authentication failure
and in tail -f /var/log/secure
Apr 28 11:08:34 web2 auth: pam_unix(dovecot:auth): check pass; user unknown Apr 28 11:08:34 web2 auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=long@abc.in rhost=14.94.14.97 Apr 28 11:08:53 web2 sshd[8234]: Accepted password for root from 103.212.156.161 port 61429 ssh2 Apr 28 11:08:53 web2 sshd[8234]: pam_unix(sshd:session): session opened for user root by (uid=0) Apr 28 11:08:58 web2 auth: pam_unix(dovecot:auth): check pass; user unknown Apr 28 11:08:58 web2 auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=ofx@abc.in rhost=14.94.14.97
Submitted by JamieCameron on Thu, 04/29/2021 - 00:47 Comment #3
Is
long@abc.in
actually the correct username? Normally Virtualmin will create a user likelong-abc
for the email addresslong@abc.in
Submitted by Deepakkr3110 on Thu, 04/29/2021 - 02:36 Comment #4
user like long-abc for the email address long@abc.in i have this format.
Submitted by JamieCameron on Thu, 04/29/2021 - 22:34 Comment #5
But in the dovecot logs, it looks like the mail client is trying to login as long@abc.in
Submitted by Deepakkr3110 on Fri, 04/30/2021 - 01:54 Comment #6
yes, even this error ("SASL LOGIN authentication failed: authentication failure") shows with valid-user. so can you tell me the solution?
I have this setting in my /etc/sysconfig/saslauthd
Directory in which to place saslauthd's listening socket, pid file, and so on. This directory must already exist.SOCKETDIR=/run/saslauthd
Mechanism to use when checking passwords. Run "saslauthd -v" to get a list of which mechanism your installation was compiled with the ablity to use. MECH=pamMECH="rimap -r"
Additional flags to pass to saslauthd on the command line. See saslauthd(8) for the list of accepted flags. FLAGS="-r"FLAGS = "-O webmail2.abc.in"
OPTIONS="-c -m /var/run/saslauthd -r" PARAMS="-m /var/run/saslauthd -r" [root@webmail2 ~]#
Submitted by JamieCameron on Sat, 05/01/2021 - 13:21 Comment #7
Did you customize anything in
/etc/sysconfig/saslauthd
after the default install?Submitted by Deepakkr3110 on Mon, 05/03/2021 - 00:41 Comment #8
I don't remember, can you help me with the default setting?
Submitted by JamieCameron on Mon, 05/03/2021 - 23:30 Comment #9
I can check on another system ... are you running CentOS 7?
Submitted by Deepakkr3110 on Tue, 05/04/2021 - 01:09 Comment #10
Yes i am running CentOS 7
Submitted by JamieCameron on Wed, 05/05/2021 - 20:09 Comment #11
The file should just contain :
Submitted by Deepakkr3110 on Wed, 05/05/2021 - 23:23 Comment #12
Hello
I have added this files but i am getting the same error:
[root@webmail2 styles]# systemctl status saslauthd ● saslauthd.service - SASL authentication daemon. Loaded: loaded (/usr/lib/systemd/system/saslauthd.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2021-05-06 09:48:31 IST; 9s ago Process: 31861 ExecStart=/usr/sbin/saslauthd -m $SOCKETDIR -a $MECH $FLAGS (code=exited, status=0/SUCCESS) Main PID: 31862 (saslauthd) CGroup: /system.slice/saslauthd.service ├─31862 /usr/sbin/saslauthd -m /run/saslauthd -a pam -r ├─31863 /usr/sbin/saslauthd -m /run/saslauthd -a pam -r ├─31864 /usr/sbin/saslauthd -m /run/saslauthd -a pam -r ├─31865 /usr/sbin/saslauthd -m /run/saslauthd -a pam -r └─31866 /usr/sbin/saslauthd -m /run/saslauthd -a pam -r
May 06 09:48:35 webmail2.abc saslauthd[31862]: pam_unix(smtp:auth): check pass; user unknown May 06 09:48:35 webmail2.abc saslauthd[31862]: pam_unix(smtp:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= May 06 09:48:37 webmail2.abc saslauthd[31862]: DEBUG: auth_pam: pam_authenticate failed: User not known to the underlying authentication module May 06 09:48:37 webmail2.abc saslauthd[31862]: do_auth : auth failure: [user=test] [service=smtp] [realm=] [mech=pam] [reason=PAM auth error] May 06 09:48:37 webmail2.abc saslauthd[31865]: pam_unix(smtp:auth): check pass; user unknown May 06 09:48:37 webmail2.abc saslauthd[31865]: pam_unix(smtp:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= May 06 09:48:40 webmail2.abc saslauthd[31865]: DEBUG: auth_pam: pam_authenticate failed: User not known to the underlying authentication module May 06 09:48:40 webmail2.abc saslauthd[31865]: do_auth : auth failure: [user=test] [service=smtp] [realm=] [mech=pam] [reason=PAM auth error] May 06 09:48:40 webmail2.abc saslauthd[31864]: pam_unix(smtp:auth): check pass; user unknown May 06 09:48:40 webmail2.abc saslauthd[31864]: pam_unix(smtp:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=
in maillog
May 6 09:49:09 webmail2 postfix/smtpd[31682]: warning: unknown[15.231.143.11]: SASL LOGIN authentication failed: authentication failure May 6 09:49:10 webmail2 postfix/smtpd[31682]: lost connection after AUTH from unknown[15.231.143.11] May 6 09:49:10 webmail2 postfix/smtpd[31682]: disconnect from unknown[15.231.143.11] May 6 09:49:10 webmail2 postfix/smtpd[30269]: connect from unknown[15.231.143.11] May 6 09:49:12 webmail2 postfix/smtpd[30269]: warning: unknown[15.231.143.11]: SASL LOGIN authentication failed: authentication failure May 6 09:49:12 webmail2 postfix/smtpd[30269]: lost connection after AUTH from unknown[15.231.143.11]
Submitted by andreychek on Thu, 05/06/2021 - 08:59 Comment #13
If doesn't appear that you're experiencing a bug there.
We're sorry, but as you're using Virtualmin GPL there, if you had any additional questions, you'd want to use the Forums for support.
We monitor the Forums, along with lots of wonderful folks in the community.
Thanks!