PDA

View Full Version : postfix auth problem (sasl)


lerra
6th March 2006, 09:29
Hi! I cant use my postfix to send mail, i get this when i try to send it in the logs:

Mar 6 08:44:01 caveguard postfix/smtpd[4915]: setting up TLS connection from xxxx[xxx]
Mar 6 08:44:01 caveguard postfix/smtpd[4915]: TLS connection established from xxxx[xxx]: TLSv1 with ciith cipher RC4-MD5 (128/128 bits)
Mar 6 08:44:01 caveguard postfix/smtpd[4915]: connect from xxxx[xxx]
Mar 6 08:44:01 caveguard postfix/smtpd[4915]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
Mar 6 08:44:01 caveguard postfix/smtpd[4915]: warning: xxxx[xxx]: SASL LOGIN authentication failed
Mar 6 08:44:01 caveguard postfix/smtpd[4915]: warning: Read failed in network_biopair_interop with errno=0: num_read=0, want_read=5
Mar 6 08:44:01 caveguard postfix/smtpd[4915]: lost connection after AUTH from xxxx[xxx]
Mar 6 08:44:01 caveguard postfix/smtpd[4915]: disconnect from xxxx[xxx]
Mar 6 08:44:06 caveguard postfix/smtpd[4915]: setting up TLS connection from xxxx[xxx]


Anybody that knows what to do? What coud be the problem? I see that the TLS phase works, but when it try to identify the user it cant find db

Here is some other configs:
caveguard:~# cat /etc/default/saslauthd
# This needs to be uncommented before saslauthd will be run automatically
START=yes

PARAMS="-m /var/spool/postfix/var/run/saslauthd"

# You must specify the authentication mechanisms you wish to use.
# This defaults to "pam" for PAM support, but may also include
# "shadow" or "sasldb", like this:
# MECHANISMS="pam shadow"

MECHANISMS="pam"
#PARAMS="-m /var/spool/postfix/var/run/saslauthd -r"

and fro my main.cnf:
smtpd_sasl_local_domain =
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
broken_sasl_auth_clients = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject _unauth_destination

And
caveguard:~# cat /etc/postfix/sasl/smtpd.conf
pwcheck_method: saslauthd
mech_list: plain login
allow_plaintext: true

Any tip?

falko
6th March 2006, 11:14
saslauthd isn't running. Start it: /etc/init.d/saslauthd start

lerra
6th March 2006, 11:39
<quote>
caveguard:~# /etc/init.d/saslauthd start
Starting SASL Authentication Daemon: /usr/sbin/saslauthd already running.
</quote>

falko
6th March 2006, 11:53
Then try /etc/init.d/saslauthd restart

lerra
6th March 2006, 13:47
Still the same error:)

falko
6th March 2006, 19:11
Which distribution do you use?

lerra
6th March 2006, 20:27
Debian sarge 3.1 amd64. Followd your howto in perfect setup for debian 3.1

falko
6th March 2006, 22:21
Please redo the saslauthd configuration from http://www.howtoforge.com/perfect_setup_debian_sarge_p4 . Maybe you made a typo somewhere.

