List Info

Thread: AW: Kolab2 V2.1.0 Final SMTP over SSL > problemtalkingto server private/kolabpolicy: S




AW: Kolab2 V2.1.0 Final SMTP over SSL > problemtalkingto server private/kolabpolicy: S
country flaguser name
Switzerland
2007-06-03 07:23:51
Hi Alain
 
anyway thanks for the answer but the link could not help meaning why should I manipulate the unix or inet position if it works. It is clear a kolab policy issue but I do not know where to manipulate. The function is here this has brought up the tests and from this point of view no manipulation depending inet or unix is required.
 
I'm looking forward that probably somebody from the development is answering and helping me....
 
Anyway many thanks again for your time.
 
Andrea


Von: Alain Spineux [mailto:aspineuxgmail.com]
Gesendet: Sonntag, 3. Juni 2007 13:29
An: ComCept Net GmbH Andrea Soliva
Cc: Kolab development coordination; kolab-userskolab.org
Betreff: Re: [Kolab-devel] Kolab2 V2.1.0 Final SMTP over SSL > problemtalkingto server private/kolabpolicy: Socket operation onnon-socket


On 6/3/07, ComCept Net GmbH Andrea Soliva <comcept.ch">solivacomcept.ch> wrote:
Yes Sir Solaris 10 11/06 Sparc ;latest recommended cluster May 2007

Too bad

Why you are asking....this should have nothing to do with the below message or?

This is a old supporting technic, ask a unexpected question and say the problem is their.

-&gt; The problem is SOLARIS

Then add : Their is no know solution for this problem.

-> I have no solution for your issue.

And then a big laugh because of this hilarious joke
Sorry

look at
http://archives.neohapsis.com/archives/postfix/2004-03/1082.html
if it help.


Andrea


Von: kolab.org" target=_blank>kolab-users-bounceskolab.org [mailto:kolab.org" target=_blank>kolab-users-bounceskolab.org] Im Auftrag von Alain Spineux
Gesendet: Samstag, 2. Juni 2007 20:51
An: Kolab development coordination
Cc: kolab.org" target=_blank>kolab-userskolab.org
Betreff: Re: [Kolab-devel] Kolab2 V2.1.0 Final SMTP over SSL > problemtalkingto server private/kolabpolicy: Socket operation onnon-socket

Are you using SOLARIS ?

On 6/2/07, ComCept Net GmbH Andrea Soliva <comcept.ch" target=_blank>solivacomcept.ch> wrote:
Hi Alain
 
I checked the /kolab/var/resmgr/resmgr.log. No errors at all also not in the time of test. The local connection with the untouched useraccount and with the absolut same configuration worked. Here as mentioned the logs from this test/connection:
 
LOCAL TEST WITH SAME ACCOUNT:
 
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[9033]: connect from PCG-GRT716S[xxx.xxx.xxx.x]
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[9033]: setting up TLS connection from PCG-GRT716S[xxx.xxx.xxx.x]
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[9033]: TLS connection established from PCG-GRT716S[xxx.xxx.xxx.x]: TLSv1 with cipher RC
4-MD5 (128/128 bits)
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[9033]: 808249D1F: client=PCG-GRT716S[xxx.xxx.xxx.x], sasl_method=LOGIN, sasl_username=wojnowski.ch" target=_blank>domenicawojnowski.ch
Jun 02 13:12:04 kolab2 <info&gt; postfix/cleanup[8895]: 808249D1F: message-id=<kolab2.comcept.ch" target=_blank>20070602111204.808249D1Fkolab2.comcept.ch >
Jun 02 13:12:04 kolab2 <info&gt; postfix/qmgr[7038]: 808249D1F: from=<wojnowski.ch" target=_blank> domenicawojnowski.ch >, size=649, nrcpt=1 (queue active)
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[9033]: disconnect from PCG-GRT716S[xxx.xxx.xxx.x]
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[8898]: connect from localhost[127.0.0.1]
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[8898]: C63539DE2: client=localhost[127.0.0.1]
Jun 02 13:12:04 kolab2 <info&gt; postfix/cleanup[8899]: C63539DE2: message-id=<kolab2.comcept.ch" target=_blank>20070602111204.808249D1Fkolab2.comcept.ch >
Jun 02 13:12:04 kolab2 <info&gt; postfix/qmgr[7038]: C63539DE2: from=<wojnowski.ch" target=_blank> domenicawojnowski.ch >, size=824, nrcpt=1 (queue active)
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[8898]: disconnect from localhost[127.0.0.1]
Jun 02 13:12:04 kolab2 <info&gt; postfix/pipe[8896]: 808249D1F: to=<wojnowski.ch" target=_blank>domenicawojnowski.ch >, relay=kolabfilter, delay=0, status=sent (kola
b2.comcept.ch)
Jun 02 13:12:04 kolab2 <info&gt; postfix/qmgr[7038]: 808249D1F: removed
 
