SMTP SSL problem after upgrade from kolab 2.1 to 2.2.0

Alain Spineux aspineux at gmail.com
Sun Jan 4 16:04:47 CET 2009


On Sun, Jan 4, 2009 at 1:13 PM, Otmar Stahl
<O.Stahl at lsw.uni-heidelberg.de> wrote:
> Hello again,
>
> Quoting Alain Spineux <aspineux at gmail.com>:
>
>> On Fri, Jan 2, 2009 at 1:56 PM, Otmar Stahl
>> <O.Stahl at lsw.uni-heidelberg.de> wrote:
>>> Hello,
>>>
>>> Thank you for the mail.
>>>
>>> Alain Spineux wrote:
>>>>
>>>> On Thu, Jan 1, 2009 at 10:18 AM, Otmar Stahl
>>>> <O.Stahl at lsw.uni-heidelberg.de> wrote:
>>>>>
>>>>> 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
>>>>
>>>> Something wrong is happening her, please look into
>>>> /kolab/var/kolab-filter/log/filter.log
>>>> for more error
>>>
>>> Thank you for this hint. Unfortunately, there is absolutely nothing logged
>>> in this file at the corresponding date. The sending attempt seems to die
>>> before it can log anything in filter.log. All I have is the postfix log :-(
>>>
>>> Kind regards,
>>> Otmar
>>>
>>
>> Sorry, The "policy" is a perl script, and log in the syslog, then you
>> should look into your /var/log/messages or /var/log/maillog or ...
>> depending your syslog configuration (the facility is "mail" and
>> priority is "info" )
>>
>> You can increase the verbosity by adding a -v in your master.cf.
>> Dont forget to make the chnage in the template.
>
> Thank you for the hints. I see errors only in postfix.log and adding
> -v to the policy script did not help. However I had a look at the
> policy script and tried to debug it by starting it from hand as
> suggested in the script. I get the following:
>
> -------------------------------------------------------------------------
> root at srv0:~#  su - kolab
> kolab at srv0$  /kolab/etc/kolab/kolab_smtpdpolicy
> IO object version 1.23_01 does not match bootstrap parameter 1.23 at

look like a probleme with perl installation.
Looks like something goes wrong during the upgrade.
Can you check the perl packages ?
Do they match the 2.2 version ?

Hope this help


> /kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 226.
> Compilation failed in require at
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/IO/Handle.pm line 263.
> BEGIN failed--compilation aborted at
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/IO/Handle.pm line 263.
> Compilation failed in require at
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/IO/Socket.pm line 11.
> BEGIN failed--compilation aborted at
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/IO/Socket.pm line 11.
> Compilation failed in require at
> /kolab/lib/perl/vendor_perl/5.10.0/Net/LDAP.pm line 8.
> BEGIN failed--compilation aborted at
> /kolab/lib/perl/vendor_perl/5.10.0/Net/LDAP.pm line 8.
> Compilation failed in require at /kolab/etc/kolab/kolab_smtpdpolicy line 26.
> BEGIN failed--compilation aborted at
> /kolab/etc/kolab/kolab_smtpdpolicy line 26.
>
> --------------------------------------------------------------------------
>
> So the script does not start at all and that should be a useful error
> message, but I still do not know what to do about it. Any hints how to
> fix this?
>
> Kind regards,
> Otmar
>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you




More information about the users mailing list