lerra
6th March 2006, 23:02
Still the same error:(

falko
6th March 2006, 23:15
Please post the output of ps aux|grep sasl

lerra
7th March 2006, 01:08
caveguard:~# ps aux|grep sasl
root 25783 0.0 0.1 31788 1268 ? Ss Mar06 0:00 /usr/sbin/saslauthd -m /var/spool/postfix/var/run/saslauthd -a pam
root 25784 0.0 0.0 31788 844 ? S Mar06 0:00 /usr/sbin/saslauthd -m /var/spool/postfix/var/run/saslauthd -a pam
root 25785 0.0 0.0 31788 780 ? S Mar06 0:00 /usr/sbin/saslauthd -m /var/spool/postfix/var/run/saslauthd -a pam
root 25786 0.0 0.0 31788 780 ? S Mar06 0:00 /usr/sbin/saslauthd -m /var/spool/postfix/var/run/saslauthd -a pam
root 25787 0.0 0.0 31788 780 ? S Mar06 0:00 /usr/sbin/saslauthd -m /var/spool/postfix/var/run/saslauthd -a pam
root 5932 0.0 0.0 2696 508 pts/0 S+ 01:07 0:00 grep sasl
caveguard:~#

lerra
7th March 2006, 09:54
coud u find anything? A nother problem that i have too is the webmail that is a package for ispconfig, gives me

Warning: Header may not contain more than a single header, new line detected. in /home/admispconfig/ispconfig/web/webmail/inc/inc.php on line 136

here and there...and on logout it gives

Warning: Header may not contain more than a single header, new line detected. in /home/admispconfig/ispconfig/web/webmail/inc/inc.php on line 136

Warning: Cannot modify header information - headers already sent by (output started at /home/admispconfig/ispconfig/web/webmail/inc/inc.php:136) in /home/admispconfig/ispconfig/web/webmail/logout.php on line 73

falko
7th March 2006, 13:23
coud u find anything?
Looks ok. What's the exact error message from your mail log?

A nother problem that i have too is the webmail that is a package for ispconfig, gives me

Warning: Header may not contain more than a single header, new line detected. in /home/admispconfig/ispconfig/web/webmail/inc/inc.php on line 136

here and there...and on logout it gives

Warning: Header may not contain more than a single header, new line detected. in /home/admispconfig/ispconfig/web/webmail/inc/inc.php on line 136

Warning: Cannot modify header information - headers already sent by (output started at /home/admispconfig/ispconfig/web/webmail/inc/inc.php:136) in /home/admispconfig/ispconfig/web/webmail/logout.php on line 73
Take a look at this thread: http://www.howtoforge.com/forums/showthread.php?t=2842

todvard
7th March 2006, 13:24
what are the outputs of:

dpkg -l | grep sasl
ls -la /var/spool/postfix/var/run/saslauthd

lerra
7th March 2006, 14:52
Todvard:

caveguard:~# dpkg -l | grep sasl
ii libsasl2 2.1.19-1.5 Authentication abstraction library
ii libsasl2-modul 2.1.19-1.5 Pluggable Authentication Modules for SASL
ii sasl2-bin 2.1.19-1.5 Programs for manipulating the SASL users dat
caveguard:~# ls -la /var/spool/postfix/var/run/saslauthd
total 12
drwxr-xr-x 2 root sasl 4096 Mar 6 22:58 .
drwxr-xr-x 3 root root 4096 Jan 22 13:41 ..
srwxrwxrwx 1 root root 0 Mar 6 22:58 mux
-rw------- 1 root root 0 Mar 6 22:58 mux.accept
-rw------- 1 root root 6 Mar 6 22:58 saslauthd.pid
caveguard:~#




falko:

Mar 6 08:44:01 caveguard postfix/smtpd[4915]: setting up TLS connection from xxxx[xxx]
Mar 6 08:44:01 caveguard postfix/smtpd[4915]: TLS connection established from xxxx[xxx]: TLSv1 with ciith cipher RC4-MD5 (128/128 bits)
Mar 6 08:44:01 caveguard postfix/smtpd[4915]: connect from xxxx[xxx]
Mar 6 08:44:01 caveguard postfix/smtpd[4915]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
Mar 6 08:44:01 caveguard postfix/smtpd[4915]: warning: xxxx[xxx]: SASL LOGIN authentication failed
Mar 6 08:44:01 caveguard postfix/smtpd[4915]: warning: Read failed in network_biopair_interop with errno=0: num_read=0, want_read=5
Mar 6 08:44:01 caveguard postfix/smtpd[4915]: lost connection after AUTH from xxxx[xxx]
Mar 6 08:44:01 caveguard postfix/smtpd[4915]: disconnect from xxxx[xxx]
Mar 6 08:44:06 caveguard postfix/smtpd[4915]: setting up TLS connection from xxxx[xxx]

todvard
7th March 2006, 20:47
what is the content of /etc/postfix/master.cf file?
cat /etc/postfix/master.cf

lerra
7th March 2006, 22:48
# See /usr/share/postfix/main.cf.dist for a commented, more complete version

smtpd_banner = $myhostname ESMTP $mail_name
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

myhostname = mail.infonavia.se
#myhostname = infonavia.se
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination = mail.infonavia.se, localhost.localdomain, localhost.localdomain, localhost
relayhost =
mynetworks = 127.0.0.0/8
mailbox_command =
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all

smtpd_sasl_local_domain =
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
broken_sasl_auth_clients = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject _unauth_destination

smtpd_tls_auth_only = no
smtp_use_tls = yes
smtpd_use_tls = yes
smtp_tls_note_starttls_offer = yes
smtpd_tls_key_file = /etc/postfix/ssl/smtpd.key
smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.crt
smtpd_tls_CAfile = /etc/postfix/ssl/cacert.pem
smtpd_tls_loglevel = 1
smtpd_tls_received_header = yes
smtpd_tls_session_cache_timeout = 3600s
tls_random_source = dev:/dev/urandom

virtual_maps = hash:/etc/postfix/virtusertable

mydestination = /etc/postfix/local-host-names
home_mailbox = Maildir/

falko
7th March 2006, 23:03
todvard asked for master.cf, not main.cf... ;)

