Timeline for POSTFIX SASL Authentication ERROR
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 13, 2020 at 14:43 | comment | added | madcap | The answer is that smtpd and saslauthd disagree on the name. The lsof output you posted earlier shows that sslauthd is listening on /run/saslauthd/mux. If your postfix is running chroot to some directory, then it can't access that path. So you have to change the pathname that sslauthd is listening on to something that postfix can access. You need to figure out which directory your postfix is chrooted to, (for me, that is /var/spool/postfix, but it seems that you are not running the same OS as I do), and then figure out how to pass startup options to sslauthd. | |
| Oct 12, 2020 at 17:14 | comment | added | Naga | Sorry about the late reply. This Change doesnt work either : private/saslauthd/mux to /run/saslauthd/mux. I am not sure what you meant in the second statement. I am new to this email server configuration, Could you please kindly let me know with more information ? Still the same error : warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory warning: unknown[99.999.99.999]: SASL LOGIN authentication failed: generic failure | |
| Oct 7, 2020 at 9:15 | comment | added | madcap | Try changing saslauthd_path: private/saslauthd/mux to /run/saslauthd/mux. If that does not work, your postfix is running chroot. Mine is, and then you need to change it back, and figure out how to pass -m /var/spool/postfix/private/sslauthd to ssslauthd. Your postfix might yous another root directory. | |
| Oct 7, 2020 at 8:34 | comment | added | Naga | This command also doesnt given an output. sudo lsof -c smtpd | more | |
| Oct 6, 2020 at 14:49 | comment | added | madcap | Your lsof does not have the same output format as mine. For me, the third line contains the root directory for the process. The FD is "rtd" and the TYPE is "DIR" and NAME is "/var/spool/postfix". Try sudo lsof -c smtpd | more, and you can probably figure it out. You already have the pathname that sslauthd is using, which in not same as you have configured smtpd to use. | |
| Oct 6, 2020 at 14:02 | comment | added | Naga | sudo lsof -c smtpd | grep rtd --> this gives no output | |
| Oct 6, 2020 at 14:02 | comment | added | Naga | Actuall the command gives more output, but due to the space constraint, i have placed the first two line. ---> sudo lsof -c saslauthd | grep unix saslauthd 23203 root 3u unix 0xffff888079bbcc00 0t0 3194590 socket saslauthd 23203 root 5u unix 0xffff888079bbc400 0t0 3194591 /run/saslauthd/mux | |
| Oct 6, 2020 at 13:32 | comment | added | madcap | You can use the the command sudo lsof -c saslauthd | grep unix to see all unix domain sockets that saslauthd has open. You can also use sudo lsof -c smtpd | grep rtd to see if postfix is chrooted. | |
| Oct 6, 2020 at 13:03 | comment | added | Naga | The daemon is running : i checked with the status command. But I didnt get your second point ---> or that smtpd and saslauthd disagree on the name. How can i check this ?? | |
| Oct 6, 2020 at 12:51 | history | edited | madcap | CC BY-SA 4.0 | deleted 1 character in body |
| Oct 6, 2020 at 12:44 | history | answered | madcap | CC BY-SA 4.0 |