| If you can, please let us know the saslauthd run time flags you’re using. I vaguely remember having to update the saslauthd systemd file on my system to use the -r flag and mech=pam. Pretty sure cyrus will be passing the domain and it’ll be splitting the parts to use; just suspect saslauthd daemon hasn't been told to use the domain part. On my system saslauthd runtime looks like this: /usr/sbin/saslauthd -m /run/saslauthd -a pam -r Where saslauthd systemd file has: MECH=pam FLAGS=-r Bu default i dont think saslauthd in default install has -r flag. When you use the cli tesy tool pretty sure when you specify -r it prob works because daemon knows what you are wanting. Use the cyrus cli tool and i think it hots the daemon and daemon doesnt know to expect it. Thats my theory, worth a shot :) Pretty sure i had the same issue and adding the flag and restarting saslauthd fixed it. Thats a few years ago now but has all the signs of the issue i had. If it works massive if not, only a few seconds lost :) -Andy
Sent from my iPhone On 24/07/2023, at 5:45 PM, Richard <rheggs@xxxxxxxxx> wrote:
|