TEST WITH "NONE FIX IP FROM INTERNET" ENTERED IN TRUSTED NETWORK:
 
Jun 02 13:23:23 kolab2 <info&gt; postfix/smtpd[10675]: connect from 100-132.3-85.cust.bluewin.ch[85.3.132.100]
Jun 02 13:23:23 kolab2 <info&gt; postfix/smtpd[10675]: setting up TLS connection from 100-132.3-85.cust.bluewin.ch[85.3.132.100]
Jun 02 13:23:23 kolab2 <info&gt; postfix/smtpd[10675]: TLS connection established from 100-132.3-85.cust.bluewin.ch[85.3.132.100]: TLSv
1 with cipher RC4-MD5 (128/128 bits)
Jun 02 13:23:23 kolab2 <info&gt; postfix/smtpd[10675]: 8A8E7A179: client=100-132.3-85.cust.bluewin.ch[85.3.132.100], sasl_method=LOGIN,
&nbsp;wojnowski.ch" target=_blank>sasl_username=domenicawojnowski.ch
Jun 02 13:23:24 kolab2 <info&gt; postfix/cleanup[10447]: 8A8E7A179: message-id=<Amilo" target=_blank>000001c7a508$5d781260$2101a8c0Amilo >
Jun 02 13:23:24 kolab2 <info&gt; postfix/qmgr[10181]: 8A8E7A179: from=<wojnowski.ch" target=_blank>domenicawojnowski.ch>, size=2172, nrcpt=1 (queue active)
Jun 02 13:23:24 kolab2 <info&gt; postfix/smtpd[10450]: connect from localhost[127.0.0.1]
Jun 02 13:23:24 kolab2 <info&gt; postfix/smtpd[10450]: 69BC9A17B: client=localhost[127.0.0.1]
Jun 02 13:23:24 kolab2 <info&gt; postfix/cleanup[10451]: 69BC9A17B: message-id=<Amilo" target=_blank>000001c7a508$5d781260$2101a8c0Amilo>
Jun 02 13:23:24 kolab2 <info&gt; postfix/qmgr[10181]: 69BC9A17B: from=<wojnowski.ch" target=_blank>domenicawojnowski.ch>, size=2345, nrcpt=1 (queue active)
Jun 02 13:23:24 kolab2 <info&gt; postfix/smtpd[10450]: disconnect from localhost[127.0.0.1]
Jun 02 13:23:24 kolab2 <info&gt; postfix/pipe[10448]: 8A8E7A179: to=<comcept.ch" target=_blank>solivacomcept.ch>, relay=kolabfilter, delay=1, status=sent (kolab
2.comcept.ch)
 
You see that is 100% a confirmation that actually all is working fine but "only" within local trusted network or if the IP is configured as trusted network even this solution is not visible (because it is not a fix IP).
 ;
What is here wrong.....except within the postfix.log I have no errors meaning I controlled all logs (really all .
 ;
Any help and explanation really appriciated.
 ;
Many thanks
 ;
Andrea
 ;
 ;
 ;


Von: kolab.org" target=_blank>kolab-devel-bounceskolab.org [mailto:kolab.org" target=_blank> kolab-devel-bounceskolab.org] Im Auftrag von Alain Spineux
Gesendet: Samstag, 2. Juni 2007 18:10
An: Kolab development coordination
Cc: kolab.org" target=_blank>kolab-userskolab.org
Betreff: Re: [Kolab-devel] Kolab2 V2.1.0 Final SMTP over SSL > problemtalking to server private/kolabpolicy: Socket operation onnon-socket


You should look about error messages from the kolab policy.
Maybe thei are in /kolab/var/resmgr/resmgr.log (not sure)

Also can you give the log a the successful connection you got, when connected locally ?

Regards.

Alain




On 6/2/07, ComCept Net GmbH Andrea Soliva <comcept.ch" target=_blank>solivacomcept.ch> wrote:
Hi all

