I'm pretty sure this actually no longer classifies as a bug, and is
really an issue in documentation of upgrades / lack of reverse support.
I don't have an old copy of my smtpd.conf file from when I upgraded and
it first broke, but my new smtpd.com shows:
auxprop_plugin: sql
sql_engine: mysql
Are you using ldap instead of sql for your mail authentications? If
you're getting the same problem that I initially described here, between
saslauthd and mysql via cyrus-sasl, then I'd say it's almost definitely
a configuration problem, as I spent a couple months pulling my hair out
and
Close but not quite.
Originally BEFORE I made the config changes, I had to downgrade sasl
specifically and relink a couple libraries and I was able to get it
working (but every time I would upgrade apt packages, it would manage to
break again, after telling it not put those packages on hold).
You're seeing:
postfix/smtpd[4930]: sql auxprop plugin using mysql engine
with login attempts and /var/log/mail.log shows:
SASL LOGIN authentication failed: no mechanism available
Every time.
?? Were there any changes to the log output when you made the changes?
Dumb question but
I'm pretty sure this actually no longer classifies as a bug, and is
really an issue in documentation of upgrades / lack of reverse support.
I don't have an old copy of my smtpd.conf file from when I upgraded and
it first broke, but my new smtpd.com shows:
auxprop_plugin: sql
sql_engine: mysql
Are you using ldap instead of sql for your mail authentications? If
you're getting the same problem that I initially described here, between
saslauthd and mysql via cyrus-sasl, then I'd say it's almost definitely
a configuration problem, as I spent a couple months pulling my hair out
and
Close but not quite.
Originally BEFORE I made the config changes, I had to downgrade sasl
specifically and relink a couple libraries and I was able to get it
working (but every time I would upgrade apt packages, it would manage to
break again, after telling it not put those packages on hold).
You're seeing:
postfix/smtpd[4930]: sql auxprop plugin using mysql engine
with login attempts and /var/log/mail.log shows:
SASL LOGIN authentication failed: no mechanism available
Every time.
?? Were there any changes to the log output when you made the changes?
Dumb question but
I totally agree with you, this is kind of ridiculous. Waiting til the
next version?? I can't wait until April for it to be taken care of. As
a long, long time user of Debian, and a strong advocate for the use of
Ubuntu to anyone with technical savvy enough to handle Linux, I'm pretty
I totally agree with you, this is kind of ridiculous. Waiting til the
next version?? I can't wait until April for it to be taken care of. As
a long, long time user of Debian, and a strong advocate for the use of
Ubuntu to anyone with technical savvy enough to handle Linux, I'm pretty
This was definitely not the problem for me.
I used aptitude and put the sasl packages on hold, but it somehow keeps
breaking through other, what I thought were unrelated packages and I
have 'make install' on the compiled source, re dpkg -i the .23 debs, and
then make uninstall the compiled
This was definitely not the problem for me.
I used aptitude and put the sasl packages on hold, but it somehow keeps
breaking through other, what I thought were unrelated packages and I
have 'make install' on the compiled source, re dpkg -i the .23 debs, and
then make uninstall the compiled
potatochip: you first installed the 2.1.23 (which is the version that
WORKS) and then you overwrote some of the files and links by compiling
and installing 2.1.25 (the output of your saslauthd shows 2.1.25 is
what's installed).
Go back into your 2.1.25 source, make uninstall, then run dpkg -i
On 10/22/2011 1:19 PM, Dan Moore wrote:
Otlay's workaround worked for me. But I had to go through some pushups
to get it installed without error. I had a dependency conflict with some
:i386 packages.
Note: I think any other updates are on hold until this gets resolved.
e.g.:
sudo
potatochip: you first installed the 2.1.23 (which is the version that
WORKS) and then you overwrote some of the files and links by compiling
and installing 2.1.25 (the output of your saslauthd shows 2.1.25 is
what's installed).
Go back into your 2.1.25 source, make uninstall, then run dpkg -i
On 10/22/2011 1:19 PM, Dan Moore wrote:
Otlay's workaround worked for me. But I had to go through some pushups
to get it installed without error. I had a dependency conflict with some
:i386 packages.
Note: I think any other updates are on hold until this gets resolved.
e.g.:
sudo
Check out my post at the bottom of:
http://ubuntuforums.org/showthread.php?t=1859667page=2
Basically I downgraded libsasl2-2, libsasl2-dev, libsasl2-modules,
libsasl2-modules-sql and sasl2-bin
Archives I used: wget http://archive.ubuntu.com/ubuntu/poo...ntu3_amd64.deb
Manually upgrading my sasl libs (cyrus-sasl) from 2.1.24rc1 (ubuntu
package) to the latest 2.1.25 FIXED my SASL issues. I had to configure
--with-ldap --enable-sql (without ldap had version linking problems)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Eric, pls make sure when you do saslauthd -v it shows 2.1.25 and that
postfix and saslauthd have been restarted. After that, do the log files
show the same thing, and are there any errors popping up when you
restart postfix/saslauthd?
--
You received this bug notification because you are a
SASL PLAIN authentication failed: no mechanism available
SASL LOGIN authentication failed: no mechanism available
I've been working on this for a few hours and not able to get saslauthd
to lookup logins either. upgraded and ensured that libsasl2-2 etc is
all installed, has been working fine for
20 matches
Mail list logo
