The Perfect Setup - Debian Etch (Debian 4.0) some trouble

mail log continue

Jan 25 14:04:04 server postfix/smtpd[29760]: warning: SASL per-process initializ ation failed: generic failure
Jan 25 14:04:04 server postfix/smtpd[29760]: fatal: SASL per-process initializat ion failed
Jan 25 14:04:05 server postfix/master[9108]: warning: process /usr/lib/postfix/s mtpd pid 29760 exit status 1
Jan 25 14:04:05 server postfix/master[9108]: warning: /usr/lib/postfix/smtpd: ba d command startup -- throttling
Jan 25 14:05:05 server postfix/smtpd[29880]: warning: SASL per-process initializ ation failed: generic failure
Jan 25 14:05:05 server postfix/smtpd[29880]: fatal: SASL per-process initializat ion failed
Jan 25 14:05:06 server postfix/master[9108]: warning: process /usr/lib/postfix/s mtpd pid 29880 exit status 1
Jan 25 14:05:06 server postfix/master[9108]: warning: /usr/lib/postfix/smtpd: ba d command startup -- throttling
Jan 25 14:06:06 server postfix/smtpd[29999]: warning: SASL per-process initializ ation failed: generic failure
Jan 25 14:06:06 server postfix/smtpd[29999]: fatal: SASL per-process initializat ion failed
Jan 25 14:06:07 server postfix/master[9108]: warning: process /usr/lib/postfix/s mtpd pid 29999 exit status 1
Jan 25 14:06:07 server postfix/master[9108]: warning: /usr/lib/postfix/smtpd: ba d command startup -- throttling
Jan 25 14:07:07 server postfix/smtpd[30118]: warning: SASL per-process initializ ation failed: generic failure
Jan 25 14:07:07 server postfix/smtpd[30118]: fatal: SASL per-process initializat ion failed
Jan 25 14:07:08 server postfix/master[9108]: warning: process /usr/lib/postfix/s mtpd pid 30118 exit status 1
Jan 25 14:07:08 server postfix/master[9108]: warning: /usr/lib/postfix/smtpd: ba d command startup -- throttling
Jan 25 14:08:08 server postfix/smtpd[30238]: warning: SASL per-process initializ ation failed: generic failure
Jan 25 14:08:08 server postfix/smtpd[30238]: fatal: SASL per-process initializat ion failed
Jan 25 14:08:09 server postfix/master[9108]: warning: process /usr/lib/postfix/s mtpd pid 30238 exit status 1
Jan 25 14:08:09 server postfix/master[9108]: warning: /usr/lib/postfix/smtpd: ba d command startup -- throttling
Jan 25 14:09:09 server postfix/smtpd[30358]: warning: SASL per-process initializ ation failed: generic failure
Jan 25 14:09:09 server postfix/smtpd[30358]: fatal: SASL per-process initializat ion failed
Jan 25 14:09:10 server postfix/master[9108]: warning: process /usr/lib/postfix/s mtpd pid 30358 exit status 1
Jan 25 14:09:10 server postfix/master[9108]: warning: /usr/lib/postfix/smtpd: ba d command startup -- throttling
Jan 25 14:10:10 server postfix/smtpd[30478]: warning: SASL per-process initializ ation failed: generic failure
Jan 25 14:10:10 server postfix/smtpd[30478]: fatal: SASL per-process initializat ion failed
Jan 25 14:10:11 server postfix/master[9108]: warning: process /usr/lib/postfix/s mtpd pid 30478 exit status 1
Jan 25 14:10:11 server postfix/master[9108]: warning: /usr/lib/postfix/smtpd: ba d command startup -- throttling
Jan 25 14:11:11 server postfix/smtpd[30598]: warning: SASL per-process initializ ation failed: generic failure
Jan 25 14:11:11 server postfix/smtpd[30598]: fatal: SASL per-process initializat ion failed
Jan 25 14:11:12 server postfix/master[9108]: warning: process /usr/lib/postfix/s mtpd pid 30598 exit status 1
Jan 25 14:11:12 server postfix/master[9108]: warning: /usr/lib/postfix/smtpd: ba d command startup -- throttling
Jan 25 14:12:13 server postfix/smtpd[30717]: warning: SASL per-process initializ ation failed: generic failure
Jan 25 14:12:13 server postfix/smtpd[30717]: fatal: SASL per-process initializat ion failed
Jan 25 14:12:13 server postfix/master[9108]: warning: process /usr/lib/postfix/s mtpd pid 30717 exit status 1
Jan 25 14:12:13 server postfix/master[9108]: warning: /usr/lib/postfix/smtpd: ba d command startup -- throttling
Jan 25 14:12:19 server postfix/master[9108]: terminating on signal 15
Jan 26 10:33:22 server postfix/master[2378]: daemon started -- version 2.3.8, co nfiguration /etc/postfix
Jan 26 10:35:11 server postfix/smtpd[2734]: warning: SASL per-process initializa tion failed: generic failure
Jan 26 10:35:11 server postfix/smtpd[2734]: fatal: SASL per-process initializati on failed
Jan 26 10:35:12 server postfix/master[2378]: warning: process /usr/lib/postfix/s mtpd pid 2734 exit status 1
Jan 26 10:35:12 server postfix/master[2378]: warning: /usr/lib/postfix/smtpd: ba d command startup -- throttling
Jan 26 10:36:12 server postfix/smtpd[2854]: warning: SASL per-process initializa tion failed: generic failure
Jan 26 10:36:12 server postfix/smtpd[2854]: fatal: SASL per-process initializati on failed
Jan 26 10:36:13 server postfix/master[2378]: warning: process /usr/lib/postfix/s mtpd pid 2854 exit status 1
Jan 26 10:36:13 server postfix/master[2378]: warning: /usr/lib/postfix/smtpd: ba d command startup -- throttling
Jan 26 10:37:13 server postfix/smtpd[2974]: warning: SASL per-process initializa tion failed: generic failure
Jan 26 10:37:13 server postfix/smtpd[2974]: fatal: SASL per-process initializati on failed
Jan 26 10:37:14 server postfix/master[2378]: warning: process /usr/lib/postfix/s mtpd pid 2974 exit status 1
Jan 26 10:37:14 server postfix/master[2378]: warning: /usr/lib/postfix/smtpd: ba d command startup -- throttling
Jan 26 10:38:14 server postfix/smtpd[3094]: warning: SASL per-process initializa tion failed: generic failure
Jan 26 10:38:14 server postfix/smtpd[3094]: fatal: SASL per-process initializati on failed
Jan 26 10:38:15 server postfix/master[2378]: warning: process /usr/lib/postfix/s mtpd pid 3094 exit status 1
Jan 26 10:38:15 server postfix/master[2378]: warning: /usr/lib/postfix/smtpd: ba d command startup -- throttling
Jan 27 09:47:46 server postfix/master[2365]: daemon started -- version 2.3.8, co nfiguration /etc/postfix
server:~#

 

/etc/default/saslauthd and /etc/postfix/sasl/smtpd.conf

server:~# cat /etc/default/saslauthd
#
# Settings for saslauthd daemon
#

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

# 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)
# See the saslauthd man page for information about these options.
#
# Example for postfix users: "-c -m /var/spool/postfix/var/run/saslauthd"
# Note: See /usr/share/doc/sasl2-bin/README.Debian
OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd -r"
server:~# clear
server:~#
server:~#
server:~#
server:~# cat /etc/default/saslauthd
#
# Settings for saslauthd daemon
#

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

# 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)
# See the saslauthd man page for information about these options.
#
# Example for postfix users: "-c -m /var/spool/postfix/var/run/saslauthd"
# Note: See /usr/share/doc/sasl2-bin/README.Debian
OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd -r"
server:~#




server:~# cat /etc/postfix/sasl/smtpd.conf
pwcheck method: saslauthd
mech_listlain login
pwcheck_method: saslauthd
mech_list: plain login
pwcheck_method: saslauthd
mech_list: plain login
pwcheck_method: saslauthd
mech_list: plain login
server:~#

 

Im having the same problems. Im getting to the telnet and it hangs. Anyhelp is much appreciated. Thank you

 

You need

Code:

pwcheck_method: saslauthd
mech_list: plain login

only once in your smtpd.conf.

 

Please open a new thread for this.

 

hi falko thanks one for all but not lasts one

hey hey hey as promise i redone all from beginning and seem all work fine so before i install ISPconfig i like to know how to test all services to know if they are working ?
one more questiions ?>>>#
i have a broadband with dynamic IP like
and i have a router and i use three computer conected to it one 4 me and 2 4 other friends i can ascess my sever from there computer thats fine like use putty with ip address ex: 192.168.2.1
and when i use the name i can't like ex: sever1.example.com
it can't find the host name:

and second questions is how can i access my sever1.example.com from any computer from a cyber cafe or in other house or like i have some friends in another country like to conect to it how please help


i have configure my router on Nat option enable
ans i add my linux ip like 192.168.2.110 to port 22 but it don't work any tut on it #
i use canyon router thanks 4 help

 

You can add server1.example.com to the clients' hosts files: http://www.howtoforge.com/forums/showthread.php?t=432&highlight=hosts+file+windows

You can get a hostname from dyndns.org pointing to your router's public IP address (you can make your router update the dyndns.org address whenever the IP address changes) and make your router forward all needed ports to your computer.