I tested further with V2.1.0 Final and up to know it seems to work all fine
(internal trusted networks) with one exception:

I'm working with Toltec and the E-Mail account is configured with Port POP
over SSL TCP 995 as SMTP over SSL TCP 465. All is working fine without
problems.

The next test I did is I added a new domain wojnowski.ch and a user. This
user is not in my trusted network meaning this user makes requests somewhere
from the internet. On the firewall I opened:

POP over SSL TCP 995 as SMTP over SSL TCP 465

The Email account from the user is also configured with the specific ports
as the certificat is installed. The issue we have is following:

--> The user can fetch his emails over POP over SSL TCP 995 without
problems. As soon as he tries to send a mail over SMTP over SSL TCP 465 it
would not work:

==&gt; /kolab/var/postfix/log/postfix.log <==
Jun 02 12:24:55 kolab2 <info&gt; postfix/smtpd[2815]: connect from
147-164.3-85.cust.bluewin.ch[85.3.164.147]
Jun 02 12:24:55 kolab2 <info&gt; postfix/smtpd[2815]: setting up TLS connection
from 147-164.3-85.cust.bluewin.ch[ 85.3.164.147]
Jun 02 12:24:55 kolab2 <info&gt; 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)
Jun 02 12:24:56 kolab2 <warning> postfix/smtpd[2815]: warning: connect to
private/kolabpolicy: Socket operation on non-socket
Jun 02 12:24:56 kolab2 <warning> postfix/smtpd[2815]: warning: problem
talking to server private/kolabpolicy: Socket operation on non-socket
Jun 02 12:24:57 kolab2 <warning> postfix/smtpd[2815]: warning: connect to
private/kolabpolicy: Socket operation on non-socket
Jun 02 12:24:57 kolab2 <warning> postfix/smtpd[2815]: warning: problem
talking to server private/kolabpolicy: Socket operation on non-socket
Jun 02 12:24:57 kolab2 <info&gt; postfix/smtpd[2815]: NOQUEUE: reject: RCPT
from 147-164.3-85.cust.bluewin.ch[ 85.3.164.147]: 450 Server configuration
problem; from=<wojnowski.ch" target=_blank>domenicawojnowski.ch> to=<comcept.ch" target=_blank> solivacomcept.ch> proto=ESMTP
helo=<Amilo>
Jun 02 12:25:00 kolab2 <info&gt; postfix/smtpd[2815]: disconnect from
147-164.3-85.cust.bluewin.ch[85.3.164.147]


As a test I configured the account in my local network (trusted network)
with the same config as the user has. It works without problems. If I look
to the error or warnings it seems to me that the kolabpolicy does not allow
this even the users is authenticating. The config over the manager interface
looks like following:

All services available except HTTP FreeBusy Service (Legacy) and POP3
Service

Quota not active

Freebusy not set

Priviliged networks set to 127.0.0.0/8, xxx.xxx.xxx.0/24,
xxx.xxx.xxx.0/24,, xxx.xxx.xxx.0/24

No Smart Relay Host set

Accept Internet Email not active

Domains both domains are visible

Mail Filter settings set to "Reject the message with the except if it
originates"


Temporarly I entered the IP from the user "85.3.164.147" to the trusted
network config and it worked fine. This user has now fix IP from this point
of view it is not visible to use such a config. At the moment I'm a little
bit confiused meaning is this configuration I would like to have not visible
meaning having user travelling around the world and using kolab2 for sending
emails?

Can somebody point me in the correct direction or is it something which
should work and does not in V2.1.0 (Bug?).

For any answer many thanks in advanced.

Kind regards

Andrea

_______________________________________________
Kolab-devel mailing list
kolab.org" target=_blank>Kolab-develkolab.org
https://kolab.org/mailman/listinfo/kolab-devel



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

_______________________________________________
Kolab-devel mailing list
kolab.org" target=_blank>Kolab-develkolab.org
https://kolab.org/mailman/listinfo/kolab-devel



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

_______________________________________________
Kolab-users mailing list
kolab.org">Kolab-userskolab.org
https://kolab.org/mailman/listinfo/kolab-users




--
--
Alain Spineux
aspineux gmail com
May the sources be with you
Re: Kolab2 V2.1.0 Final SMTP over SSL > problemtalkingto server private/kolabpolicy: S
user name
2007-06-03 07:42:06


