Recent searches
Search options
Administered by:
I'm trying to get #Postfix to work with #Cyrus #SASL. This is not the first time, I've done this at least 3 times before, without much hassle.
Not sure what I'm doing wrong this time, or what has changed, but Postfix keeps giving me "SASL authentication failure: Password verification failed", while "testsaslauthd" gives me a nice "0: OK Success." Very frustrating...
Let's go with "it's monday". Getting a bite to eat first, maybe that'll clear things up.
Not sure what I'm doing wrong this time, or what has changed, but Postfix keeps giving me "SASL authentication failure: Password verification failed", while "testsaslauthd" gives me a nice "0: OK Success." Very frustrating...
Let's go with "it's monday". Getting a bite to eat first, maybe that'll clear things up.
social.woefdram.nlSocial.woefdram.nl
Nah, it's not TLS related, I suspect it's Postfix somehow not using (the right?) socket to saslauthd, but I see nothing in the logs. testsaslauthd is happy, using the exact same socket as configured in postfix, correct file permissions, I even run it as sudo postfix. But when I connect to Postfix, I get a fail.
@hans oh boy, this brings back all kinds of mailserver-related trauma 
good luck!
@bazkie bumpercar I've configured SASL lots of times, but almost always with Dovecot/SASL, not Cyrus. But it's frustrating to know I've done this before with Cyrus, I'm even looking at the very config files I created then.
Anyway, I found it. Postfix runs chrooted, of course, and the socket path was correct. But apparently it also needs access to the actual SASL databasefile, which wasn't within the chroot. And that action wasn't visible in my subversioned previous config files...
Documentation, huh?
Anyway, I found it. Postfix runs chrooted, of course, and the socket path was correct. But apparently it also needs access to the actual SASL databasefile, which wasn't within the chroot. And that action wasn't visible in my subversioned previous config files...
Documentation, huh?
@hans ahh that makes sense.. couldn't it just have outputted an error message somewhere saying it wasn't connecting to the db?
@bazkie bumpercar That's what I've been looking for, but the only error I got was "SASL authentication failure: Password verification failed", nothing else. You'd think a nice "can't access database" would be in order.
Well, shows again that you need to maek (and maintain) documentation.