Hans van Zijst

Hans van Zijst

hans@social.woefdram.nl

Professional nerd and grammar nazi, writes in Dutch and English. Can read some German, French and Spanish too. Learning русский.

Location:: Netherlands

Mon, 07 Aug 2023 20:06:33 +0200

Hans van Zijst

hans@social.woefdram.nl

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.

computers

show all 11 comments

Mon, 07 Aug 2023 22:46:22 +0200

Hans

hans@hubzilla.hopto.org

Debian? Check missing certificates. Seen two people complaining about it

Mon, 07 Aug 2023 22:51:43 +0200

Hans

hans@hubzilla.hopto.org

Ssllabs might give back good info too b.t.w.

Mon, 07 Aug 2023 23:21:33 +0200

Hans van Zijst

hans@social.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.

Mon, 07 Aug 2023 23:45:49 +0200

bazkie bumpercar | unfluencer

bazkie@mstdn.social

@hans oh boy, this brings back all kinds of mailserver-related trauma 🤣 good luck!

Tue, 08 Aug 2023 00:24:26 +0200

Michael Boelen

mboelen@mastodon.social

@hans
It's DNS, or systemd, or the firewall, or GPG, but most likely file permissions, ownership, or selinux/apparmor, or just a fresh reboot 😉

Tue, 08 Aug 2023 00:51:40 +0200

Hans van Zijst

hans@social.woefdram.nl

@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?

Tue, 08 Aug 2023 00:54:15 +0200

Hans van Zijst

hans@social.woefdram.nl

@Michael Boelen That's a pretty wide net you're casting there 😉

Tue, 08 Aug 2023 01:01:26 +0200

bazkie bumpercar | unfluencer

bazkie@mstdn.social

@hans ahh that makes sense.. couldn't it just have outputted an error message somewhere saying it wasn't connecting to the db?

Tue, 08 Aug 2023 01:33:22 +0200

Hans van Zijst

hans@social.woefdram.nl

@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.

Tue, 08 Aug 2023 01:34:16 +0200 last edited: Tue, 08 Aug 2023 01:34:28 +0200

Hans van Zijst

hans@social.woefdram.nl

Well, shows again that you need to make (and maintain) documentation.

Tue, 08 Aug 2023 10:57:14 +0200

Michael Boelen

mboelen@mastodon.social

@hans
You are smart enough to find which one it is 😄