On 6/3/07, ComCept Net GmbH Andrea Soliva < solivacomcept.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> solivacomcept.ch> wrote:
Hi Alain
 
anyway thanks for the answer but the link could not help meaning why should I manipulate the unix or inet position if it works. It is clear a kolab policy issue but I do not know where to manipulate. The function is here this has brought up the tests and from this point of view no manipulation depending inet or unix is required.
 
I'm looking forward that probably somebody from the development is answering and helping me....

You have anticipated my next answer.
You can fill in a bug on the track https://intevation.de/roundup/kolab


Anyway many thanks again for your time.
 
Andrea


Von: Alain Spineux [mailto: aspineuxgmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">aspineuxgmail.com]
Gesendet: Sonntag, 3. Juni 2007 13:29
An: ComCept Net GmbH Andrea Soliva
Cc: Kolab development coordination; kolab-userskolab.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">kolab-userskolab.org

Betreff: Re: [Kolab-devel] Kolab2 V2.1.0 Final SMTP over SSL > problemtalkingto server private/kolabpolicy: Socket operation onnon-socket


On 6/3/07, ComCept Net GmbH Andrea Soliva < solivacomcept.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">solivacomcept.ch> wrote:
Yes Sir Solaris 10 11/06 Sparc ;latest recommended cluster May 2007

Too bad

Why you are asking....this should have nothing to do with the below message or?

This is a old supporting technic, ask a unexpected question and say the problem is their.

-&gt; The problem is SOLARIS

Then add : Their is no know solution for this problem.

-> I have no solution for your issue.

And then a big laugh because of this hilarious joke
Sorry

look at
http://archives.neohapsis.com/archives/postfix/2004-03/1082.html
if it help.


Andrea


Von: kolab-users-bounceskolab.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">kolab-users-bounceskolab.org [mailto: kolab-users-bounceskolab.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> kolab-users-bounceskolab.org] Im Auftrag von Alain Spineux
Gesendet: Samstag, 2. Juni 2007 20:51
An: Kolab development coordination
Cc: kolab-userskolab.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> kolab-userskolab.org
Betreff: Re: [Kolab-devel] Kolab2 V2.1.0 Final SMTP over SSL > problemtalkingto server private/kolabpolicy: Socket operation onnon-socket

Are you using SOLARIS ?

On 6/2/07, ComCept Net GmbH Andrea Soliva < solivacomcept.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">solivacomcept.ch> wrote:
Hi Alain
 
I checked the /kolab/var/resmgr/resmgr.log. No errors at all also not in the time of test. The local connection with the untouched useraccount and with the absolut same configuration worked. Here as mentioned the logs from this test/connection:
 
LOCAL TEST WITH SAME ACCOUNT:
 
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[9033]: connect from PCG-GRT716S[xxx.xxx.xxx.x]
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[9033]: setting up TLS connection from PCG-GRT716S[xxx.xxx.xxx.x]
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[9033]: TLS connection established from PCG-GRT716S[xxx.xxx.xxx.x]: TLSv1 with cipher RC
4-MD5 (128/128 bits)
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[9033]: 808249D1F: client=PCG-GRT716S[xxx.xxx.xxx.x], sasl_method=LOGIN, sasl_username= domenicawojnowski.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">domenicawojnowski.ch
Jun 02 13:12:04 kolab2 <info&gt; postfix/cleanup[8895]: 808249D1F: message-id=< 20070602111204.808249D1Fkolab2.comcept.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">20070602111204.808249D1Fkolab2.comcept.ch >
Jun 02 13:12:04 kolab2 <info&gt; postfix/qmgr[7038]: 808249D1F: from=< domenicawojnowski.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> domenicawojnowski.ch >, size=649, nrcpt=1 (queue active)
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[9033]: disconnect from PCG-GRT716S[xxx.xxx.xxx.x]
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[8898]: connect from localhost[127.0.0.1]
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[8898]: C63539DE2: client=localhost[127.0.0.1]
Jun 02 13:12:04 kolab2 <info&gt; postfix/cleanup[8899]: C63539DE2: message-id=< 20070602111204.808249D1Fkolab2.comcept.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">20070602111204.808249D1Fkolab2.comcept.ch >
Jun 02 13:12:04 kolab2 <info&gt; postfix/qmgr[7038]: C63539DE2: from=< domenicawojnowski.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> domenicawojnowski.ch >, size=824, nrcpt=1 (queue active)
Jun 02 13:12:04 kolab2 <info&gt; postfix/smtpd[8898]: disconnect from localhost[127.0.0.1]
Jun 02 13:12:04 kolab2 <info&gt; postfix/pipe[8896]: 808249D1F: to=< domenicawojnowski.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">domenicawojnowski.ch >, relay=kolabfilter, delay=0, status=sent (kola
b2.comcept.ch)
Jun 02 13:12:04 kolab2 <info&gt; postfix/qmgr[7038]: 808249D1F: removed
 