lerra
8th March 2006, 10:48
Haha, sorry, was tierd yesterday;)

Here it goes:

# ================================================== ========================
# service type private unpriv chroot wakeup maxproc command + args
# (yes) (yes) (yes) (never) (100)
# ================================================== ========================
smtp inet n - - - - smtpd
#submission inet n - - - - smtpd
# -o smtpd_etrn_restrictions=reject
#628 inet n - - - - qmqpd
pickup fifo n - - 60 1 pickup
cleanup unix n - - - 0 cleanup
qmgr fifo n - - 300 1 qmgr
#qmgr fifo n - - 300 1 oqmgr
rewrite unix - - - - - trivial-rewrite
bounce unix - - - - 0 bounce
defer unix - - - - 0 bounce
trace unix - - - - 0 bounce
verify unix - - - - 1 verify
flush unix n - - 1000? 0 flush
proxymap unix - - n - - proxymap
smtp unix - - - - - smtp
relay unix - - - - - smtp
# -o smtp_helo_timeout=5 -o smtp_connect_timeout=5
showq unix n - - - - showq
error unix - - - - - error
local unix - n n - - local
virtual unix - n n - - virtual
lmtp unix - - n - - lmtp
anvil unix - - n - 1 anvil
#
# Interfaces to non-Postfix software. Be sure to examine the manual
# pages of the non-Postfix software to find out what options it wants.
#
# maildrop. See the Postfix MAILDROP_README file for details.
#
maildrop unix - n n - - pipe
flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient}
uucp unix - n n - - pipe
flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
ifmail unix - n n - - pipe
flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
bsmtp unix - n n - - pipe
flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -d -t$nexthop -f$sender $recipient
scalemail-backend unix - n n - 2 pipe
flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension}

# only used by postfix-tls
tlsmgr fifo - - n 300 1 tlsmgr
smtps inet n - n - - smtpd -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes
587 inet n - n - - smtpd -o smtpd_enforce_tls=yes -o smtpd_sasl_auth_enable=yes

todvard
8th March 2006, 11:20
seems ok to me. last questions from me :)
ls -la /var/spool/postfix/etc/
ls -Rla /var/spool/postfix/usr/

lerra
8th March 2006, 12:35
caveguard:~# ls -la /var/spool/postfix/etc/
total 44
drwxr-xr-x 2 root root 4096 Mar 7 23:59 .
drwxr-xr-x 20 root root 4096 Jan 22 13:43 ..
-rw-r--r-- 1 root root 422 Mar 7 23:59 hosts
-rw-r--r-- 1 root root 675 Mar 7 23:59 localtime
-rw-r--r-- 1 root root 465 Mar 7 23:59 nsswitch.conf
-rw-r--r-- 1 root root 107 Mar 7 23:59 resolv.conf
-rw-r--r-- 1 root root 17571 Mar 7 23:59 services
caveguard:~# ls -Rla /var/spool/postfix/usr/
/var/spool/postfix/usr/:
total 12
drwxr-xr-x 3 root root 4096 Jan 22 13:37 .
drwxr-xr-x 20 root root 4096 Jan 22 13:43 ..
drwxr-xr-x 3 root root 4096 Jan 22 13:37 lib

/var/spool/postfix/usr/lib:
total 12
drwxr-xr-x 3 root root 4096 Jan 22 13:37 .
drwxr-xr-x 3 root root 4096 Jan 22 13:37 ..
drwxr-xr-x 2 root root 4096 Mar 7 23:59 zoneinfo

