Hello,
I've been trying to setup postfix with tls and smtp auth (dovecot sasl).
I'm now stuck with the smtp auth part, with a strange error. For a few
days I've tried to search information about similar problems, but found
none. Now I'm hoping somebody here could help me out. I'm running Ubuntu
Jaunty on AMD64.
I've disabled tls (and a lot of other options, and not running in a
chroot jail) for now. The problem is, that as soon as I enable smtp auth
in postfix (smtpd_sasl_auth_enable), smtp stops working. When doing
bash:# telnet localhost 25
Trying ::1...
Connected to localhost.
Escape character is '^]'.
...and it halts, and timeouts. Never prints the banner. I've get
increased logging enabled ('smtpd -vv' in master.cf) and below is the
relevant part, with the 'no SASL authentication mechanisms' print:
Apr 24 15:42:30 server postfix/smtpd[8126]: xsasl_dovecot_server_create:
SASL service=smtp, realm=(null)
Apr 24 15:42:30 server postfix/smtpd[8126]: name_mask: noanonymous
Apr 24 15:42:30 server postfix/smtpd[8126]:
xsasl_dovecot_server_connect: Connecting
Apr 24 15:42:40 server postfix/smtpd[8126]:
xsasl_dovecot_server_connect: auth reply: status
Apr 24 15:42:50 server postfix/smtpd[8126]: fatal: no SASL
authentication mechanisms
Apr 24 15:42:50 server postfix/pipe[8128]: warning: unexpected
end-of-input from dovecot socket while reading input attribute name
Apr 24 15:42:50 server postfix/pipe[8128]: warning: deliver_request_get:
error receiving common attributes
Apr 24 15:42:51 server postfix/master[8903]: warning: process
/usr/lib/postfix/smtpd pid 8126 exit status 1
I've seen the 'no SASL authentication mechanisms' erros with google, but
usually because postfix is unable to find the dovecot client auth
socket. I don't think this is my problem. Below are output of 'postconf
-n' and 'dovecot -n' commands:
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
canonical_maps = hash:/etc/postfix/canonical
config_directory = /etc/postfix
home_mailbox = Maildir/
inet_interfaces = all
inet_protocols = all
mailbox_command = /usr/lib/dovecot/deliver -c
/etc/dovecot/dovecot-postfix.conf -n -m "${EXTENSION}"
mydestination =
mydomain = *my.domain*
myhostname = *server.at.my.domain*
mynetworks = 127.0.0.0/8, 192.168.0.0/24, [::1]/128
myorigin = /etc/mailname
readme_directory = no
relay_domains =
relayhost = [*my.isp.provider*]
smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
smtpd_sasl_auth_enable = yes
smtpd_sasl_path = private/dovecot
smtpd_sasl_type = dovecot
strict_rfc821_envelopes = yes
virtual_gid_maps = static:5000
virtual_mailbox_domains = /etc/postfix/vhosts
virtual_minimum_uid = 1000
virtual_transport = dovecot
virtual_uid_maps = static:5000
# 1.1.11: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.28-11-server x86_64 Ubuntu 9.04 ext3
base_dir: /var/run/dovecot/
log_path: /var/log/dovecot.log
info_log_path: /var/log/dovecot-info.log
ssl_cert_file: /etc/ssl/certs/dovecot.pem
ssl_key_file: /etc/ssl/private/dovecot.pem
disable_plaintext_auth: no
login_dir: /var/run/dovecot//login
login_executable: /usr/lib/dovecot/imap-login
valid_chroot_dirs: /var/spool/vmail
mail_location: maildir:/home/vmail/%d/%n/Maildir
auth default:
mechanisms: plain login
debug: yes
passdb:
driver: passwd-file
args: /etc/dovecot/passwd
userdb:
driver: static
args: uid=vmail gid=vmail home=/home/vmail/%d/%n
socket:
type: listen
client:
path: /var/spool/postfix/private/auth
mode: 438
user: postfix
group: postfix
master:
path: /var/run/dovecot/auth-master
mode: 384
user: vmail
I can see the private/auth socket created when dovecot starts, with
postfix:postfix permissions. Also, netstat shows it:
bash:# netstat -ln | grep dovecot
unix 2 [ ACC ] STREAM LISTENING 111791 private/dovecot
unix 2 [ ACC ] STREAM LISTENING 120787
/var/run/dovecot//dict-server
unix 2 [ ACC ] STREAM LISTENING 120789
/var/run/dovecot//login/default
unix 2 [ ACC ] STREAM LISTENING 120800
/var/run/dovecot/auth-master
unix 2 [ ACC ] STREAM LISTENING 120803
/var/run/dovecot//auth-worker.29982
I'm totally clueless as to what to try next. Does anybody here have any
suggestions how to continue, what to try or debug. I'd bee very greatful
for any ideas.
TIA,
Juha Pahkala
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