TEST WITH "NONE FIX IP FROM INTERNET&quot; ENTERED IN TRUSTED NETWORK:
 
Jun 02 13:23:23 kolab2 <info&gt; postfix/smtpd[10675]: connect from 100-132.3-85.cust.bluewin.ch[85.3.132.100]
Jun 02 13:23:23 kolab2 <info&gt; postfix/smtpd[10675]: setting up TLS connection from 100-132.3-85.cust.bluewin.ch[85.3.132.100]
Jun 02 13:23:23 kolab2 <info&gt; postfix/smtpd[10675]: TLS connection established from 100-132.3-85.cust.bluewin.ch[85.3.132.100]: TLSv
1 with cipher RC4-MD5 (128/128 bits)
Jun 02 13:23:23 kolab2 <info&gt; postfix/smtpd[10675]: 8A8E7A179: client=100-132.3-85.cust.bluewin.ch[85.3.132.100], sasl_method=LOGIN,
&nbsp; sasl_username=domenicawojnowski.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">sasl_username=domenicawojnowski.ch
Jun 02 13:23:24 kolab2 <info&gt; postfix/cleanup[10447]: 8A8E7A179: message-id=< 000001c7a508$5d781260$2101a8c0Amilo" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">000001c7a508$5d781260$2101a8c0Amilo >
Jun 02 13:23:24 kolab2 <info&gt; postfix/qmgr[10181]: 8A8E7A179: from=< domenicawojnowski.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">domenicawojnowski.ch>, size=2172, nrcpt=1 (queue active)
Jun 02 13:23:24 kolab2 <info&gt; postfix/smtpd[10450]: connect from localhost[127.0.0.1]
Jun 02 13:23:24 kolab2 <info&gt; postfix/smtpd[10450]: 69BC9A17B: client=localhost[127.0.0.1]
Jun 02 13:23:24 kolab2 <info&gt; postfix/cleanup[10451]: 69BC9A17B: message-id=< 000001c7a508$5d781260$2101a8c0Amilo" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">000001c7a508$5d781260$2101a8c0Amilo &gt;
Jun 02 13:23:24 kolab2 <info&gt; postfix/qmgr[10181]: 69BC9A17B: from=< domenicawojnowski.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">domenicawojnowski.ch>, size=2345, nrcpt=1 (queue active)
Jun 02 13:23:24 kolab2 <info&gt; postfix/smtpd[10450]: disconnect from localhost[127.0.0.1]
Jun 02 13:23:24 kolab2 <info&gt; postfix/pipe[10448]: 8A8E7A179: to=< solivacomcept.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">solivacomcept.ch>, relay=kolabfilter, delay=1, status=sent (kolab
2.comcept.ch)
 
You see that is 100% a confirmation that actually all is working fine but "only" within local trusted network or if the IP is configured as trusted network even this solution is not visible (because it is not a fix IP).
 ;