/var/spool/postfix/usr/lib/zoneinfo:
total 8
drwxr-xr-x 2 root root 4096 Mar 7 23:59 .
drwxr-xr-x 3 root root 4096 Jan 22 13:37 ..
lrwxrwxrwx 1 root root 14 Mar 7 23:59 localtime -> /etc/localtime

todvard
8th March 2006, 13:27
hmm, weird.
dpkg -l | grep postfix
ls -Rla /var/spool/postfix/lib

lerra
8th March 2006, 16:20
caveguard:~# dpkg -l | grep postfix
ii postfix 2.1.5-9 A high-performance mail transport agent
ii postfix-tls 2.1.5-9 TLS and SASL support for Postfix
caveguard:~# ls -Rla /var/spool/postfix/lib
/var/spool/postfix/lib:
total 232
drwxr-xr-x 2 root root 4096 Mar 7 23:59 .
drwxr-xr-x 20 root root 4096 Jan 22 13:43 ..
-rw-r--r-- 1 root root 31744 May 12 2005 libnss_compat-2.3.2.so
lrwxrwxrwx 1 root root 22 Mar 7 23:59 libnss_compat.so.2 -> libnss_compat-2.3.2.so
-rw-r--r-- 1 root root 21536 May 23 2005 libnss_db-2.2.so
lrwxrwxrwx 1 root root 16 Mar 7 23:59 libnss_db.so.2 -> libnss_db-2.2.so
-rw-r--r-- 1 root root 16216 May 12 2005 libnss_dns-2.3.2.so
lrwxrwxrwx 1 root root 19 Mar 7 23:59 libnss_dns.so.2 -> libnss_dns-2.3.2.so
-rw-r--r-- 1 root root 41600 May 12 2005 libnss_files-2.3.2.so
lrwxrwxrwx 1 root root 21 Mar 7 23:59 libnss_files.so.2 -> libnss_files-2.3.2.so
-rw-r--r-- 1 root root 17768 May 12 2005 libnss_hesiod-2.3.2.so
lrwxrwxrwx 1 root root 22 Mar 7 23:59 libnss_hesiod.so.2 -> libnss_hesiod-2.3.2.so
-rw-r--r-- 1 root root 39488 May 12 2005 libnss_nis-2.3.2.so
lrwxrwxrwx 1 root root 19 Mar 7 23:59 libnss_nis.so.2 -> libnss_nis-2.3.2.so
-rw-r--r-- 1 root root 45344 May 12 2005 libnss_nisplus-2.3.2.so
lrwxrwxrwx 1 root root 23 Mar 7 23:59 libnss_nisplus.so.2 -> libnss_nisplus-2.3.2.so
caveguard:~#


What do you have in your thoughts?

todvard
8th March 2006, 17:11
My first thoghts was that you are using postfix not in chroot and you are trying to access saslauthd in wrong folder, but everything seems fine in your config files and folders so far.
I could find some hints searching by google, this one is promising http://bsdsearch.com/eao/phorum/read.php?f=38&i=2810&t=2810&v=f
Lets see other config files
cat /etc/init.d/saslauthd

/* about your main.cf, i guess you forgot to install procmail, or just forgot to configure postfix to using it.
mailbox_command = procmail -a "$EXTENSION"
just ignore me if you are planning to not use procmail :) */

lerra
9th March 2006, 00:08
What feutures will procmail do? Or what does it add?


here is the file


#!/bin/sh -e

NAME=saslauthd
DAEMON="/usr/sbin/${NAME}"
DESC="SASL Authentication Daemon"
DEFAULTS=/etc/default/saslauthd
PWDIR="/var/spool/postfix/var/run/${NAME}"
PIDFILE="${PWDIR}/saslauthd.pid"
dir="root sasl 755 ${PWDIR}"

createdir() {
# $1 = user
# $2 = group
# $3 = permissions (octal)
# $4 = path to directory
[ -d "$4" ] || mkdir -p "$4"
chown -c -h "$1:$2" "$4"
chmod -c "$3" "$4"
}

test -f "${DAEMON}" || exit 0

# Source defaults file; edit that file to configure this script.
caveguard:~# clear
caveguard:~# cat /etc/init.d/saslauthd
#!/bin/sh -e

NAME=saslauthd
DAEMON="/usr/sbin/${NAME}"
DESC="SASL Authentication Daemon"
DEFAULTS=/etc/default/saslauthd
PWDIR="/var/spool/postfix/var/run/${NAME}"
PIDFILE="${PWDIR}/saslauthd.pid"
dir="root sasl 755 ${PWDIR}"

createdir() {
# $1 = user
# $2 = group
# $3 = permissions (octal)
# $4 = path to directory
[ -d "$4" ] || mkdir -p "$4"
chown -c -h "$1:$2" "$4"
chmod -c "$3" "$4"
}

test -f "${DAEMON}" || exit 0

# Source defaults file; edit that file to configure this script.
if [ -e "${DEFAULTS}" ]; then
. "${DEFAULTS}"
fi

# If we're not to start the daemon, simply exit
if [ "${START}" != "yes" ]; then
exit 0
fi

# If we have no mechanisms defined
if [ "x${MECHANISMS}" = "x" ]; then
echo "You need to configure ${DEFAULTS} with mechanisms to be used"
exit 0
fi

# Add our mechanimsms with the necessary flag
PARAMS="${PARAMS} -a ${MECHANISMS}"

START="--start --quiet --pidfile ${PIDFILE} --startas ${DAEMON} --name ${NAME} -- ${PARAMS}"

# Consider our options
case "${1}" in
start)
echo -n "Starting ${DESC}: "
#comment out
#dir=`dpkg-statoverride --list $PWDIR`
test -z "$dir" || createdir $dir
if start-stop-daemon ${START} >/dev/null 2>&1 ; then
echo "${NAME}."
else
if start-stop-daemon --test ${START} >/dev/null 2>&1; then
echo "(failed)."
exit 1
else
echo "${DAEMON} already running."
exit 0
fi
fi
;;
stop)
echo -n "Stopping ${DESC}: "
if start-stop-daemon --stop --quiet --pidfile "${PIDFILE}" \
--startas ${DAEMON} --retry 10 --name ${NAME} \
>/dev/null 2>&1 ; then
echo "${NAME}."
else
if start-stop-daemon --test ${START} >/dev/null 2>&1; then
echo "(not running)."
exit 0
else
echo "(failed)."
exit 1
fi
fi
;;
restart|force-reload)
$0 stop
exec $0 start
;;
*)
echo "Usage: /etc/init.d/${NAME} {start|stop|restart|force-reload}" >&2
exit 1
;;
esac

exit 0

falko
9th March 2006, 10:17
Looks ok, too... :confused:

todvard
9th March 2006, 11:07
What feutures will procmail do? Or what does it add?

Procmail is needed for selecting and forwarding messages to different services like the spamfilter, virusscanner, mail forward, quota, autoresponder and such..
I hope Falko or Till will correct me if i am wrong.. :)

about sasl, i can not see errors im your config files. it could be smthing very annoying typo somewhere.. or maybe not.. :confused: If i were you i would reinstall all packages related to this issue:
apt-get --reinstall install postfix postfix-tls libsasl2 libsasl2-modules sasl2-bin

lerra
10th March 2006, 19:10
Hm, i already use thows feutures and they seams to work..
Hm, ok, i will do that and come back...will follow perfect setup 3.1 debian again and report back.

lerra
13th April 2006, 21:29
Is there nobody that can help me with the sasl problem? Still haveing the problem.. :/

falko
13th April 2006, 22:36
You must have something wrong. If you simply copy & paste the commands from the "Perfect Setup", it will work.

r12dk
13th April 2006, 22:45
Falko, i think something has changed in the debian packages since you wrote the howto. Lot of people seem to have problems with saslauth and smtp auth'ing, including me.

I also followed the perfect setup, step by step, and it simply wornt work.

falko
13th April 2006, 23:05
Believe me, it's working. I've just set up another server with this tutorial two days ago. If you just follow it and don't look left and right, then it's working. Don't do anything else, just do what is said in the tutorial.

lerra
19th April 2006, 22:07
Solved! After some hours of googleing and testing i found a page:
http://lists.debian.org/debian-user/2005/07/msg01010.html

What i did was that i added postfix to the sals group,
rm -rf /var/run/saslauthd
ln -s /var/spool/postfix/var/run/saslauthd/ /var/run/saslauthd

And it works now! I am runnign Sarge 3.1 amd64
I hope this will help people, please support the ispconfig community by postback sollutions! Creds to the codehackers!

