SMTP SSL problem after upgrade from kolab 2.1 to 2.2.0
Otmar Stahl
O.Stahl at lsw.uni-heidelberg.de
Thu Jan 1 10:18:33 CET 2009
Hello and happy new year,
After an upgrade from kolab 2.1 to 2.2.0 I have a problem with sending
mail via ssl from outside the kolab domain. This worked in kolab 2.1.
The error message I get with thunderbird is:
"An error occured while sending the mail. The server reponded: 4.3.5
Server configuration problem. Please check the message recipients and
try again."
The corresponding lines in the postfix.log are the following:
"Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
connect from p5B0770BE.dip.t-dialin.net[91.7.112.190]
Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
setting up TLS connection from p5B0770BE.dip.t-dialin.net[91.7.112.190]
Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
TLS connection established from
p5B0770BE.dip.t-dialin.net[91.7.112.190]: TLSv1 with cipher
DHE-RSA-AES256-SHA (256/256 bits)
Jan 01 09:55:05 srv0.lsw.uni-heidelberg.de <warning>
postfix/spawn[4146]: warning: command /kolab/etc/kolab/kolab_smtpdpolicy
exit status 2
Jan 01 09:55:05 srv0.lsw.uni-heidelberg.de <warning>
postfix/smtpd[4143]: warning: premature end-of-input on
private/kolabpolicy while reading input attribute name
Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <warning>
postfix/spawn[4146]: warning: command /kolab/etc/kolab/kolab_smtpdpolicy
exit status 2
Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <warning>
postfix/smtpd[4143]: warning: premature end-of-input on
private/kolabpolicy while reading input attribute name
Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <warning>
postfix/smtpd[4143]: warning: problem talking to server
private/kolabpolicy: Connection reset by peer
Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
NOQUEUE: reject: RCPT from p5B0770BE.dip.t-dialin.net[91.7.112.190]: 451
4.3.5 Server configuration problem; from=<O.Stahl at lsw.uni-heidelberg.de>
to=<otmarstahl at web.de> proto=ESMTP helo=<[192.168.0.21]"
Any idea what could be causing this? How can I debug this issue?
Thank you in advance for your help,
Kind regards,
Otmar Stahl
More information about the users
mailing list