What is here wrong.....except within the postfix.log I have no errors meaning I controlled all logs (really all .
 ;
Any help and explanation really appriciated.
 ;
Many thanks
 ;
Andrea
 ;
 ;
 ;


Von: kolab-devel-bounceskolab.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">kolab-devel-bounceskolab.org [mailto: kolab-devel-bounceskolab.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> kolab-devel-bounceskolab.org] Im Auftrag von Alain Spineux
Gesendet: Samstag, 2. Juni 2007 18:10
An: Kolab development coordination
Cc: kolab-userskolab.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">kolab-userskolab.org
Betreff: Re: [Kolab-devel] Kolab2 V2.1.0 Final SMTP over SSL > problemtalking to server private/kolabpolicy: Socket operation onnon-socket


You should look about error messages from the kolab policy.
Maybe thei are in /kolab/var/resmgr/resmgr.log (not sure)

Also can you give the log a the successful connection you got, when connected locally ?

Regards.

Alain




On 6/2/07, ComCept Net GmbH Andrea Soliva < solivacomcept.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">solivacomcept.ch> wrote:
Hi all

I tested further with V2.1.0 Final and up to know it seems to work all fine
(internal trusted networks) with one exception:

I'm working with Toltec and the E-Mail account is configured with Port POP
over SSL TCP 995 as SMTP over SSL TCP 465. All is working fine without
problems.

The next test I did is I added a new domain wojnowski.ch and a user. This
user is not in my trusted network meaning this user makes requests somewhere
from the internet. On the firewall I opened:

POP over SSL TCP 995 as SMTP over SSL TCP 465

The Email account from the user is also configured with the specific ports
as the certificat is installed. The issue we have is following:

--> The user can fetch his emails over POP over SSL TCP 995 without
problems. As soon as he tries to send a mail over SMTP over SSL TCP 465 it
would not work:

==&gt; /kolab/var/postfix/log/postfix.log <==
Jun 02 12:24:55 kolab2 <info&gt; postfix/smtpd[2815]: connect from
147-164.3-85.cust.bluewin.ch[85.3.164.147]
Jun 02 12:24:55 kolab2 <info&gt; postfix/smtpd[2815]: setting up TLS connection
from 147-164.3-85.cust.bluewin.ch[ 85.3.164.147]
Jun 02 12:24:55 kolab2 <info&gt; 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)
Jun 02 12:24:56 kolab2 <warning> postfix/smtpd[2815]: warning: connect to
private/kolabpolicy: Socket operation on non-socket
Jun 02 12:24:56 kolab2 <warning> postfix/smtpd[2815]: warning: problem
talking to server private/kolabpolicy: Socket operation on non-socket
Jun 02 12:24:57 kolab2 <warning> postfix/smtpd[2815]: warning: connect to
private/kolabpolicy: Socket operation on non-socket
Jun 02 12:24:57 kolab2 <warning> postfix/smtpd[2815]: warning: problem
talking to server private/kolabpolicy: Socket operation on non-socket
Jun 02 12:24:57 kolab2 <info&gt; postfix/smtpd[2815]: NOQUEUE: reject: RCPT
from 147-164.3-85.cust.bluewin.ch[ 85.3.164.147]: 450 Server configuration
problem; from=< domenicawojnowski.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">domenicawojnowski.ch> to=< solivacomcept.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> solivacomcept.ch> proto=ESMTP
helo=<Amilo>
Jun 02 12:25:00 kolab2 <info&gt; postfix/smtpd[2815]: disconnect from
147-164.3-85.cust.bluewin.ch[85.3.164.147]


As a test I configured the account in my local network (trusted network)
with the same config as the user has. It works without problems. If I look
to the error or warnings it seems to me that the kolabpolicy does not allow
this even the users is authenticating. The config over the manager interface
looks like following:

All services available except HTTP FreeBusy Service (Legacy) and POP3
Service

Quota not active

Freebusy not set

Priviliged networks set to 127.0.0.0/8, xxx.xxx.xxx.0/24,
xxx.xxx.xxx.0/24,, xxx.xxx.xxx.0/24

No Smart Relay Host set

Accept Internet Email not active

Domains both domains are visible

Mail Filter settings set to "Reject the message with the except if it
originates"


Temporarly I entered the IP from the user "85.3.164.147" to the trusted
network config and it worked fine. This user has now fix IP from this point
of view it is not visible to use such a config. At the moment I'm a little
bit confiused meaning is this configuration I would like to have not visible
meaning having user travelling around the world and using kolab2 for sending
emails?

Can somebody point me in the correct direction or is it something which
should work and does not in V2.1.0 (Bug?).

For any answer many thanks in advanced.

Kind regards

Andrea

_______________________________________________
Kolab-devel mailing list
Kolab-develkolab.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Kolab-develkolab.org
https://kolab.org/mailman/listinfo/kolab-devel



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

_______________________________________________
Kolab-devel mailing list
Kolab-develkolab.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Kolab-develkolab.org
https://kolab.org/mailman/listinfo/kolab-devel



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

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Kolab-userskolab.org
https://kolab.org/mailman/listinfo/kolab-users




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

_______________________________________________
Kolab-devel mailing list
Kolab-develkolab.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Kolab-develkolab.org
https://kolab.org/mailman/listinfo/kolab-devel



--
--
Alain Spineux
aspineux gmail com
May the sources be with you
[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )