[Kolab-devel] [issue1779] kolab 2.1 private/kolabpolicy: Socketoperation or non-socket

[ComCept Net GmbH Andrea Soliva]

I do not think so that this is important. I would say that every OS has this
bug because it is a Kolab 2.1 behavior and has nothing to to with the OS.
 
Andrea

  _____  

Von: kolab-devel-bounces at kolab.org [mailto:kolab-devel-bounces at kolab.org] Im
Auftrag von Alain Spineux
Gesendet: Freitag, 8. Juni 2007 12:52
An: Kolab development coordination
Cc: soliva at comcept.ch
Betreff: Re: [Kolab-devel] [issue1779] kolab 2.1 private/kolabpolicy:
Socketoperation or non-socket


You forgot to say your are running SOLARIS :-)
I thing this is important

Alain


On 6/8/07, Andrea <  <mailto:kolab-issues at intevation.de>
kolab-issues at intevation.de> wrote: 


New submission from Andrea < soliva at comcept.ch  <mailto:soliva at comcept.ch>
>:

A user with Outlook 2003 on the internet with a none fix ip is trying to
comunicat over TCP 995 POP over SSL and TCP 465 SMTP TLS to the kolab2
server.
Certivicat is correct installed as the client is correct configured. This
was 
confirmed by testing the client in the internal network.

- TCP 995 POP over SSL works without problems
- TCP 465 SMTP TLS does not work error which is shown in the postfix log
  is (no other errors available in other logs): 


==> /kolab/var/postfix/log/postfix.log <==
<info> postfix/smtpd[2815]: connect from 147-164.3-85.cust.bluewin.ch
[ 85.3.164.147 <http://85.3.164.147> ]
<info> postfix/smtpd[2815]: setting up TLS connection from 147-164.3-
85.cust.bluewin.ch[ 85.3.164.147]
<info> postfix/smtpd[2815]: TLS connection established from 147-164.3-
85.cust.bluewin.ch[85.3.164.147]: TLSv1 with cipher RC4-MD5 (128/128 bits)
<warning> postfix/smtpd[2815]: warning: connect to private/kolabpolicy:
Socket 
operation on non-socket 
<warning> postfix/smtpd[2815]: warning: problem talking to server
private/kolabpolicy: Socket operation on non-socket
<warning> postfix/smtpd[2815]: warning: connect to private/kolabpolicy:
Socket
operation on non-socket
<warning> postfix/smtpd[2815]: warning: problem  talking to server
private/kolabpolicy: Socket operation on non-socket
<info> postfix/smtpd[2815]: NOQUEUE: reject: RCPT from 147-164.3 -
85.cust.bluewin.ch[ 85.3.164.147]: 450 Server configuration problem;
from=<  <mailto:domenica at wojnowski.ch> domenica at wojnowski.ch> to=<
soliva at comcept.ch <mailto:soliva at comcept.ch> > proto=ESMTP helo=<Amilo>
<info> postfix/smtpd[2815]: disconnect from 147-164.3-85.cust.bluewin.ch
[ 85.3.164.147 <http://85.3.164.147> ]



If IP 85.3.164.147 would be temporary configured on the kolab2 Admin
WebInterface under trusted network all is working fine: 

==> /kolab/var/postfix/log/postfix.log <== 
<info> postfix/smtpd[10675]: connect from 147-164.3-85.cust.bluewin.ch
[ 85.3.164.147 <http://85.3.164.147> ]
<info> postfix/smtpd[10675]: setting up TLS connection from 147-164.3-
85.cust.bluewin.ch[85.3.164.147]
<info> postfix/smtpd[10675]: TLS connection established from 147-164.3-
85.cust.bluewin.ch[85.3.164.147  <http://85.3.164.147> ]: TLSv1 with cipher
RC4-MD5 (128/128 bits)
<info> postfix/smtpd[10675]: 8A8E7A179: client=
<http://147-164.3-85.cust.bluewin.ch> 147-164.3-85.cust.bluewin.ch
[85.3.164.147  <http://85.3.164.147> ], sasl_method=LOGIN,
sasl_username=domenica at wojnowski.ch
<info> postfix/cleanup[10447]: 8A8E7A179: message-id=<000001c7a508$5d781260 
$2101a8c0 at Amilo >
<info> postfix/qmgr[10181]: 8A8E7A179: from=< domenica at wojnowski.ch>,
size=2172,
nrcpt=1 (queue active)
<info> postfix/smtpd[10450]: connect from localhost[ 127.0.0.1]
<info> postfix/smtpd[10450]: 69BC9A17B: client=localhost[ 127.0.0.1]
<info> postfix/cleanup[10451]: 69BC9A17B: message-id=<000001c7a508$5d781260
$2101a8c0 at Amilo> 
<info> postfix/qmgr[10181]: 69BC9A17B: from=<
<mailto:domenica at wojnowski.ch> domenica at wojnowski.ch>, size=2345,
nrcpt=1 (queue active)
<info> postfix/smtpd[10450]: disconnect from localhost[ 127.0.0.1
<http://127.0.0.1> ]
<info> postfix/pipe[10448]: 8A8E7A179: to=< soliva at comcept.ch>,
relay=kolabfilter, delay=1, status=sent (  <http://kolab2.comcept.ch>
kolab2.comcept.ch)

This is from my point of view a bug and should work out of the box without 
configuring the none fix IP in the trusted networks on the Admin
WebInterface
(such a config is not visible).

Authentication is from my point of view not the problem because it works if
the
none fix ip is configured in the trusted networks on the Admin WebInterface.
T 

This function is very important to users which are traveling around the
world
and and using as secured smtp server (TCP 465 SMTP TLS) like kolab2 to send
messages.

Andrea Soliva

soliva at comcept.ch

----------
messages: 10781
nosy: soliva
priority: bug
status: unread
title: kolab 2.1 private/kolabpolicy: Socket operation or non-socket
________________________________________________ 
Kolab issue tracker <kolab-issues at intevation.de>
<  <https://intevation.de/roundup/kolab/issue1779>
https://intevation.de/roundup/kolab/issue1779> 
________________________________________________

_______________________________________________
Kolab-devel mailing list
Kolab-devel at kolab.org
https://kolab.org/mailman/listinfo/kolab-devel





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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/devel/attachments/20070611/929c84c0/attachment.html>