Hans
28th April 2006, 22:56
Have a look here too:

http://www.howtoforge.com/forums/showthread.php?t=3917&highlight=saslauthd

Hans :)

minskog
10th May 2006, 14:07
Solved! After some hours of googleing and testing i found a page:
http://lists.debian.org/debian-user/2005/07/msg01010.html

What i did was that i added postfix to the sals group,
rm -rf /var/run/saslauthd
ln -s /var/spool/postfix/var/run/saslauthd/ /var/run/saslauthd

And it works now! I am runnign Sarge 3.1 amd64
I hope this will help people, please support the ispconfig community by postback sollutions! Creds to the codehackers!

I have the same problem,and dont work with that commands. I do a vimdiff from my files to howto's configuration files and are the same except the domain, of course.

update:
Im restart all services and now (thanks to $deity) gives an error:
warning: SASL authentication failure: cannot connect to saslauthd server: Permission denied

And with testsaslauthd runs well, before the restart dont work:
testsaslauthd -f /var/spool/postfix/var/run/saslauthd/mux -u minskog.net_minskog -p password
0: OK "Success."

Update 2:
lerra have: PWDIR="/var/spool/postfix/var/run/${NAME}"
I have: PWDIR=/var/run/saslauthd


But ig i put PWDIR="/var/spool/postfix/var/run/${NAME}", then sasl dont start.

falko
10th May 2006, 14:51
Please kill your existing saslauthd processes and try to start saslauthd again.

minskog
10th May 2006, 15:04
I restart it a lot, but i think that the problem could be here:

Starting SASL Authentication Daemon: mode of `/var/run/saslauthd' changed to 0710 (rwx--x---)

Update:

If i put /var/spool/postfix/var/run/saslauthd with 777, dont gives permission error, but continues giving errors, the password is correct and the user, I use them with imap, pop and testsasauthd, and works perfectly:

warning: SASL authentication failure: Password verification failed

falko
10th May 2006, 15:53
Did you kill your existing saslauthd processes and start saslauthd again?

minskog
10th May 2006, 16:13
Did you kill your existing saslauthd processes and start saslauthd again? Yes, and the same: server1:/var/spool/postfix/var/run/saslauthd# killall saslauthd
server1:/var/spool/postfix/var/run/saslauthd# killall saslauthd saslauthd: no process killed
server1:/var/spool/postfix/var/run/saslauthd# /etc/init.d/saslauthd start
Starting SASL Authentication Daemon: mode of `/var/run/saslauthd' changed to 0710 (rwx--x---) saslauthd. then i try to send one mail: May 10 16:12:27 server1 postfix/smtpd[25016]: warning: SASL authentication failure: cannot connect to saslauthd server: Permission denied May 10 16:12:27 server1 postfix/smtpd[25016]: warning: SASL authentication failure: Password verification failed Update: I am trying in another server, and the same. Are both debian sarge 3.1 32bits, ispconfig version 2.2.2. Updaet 2: I reconfigure postfix and sasl by copy&paste from the howto and the same.

Update 3:
im crazy, i have 3 servers with ispconfig, server 1 and server 2 fails, but server 3 runs well, and i dont see any significative differences in configuration ...

minskog
10th May 2006, 18:40
Server 2 work now with a complete reinstall, but server 1 continues giving sasl errors.

May 10 18:36:17 server1 postfix/smtpd[30797]: warning: SASL authentication failure: Password verification failed
May 10 18:36:17 server1 postfix/smtpd[30797]: warning: x.Red-x-x-x.staticIP.rima-tde.net[x.x.x.x]: SASL PLAIN authentication failed
May 10 18:36:17 server1 postfix/smtpd[30797]: warning: x.Red-x-x-x.staticIP.rima-tde.net[x.x.x.x]: SASL LOGIN authentication

Postfix telnet:
ehlo minskog
250-server1.domain.com
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-STARTTLS
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250 8BITMIME


Says that sasl are active, and the test:

testsaslauthd -f /var/spool/postfix/var/run/saslauthd/mux -u minskog.net_minskog -p password
0: OK "Success."

minskog
10th May 2006, 23:36
The file /etc/pam.d/smtp was corrupted, the last line was a lot of strange characters, i copy the file from server3 and works! I send a mail to isp for check the machine, could be a failing hard disk ....:eek: