List Info

Thread: Kolab2 V2.1.0 Final SMTP over SSL > problem talking to server private/kolabpolicy: Socket operation




Kolab2 V2.1.0 Final SMTP over SSL > problem talking to server private/kolabpolicy: Socket operation
country flaguser name
Switzerland
2007-06-02 07:26:09
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:

==> /kolab/var/postfix/log/postfix.log <==
Jun 02 12:24:55 kolab2 <info> postfix/smtpd[2815]:
connect from
147-164.3-85.cust.bluewin.ch[85.3.164.147]
Jun 02 12:24:55 kolab2 <info> 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> 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> 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>
to=<solivacomcept.ch> proto=ESMTP
helo=<Amilo>
Jun 02 12:25:00 kolab2 <info> 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-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Re: Kolab2 V2.1.0 Final SMTP over SSL > problem talking to server private/kolabpolicy:
user name
2007-06-02 11:10:04

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">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">domenicawojnowski.ch> to=< solivacomcept.ch">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">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 )