Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 2 > General

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #1  
Old 21st September 2006, 23:45
tom tom is offline
Senior Member
 
Join Date: Apr 2006
Posts: 492
Thanks: 8
Thanked 8 Times in 7 Posts
Default Postfix: smtpd --> SASL LOGIN authentication failed

I don't now why but I can't login and send emails whith my emailaccout from outsite for example whith an emailclient.

I've done this: http://www.howtoforge.com/perfect_setup_debian_sarge

In /var/log/mail.err I found that:
Code:
SASL LOGIN authentication failed
In /var/log/mail.log I found that:
Code:
Sep 21 23:52:03 server01 postfix/smtpd[26732]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
Sep 21 23:52:03 server01 postfix/smtpd[26732]: warning: SASL authentication failure: Password verification failed
Sep 21 23:52:03 server01 postfix/smtpd[26732]: warning: dslb-088-073-067-12.pools.arcor-ip.net[88.73.67.12]: SASL PLAIN authentication failed
Sep 21 23:52:03 server01 postfix/smtpd[26732]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
Sep 21 23:52:03 server01 postfix/smtpd[26732]: warning: dslb-088-073-067-2.pools.arcor-ip.net[88.73.67.12]: SASL LOGIN authentication failed
Sep 21 23:52:05 server01 postfix/smtpd[26732]: lost connection after AUTH from dslb-088-073-067-108.pools.arcor-ip.net[88.73.67.12]
Sep 21 23:52:05 server01 postfix/smtpd[26732]: disconnect from dslb-088-073-067-12.pools.arcor-ip.net[88.73.67.12]
So, I don't know how to fix this authentication problem whith postfix smtpd.

I even only see this output should'nt it show the saslauthd or starts postfix it if nessesary?
Code:
server01:~# ps ax|grep sasl
 2206 pts/1    R+     0:00 grep sasl

Are there some postfix-professionals around the world they now what to do?

Last edited by tom; 22nd September 2006 at 01:58.
Reply With Quote
Sponsored Links
  #2  
Old 22nd September 2006, 09:41
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,976
Thanks: 825
Thanked 5,369 Times in 4,216 Posts
Default

Do you get an error when you start saslauthd with its start script in /etc/init.d ?
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
  #3  
Old 22nd September 2006, 10:15
tom tom is offline
Senior Member
 
Join Date: Apr 2006
Posts: 492
Thanks: 8
Thanked 8 Times in 7 Posts
Default

Quote:
Originally Posted by till
Do you get an error when you start saslauthd with its start script in /etc/init.d ?
No.
That is find in /var/log/authd.log:
Code:
Sep 22 09:39:01 server01 CRON[9849]: (pam_unix) session closed for user root
Sep 22 10:09:01 server01 CRON[10237]: (pam_unix) session opened for user root by (uid=0)
Sep 22 10:09:01 server01 CRON[10237]: (pam_unix) session closed for user root
Sep 22 10:10:12 server01 sshd[10259]: Accepted keyboard-interactive/pam for root from ::ffff:88.73.82.144 port 10565 ssh2
Sep 22 10:10:12 server01 sshd[10264]: (pam_unix) session opened for user root by root(uid=0)
But why I don't see the saslauthd with ps ax after I've started it?
Reply With Quote
  #4  
Old 22nd September 2006, 11:09
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,976
Thanks: 825
Thanked 5,369 Times in 4,216 Posts
Default

The output from the authd.log comes from your ssh and not sasl daemon. Do you get any errors in the syslog when you start saslauthd?
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
  #5  
Old 22nd September 2006, 12:42
tom tom is offline
Senior Member
 
Join Date: Apr 2006
Posts: 492
Thanks: 8
Thanked 8 Times in 7 Posts
Default

Quote:
Originally Posted by till
The output from the authd.log comes from your ssh and not sasl daemon. Do you get any errors in the syslog when you start saslauthd?
Now, nothing in syslog

But you misunderstood my question:
Code:
But why I don't see the saslauthd with ps ax after I've started it?
I mean, should'nt ps ax show the saslauthd in the proceslist after I've started it by running "/etc/init.d/saslauthd"?
Reply With Quote
  #6  
Old 22nd September 2006, 12:44
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 35,976
Thanks: 825
Thanked 5,369 Times in 4,216 Posts
Default

Quote:
Originally Posted by tom
I mean, should'nt ps ax show the saslauthd in the proceslist after I've started it by running "/etc/init.d/saslauthd"?
If saslauthd died directly after yo started it, you wont find it in ps -aux, thats why I asked for the syslog.
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
  #7  
Old 22nd September 2006, 13:40
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,701
Thanks: 1,900
Thanked 2,741 Times in 2,575 Posts
Default

What's in /etc/default/saslauthd? Did you also change /etc/init.d/saslauthd, as shown in the tutorial?
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote
  #8  
Old 22nd September 2006, 14:36
tom tom is offline
Senior Member
 
Join Date: Apr 2006
Posts: 492
Thanks: 8
Thanked 8 Times in 7 Posts
Default

Quote:
Originally Posted by falko
What's in /etc/default/saslauthd? Did you also change /etc/init.d/saslauthd, as shown in the tutorial?
Yeh the solution
Yes, I've change it. But I've done a mistake. Your tutorial says to put

Quote:
START=yes
PARAMS="-m /var/spool/postfix/var/run/saslauthd -r"
MECHANISMS="pam"
in /etc/init.d/saslauthd

but I've put this ":" bloddy colon on the end of the row...
Quote:
PARAMS="-m /var/spool/postfix/var/run/saslauthd -r":
Thank a lot for your help. I was searching hours and hours but I could*nt find anything.
Thanks falko.
Reply With Quote
  #9  
Old 30th June 2008, 02:06
DantePasquale DantePasquale is offline
Senior Member
 
Join Date: Feb 2007
Location: Lakewood, OH US
Posts: 108
Thanks: 10
Thanked 3 Times in 3 Posts
Send a message via AIM to DantePasquale
Default

Hi Til,

Sorry for bugging you guys with dumb questions, but I followed your upgrade tutorial for upgrading Ubuntu to 8.04. Everything works fine, except for the problem identified in this thread. I'm sure it's a typo, but I'm not seeing it. I copied the /etc/default/saslauthd from your tutorial, was I supposed to append that to the one created during the upgrade - or overwrite the one created during upgrade?

Here's my file:

Code:
#
# Settings for saslauthd daemon
# Please read /usr/share/doc/sasl2-bin/README.Debian for details.
#

# Should saslauthd run automatically on startup? (default: no)
START=yes

# Description of this saslauthd instance. Recommended.
# (suggestion: SASL Authentication Daemon)
DESC="SASL Authentication Daemon"

# Short name of this saslauthd instance. Strongly recommended.
# (suggestion: saslauthd)
NAME="saslauthd"

# Which authentication mechanisms should saslauthd use? (default: pam)
#
# Available options in this Debian package:
# getpwent  -- use the getpwent() library function
# kerberos5 -- use Kerberos 5
# pam       -- use PAM
# rimap     -- use a remote IMAP server
# shadow    -- use the local shadow password file
# sasldb    -- use the local sasldb database file
# ldap      -- use LDAP (configuration is in /etc/saslauthd.conf)
#
# Only one option may be used at a time. See the saslauthd man page
# for more information.
#
# Example: MECHANISMS="pam"
MECHANISMS="pam"

# Additional options for this mechanism. (default: none)
# See the saslauthd man page for information about mech-specific options.
MECH_OPTIONS=""

# How many saslauthd processes should we run? (default: 5)
# A value of 0 will fork a new process for each connection.
THREADS=5

# Other options (default: -c -m /var/run/saslauthd)
# Note: You MUST specify the -m option or saslauthd won't run!
#
# See /usr/share/doc/sasl2-bin/README.Debian for Debian-specific information.
# See the saslauthd man page for general information about these options.
#
# Example for postfix users: "-c -m /var/spool/postfix/var/run/saslauthd"
#OPTIONS="-c -m /var/run/saslauthd"
OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd -r"
Reply With Quote
  #10  
Old 30th June 2008, 04:37
DantePasquale DantePasquale is offline
Senior Member
 
Join Date: Feb 2007
Location: Lakewood, OH US
Posts: 108
Thanks: 10
Thanked 3 Times in 3 Posts
Send a message via AIM to DantePasquale
 
Default

Not sure what the heck is going on, but I have 2 mux files. Wonder if that's the problem????

Code:
root@inferno:/etc/default# ls -l /var/spool/postfix/var/run/saslauthd /var/run/saslauthd/
/var/run/saslauthd/:
total 4
srwxrwxrwx 1 root root 0 2008-06-29 22:23 mux
-rw------- 1 root root 0 2008-06-29 22:23 mux.accept
-rw------- 1 root root 6 2008-06-29 22:23 saslauthd.pid

/var/spool/postfix/var/run/saslauthd:
total 4
srwxrwxrwx 1 root root 0 2008-06-29 19:54 mux
-rw------- 1 root root 0 2008-06-29 19:54 mux.accept
-rw------- 1 root root 6 2008-06-29 19:54 saslauthd.pid
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Freebsd 6.1 support misterm Installation/Configuration 10 9th April 2009 09:29
smtpd, SASL authentication failure: Steve_P Installation/Configuration 4 6th February 2009 16:26
Systemimager (rsync) doesn't copy all comedit HOWTO-Related Questions 11 19th January 2007 17:17
How to install BFD (Brute Force Detection) domino Tips/Tricks/Mods 9 31st March 2006 22:40
Total Frustration-HELP palkat Installation/Configuration 17 3rd September 2005 17:28


All times are GMT +2. The time now is 20:20.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.