Postfix will not respond to telnet, I've went through debugging, etc

billymayday · 04-18-2009, 09:19 PM

Do you have a line like

Code:

mail.*                                                  -/var/log/maillog

in /etc/syslog.conf?

Have you told your client that authentication is encrypted?

Guardian-Mage · 04-18-2009, 11:07 PM

Sure enough that line was no longer there, must of got removed somewhere along the lines.

Code:

Apr 18 23:06:43 cl-t112-271cl postfix/smtpd[22623]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: No such file or directory
Apr 18 23:06:43 cl-t112-271cl postfix/smtpd[22623]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: No such file or directory

That is the problem, SASL is using the wrong authentication method, so I figure the config file I edited was the wrong one, because that guide has had a few files in different locations than mine. Not sure where the proper one is though.

Any chance /etc/postfix/sasl/smtpd.conf should be /etc/postfix/sasl2/smtpd.conf ?

billymayday · 04-18-2009, 11:25 PM

Show "cat /etc/sysconfig/saslauthd"

billymayday · 04-18-2009, 11:38 PM

Also, what is "MECH" in /etc/init.d/saslauthd?

billymayday · 04-19-2009, 12:04 AM

Are you trying to authenticate against the standard user database? If so, you shouldn't need to change any sasl configs. If this is the case, you should be able to delete /etc/postfix/sasl and its contents

Guardian-Mage · 04-19-2009, 07:57 AM

As the tutorial states, I am trying to authenticate against a mysql database, just like my IMAP server is.

cat /etc/sysconfig/saslauthd

Code:

# Directory in which to place saslauthd's listening socket, pid file, and so
# on.  This directory must already exist.
#SOCKETDIR=/var/run/saslauthd

# Mechanism to use when checking passwords.  Run "saslauthd -v" to get a list
# of which mechanism your installation was compiled with the ablity to use.
#MECH=pam

# Additional flags to pass to saslauthd on the command line.  See saslauthd(8)
# for the list of accepted flags.
#FLAGS=

# This needs to be uncommented before saslauthd will be run automatically
START=yes

# 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"

All the values that are commented out were original, and the uncommented ones are what the tutorial told me to add.

cat /etc/init.d/saslauthd

Code:

[root]~ # cat /etc/init.d/saslauthd
#! /bin/bash
#
# saslauthd      Start/Stop the SASL authentication daemon.
#
# chkconfig: - 95 05
# description: saslauthd is a server process which handles plaintext \
#              authentication requests on behalf of the cyrus-sasl library.
# processname: saslauthd

# Source function library.
. /etc/init.d/functions

# Source our configuration file for these variables.
SOCKETDIR=/var/run/saslauthd
PIDFILE="/var/spool/postfix/var/run/${NAME}/saslauthd.pid"
MECH=shadow
FLAGS=
if [ -f /etc/sysconfig/saslauthd ] ; then
        . /etc/sysconfig/saslauthd
fi

RETVAL=0

# Set up some common variables before we launch into what might be
# considered boilerplate by now.
prog=saslauthd
path=/usr/sbin/saslauthd

# Ugh. Switch to a specific copy of saslauthd if there's one with $MECH
# in its name, in case it wasn't included in the base cyrus-sasl package
# because it would have dragged in too many undesirable dependencies.
if test -x ${path}.${MECH} ; then
        path=/usr/sbin/saslauthd.$MECH
fi

start() {
        echo -n $"Starting $prog: "
        daemon $path -m $SOCKETDIR -a $MECH $FLAGS
        RETVAL=$?
        echo
        [ $RETVAL -eq 0 ] && touch /var/lock/subsys/$prog
        return $RETVAL
}

stop() {
        echo -n $"Stopping $prog: "
        killproc $path
        RETVAL=$?
        echo
        [ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/$prog
        return $RETVAL
}

restart() {
        stop
        start
}

case "$1" in
  start)
        start
        ;;
  stop)
        stop
        ;;
  restart)
        restart
        ;;
  status)
        status $path
        ;;
  condrestart)
        [ -f /var/lock/subsys/$prog ] && restart || :
        ;;
  *)
        echo $"Usage: $0 {start|stop|status|reload|restart|condrestart}"
        exit 1
esac

exit $?

And my smtpd.conf file from /etc/postfix/sasl/

Code:

[root]~ # cat /etc/postfix/sasl/smtpd.conf
pwcheck_method: saslauthd
mech_list: plain login
allow_plaintext: true
auxprop_plugin: mysql
sql_hostnames: 127.0.0.1
sql_user: mail_admin
sql_passwd: test123
sql_database: mail
sql_select: select password from users where email = '%u'

http://www.howtoforge.com/virtual_po...ota_courier_p2

That is the instructions I am following.

Guardian-Mage · 04-19-2009, 11:14 AM

I now know the problem for sure.

Code:

[root]~ # telnet localhost 26
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
220 smtp.sabotix.com ESMTP Postfix
ehlo localhost
250-smtp.sabotix.com
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-STARTTLS
250-AUTH PLAIN LOGIN
250-AUTH=PLAIN LOGIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
auth login
334 VXNlcm5hbWU6
BASE_64 ENCODED USERNAME HERE
334 UGFzc3dvcmQ6
BASE_64 ENCODED PASSWORD HERE
235 2.0.0 Authentication successful

The thing is I entered an actual shell account username and password, which should not of authenticated if MySQL was being used. The problem is getting mysql to work now. Any ideas?

I am using /usr/lib/sasl/smtpd.conf /usr/lib/sasl2/smtpd.conf and /etc/postfix/sasl/smtpd.conf which all looks like this:

Code:

pwcheck_method: saslauthd
mech_list: plain login
allow_plaintext: true
auxprop_plugin: mysql
sql_hostnames: 127.0.0.1
sql_user: mail_admin
sql_passwd: 36upuYacHuCUw57e9Ewazej5
sql_database: mail
sql_select: select password from users where email = '%u'

Shouldn't it use pam or something and if not, maybe auxprop isn't installed. Can I check?

Guardian-Mage · 04-19-2009, 02:06 PM

I've reinstalled postfix and saslauthd to try and fix it, and now when I try to login with telnet, it tells me no auth mech can be found.

Output of saslauthd -v

Code:

[root]/etc/sysconfig # saslauthd -v
saslauthd 2.1.22
authentication mechanisms: getpwent kerberos5 pam rimap shadow ldap

billymayday · 04-19-2009, 03:32 PM

Did you install pam_mysql?

Guardian-Mage · 04-19-2009, 09:15 PM

billymayday · 04-19-2009, 09:20 PM

I'm probably not going to be of much use from here, since I don't use mysql for anything to do with my mail servers.

Can I suggest you start a new thread regarding mysql and saslauth (but note that it's CentOS)