I experiance the same problems: Mails can bei read and be sent to the server, but they can't be sent from my Computer and my Outlook program to the server; the authentification will fail.
I set up a completely new server with Debian 3.1 and after setup I immediately started with the "Perfect Debian Sarge Setup" by Falko. Also, I installed ISPconfig.
This is my main.cf:
Code:
# See /usr/share/postfix/main.cf.dist for a commented, more complete version
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
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 = titania.kriegshammer.info
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
#mydestination = titania.kriegshammer.info, localhost.kriegshammer.info, localhost
relayhost =
mynetworks = 127.0.0.0/8
mailbox_command = procmail -a "$EXTENSION"
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
smtpd_sasl_local_domain = $myhostname
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
This is my /etc/default/saslauthd:
Code:
# This needs to be uncommented before saslauthd will be run automatically
START=yes
PARAMS="-m /var/spool/postfix/var/run/saslauthd -r"
# 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"
/etc/init.d/saslauthd restart --> it says, the sasl demon is not running:
Code:
Stopping SASL Authentication Daemon: (not running).
Starting SASL Authentication Daemon: (failed).
But ps aux | grep sasl --> it says, that saslauth IS running:
Code:
titania:/etc/postfix# ps aux | grep sasl
root 2073 0.0 0.1 34900 2396 ? Ss Apr06 0:00 /usr/sbin/saslauthd -m /var/spool/postfix/var/run/saslauthd -r -a pam
root 2074 0.0 0.1 34900 2392 ? S Apr06 0:00 /usr/sbin/saslauthd -m /var/spool/postfix/var/run/saslauthd -r -a pam
root 2075 0.0 0.1 34900 2396 ? S Apr06 0:00 /usr/sbin/saslauthd -m /var/spool/postfix/var/run/saslauthd -r -a pam
root 2076 0.0 0.1 34900 2396 ? S Apr06 0:00 /usr/sbin/saslauthd -m /var/spool/postfix/var/run/saslauthd -r -a pam
root 2078 0.0 0.1 34900 2416 ? S Apr06 0:00 /usr/sbin/saslauthd -m /var/spool/postfix/var/run/saslauthd -r -a pam
root 29646 0.0 0.0 2900 608 pts/0 R+ 14:36 0:00 grep sasl
titania:/etc/postfix#
So, I guess, that sasld dows not work properly.
Also, there is no /etc/pam.d/smpt included in the "perfect debian 3.1 setup guide"... you can't simply copy the one from the other tutorial, because it uses mysql auth, and this one doesn't.
I have no clue how to solve this ...
Maybe it would be good to use shadow instead of pam, but I don't know how to do this...
Can you help us with this issue please, falko?
Recent comments
1 day 10 hours ago
1 day 13 hours ago
1 day 14 hours ago
1 day 15 hours ago
1 day 17 hours ago
1 day 19 hours ago
1 day 20 hours ago
2 days 12 hours ago
2 days 13 hours ago
2 days 16 hours ago