<br>This is not the problem now because he said it was working when adding remote IP in the networks.<br><br><br><div><span class="gmail_quote">On 6/3/07, <b class="gmail_sendername">Thomas Spuhler</b> <<a href="mailto:thomas@btspuhler.com">
thomas@btspuhler.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Sorry<br>should be thunderbird not firefox<br><br>
On Sunday 03 June 2007 12:14, Thomas Spuhler wrote:<br>> On Sunday 03 June 2007 10:36, ComCept Net GmbH Andrea Soliva wrote:<br>> > Hi Thomas<br>> ><br>> > Many thanks for that point but I do not understand you...can you give me
<br>> > more details meaning how can I reconfigure the client to use SSL. The<br>> > user is working with outlook 2003.....what I also not understand is that<br>> > he can fetch the mails over TCP POP-SSL meaning Port 995 and for that he
<br>> > uses also the authentication TLS or?<br>><br>> I don't use outlook. I can tell it better in mozilla-Thunderbid: you have<br>two<br>> options for both sending e-mail and receiving e-mail, tls or ssl
<br>> I am traveling a lot and tls works less and less. Hotels here as well as in<br>> G especially when sxxxcom it the wireless provider.<br>> I think the reason is that smtp over tls uses port 25 and many hotels etc
<br>> block this port because of guest may send out spam.<br>><br>> But I may be completely wrong in your case.<br>><br>> > If I look to the logs my understanding is that the authentication is<br>> > successful if the none fix IP from the internet is used in the trusted
<br>> > network configuration. From this point I do not think that this is a<br>> > problem of the authentication itself. It is more that postfix accepts the<br>> > connection (authentication) and would hand over to kolabpolicy but
<br>> > kolabpolicy does not accept it and this is the reason that for this<br>> > connection the socket is not available.<br>> ><br>> > Can you give me more details....how can I use the function over SSL on
<br>> > Outlook 2003?<br>> ><br>> > I can test even I do not think that this has something to do with the<br>> > authentication because as mentioned out from the logs the authentication<br>> > is done successful if the none fix IP from the internet is in the trusted
<br>> > network.<br>> ><br>> > Kind regards<br>> ><br>> > Andrea<br>> ><br>> ><br>> > -----Ursprüngliche Nachricht-----<br>> > Von: <a href="mailto:kolab-users-bounces@kolab.org">
kolab-users-bounces@kolab.org</a> [mailto:<a href="mailto:kolab-users-bounces@kolab.org">kolab-users-bounces@kolab.org</a>]<br>> > Im Auftrag von Thomas Spuhler<br>> > Gesendet: Sonntag, 3. Juni 2007 18:38<br>
> > An: <a href="mailto:kolab-users@kolab.org">kolab-users@kolab.org</a><br>> > Betreff: Re: AW: [Kolab-devel] Kolab2 V2.1.0 Final SMTP over SSL<br>> ><br>> > >problemtalkingto server private/kolabpolicy: Socket
<br>> > > operationonnon-socket<br>> ><br>> > On Saturday 02 June 2007 22:38, ComCept Net GmbH Andrea Soliva wrote:<br>> > > Yes Sir :-) Solaris 10 11/06 Sparc latest recommended cluster May 2007
<br>> > ><br>> > > Why you are asking....this should have nothing to do with the below<br>> ><br>> > message<br>> ><br>> > > or?<br>> > ><br>> > > Andrea<br>> > >
<br>> > > _____<br>> > ><br>> > > Von: <a href="mailto:kolab-users-bounces@kolab.org">kolab-users-bounces@kolab.org</a><br>> > > [mailto:<a href="mailto:kolab-users-bounces@kolab.org">
kolab-users-bounces@kolab.org</a>] Im Auftrag von Alain Spineux<br>> > > Gesendet: Samstag, 2. Juni 2007 20:51<br>> > > An: Kolab development coordination<br>> > > Cc: <a href="mailto:kolab-users@kolab.org">
kolab-users@kolab.org</a><br>> > > Betreff: Re: [Kolab-devel] Kolab2 V2.1.0 Final SMTP over SSL ><br>> > > problemtalkingto server private/kolabpolicy: Socket operation<br>> > > onnon-socket<br>
> > ><br>> > ><br>> > > Are you using SOLARIS ?<br>> > ><br>> > ><br>> > > On 6/2/07, ComCept Net GmbH Andrea Soliva <<a href="mailto:soliva@comcept.ch">soliva@comcept.ch
</a>> wrote:<br>> > ><br>> > > Hi Alain<br>> > ><br>> > > I checked the /kolab/var/resmgr/resmgr.log. No errors at all also not<br>> > > in the time of test. The local connection with the untouched
<br>> > > useraccount and with the absolut same configuration worked. Here as<br>> > > mentioned the logs<br>> ><br>> > from<br>> ><br>> > > this test/connection:<br>> > >
<br>> > > LOCAL TEST WITH SAME ACCOUNT:<br>> > ><br>> > > Jun 02 13:12:04 kolab2 <info> postfix/smtpd[9033]: connect from<br>> > > PCG-GRT716S[xxx.xxx.xxx.x]<br>> > > Jun 02 13:12:04 kolab2 <info> postfix/smtpd[9033]: setting up TLS
<br>> > > connection from PCG-GRT716S[xxx.xxx.xxx.x]<br>> > > Jun 02 13:12:04 kolab2 <info> postfix/smtpd[9033]: TLS connection<br>> > > established from PCG-GRT716S[xxx.xxx.xxx.x]: TLSv1 with cipher RC
<br>> > > 4-MD5 (128/128 bits)<br>> > > Jun 02 13:12:04 kolab2 <info> postfix/smtpd[9033]: 808249D1F:<br>> > > client=PCG-GRT716S[xxx.xxx.xxx.x], sasl_method=LOGIN, sasl_username=<br>> > > <mailto:
<a href="mailto:domenica@wojnowski.ch">domenica@wojnowski.ch</a>> <a href="mailto:domenica@wojnowski.ch">domenica@wojnowski.ch</a><br>> > > Jun 02 13:12:04 kolab2 <info> postfix/cleanup[8895]: 808249D1F:
<br>> > > message-id=<<a href="mailto:20070602111204.808249D1F@kolab2.comcept.ch">20070602111204.808249D1F@kolab2.comcept.ch</a><br>> > > <mailto:<a href="mailto:20070602111204.808249D1F@kolab2.comcept.ch">
20070602111204.808249D1F@kolab2.comcept.ch</a>> ><br>> > > Jun 02 13:12:04 kolab2 <info> postfix/qmgr[7038]: 808249D1F: from=<<br>> > > <mailto:<a href="mailto:domenica@wojnowski.ch">domenica@wojnowski.ch
</a>> <a href="mailto:domenica@wojnowski.ch">domenica@wojnowski.ch</a>>, size=649,<br>> > > nrcpt=1 (queue active)<br>> > > Jun 02 13:12:04 kolab2 <info> postfix/smtpd[9033]: disconnect from
<br>> > > PCG-GRT716S[xxx.xxx.xxx.x]<br>> > > Jun 02 13:12:04 kolab2 <info> postfix/smtpd[8898]: connect from<br>> > > localhost[<a href="http://127.0.0.1">127.0.0.1</a>]<br>> > > Jun 02 13:12:04 kolab2 <info> postfix/smtpd[8898]: C63539DE2:
<br>> > > client=localhost[<a href="http://127.0.0.1">127.0.0.1</a>]<br>> > > Jun 02 13:12:04 kolab2 <info> postfix/cleanup[8899]: C63539DE2:<br>> > > message-id=<<a href="mailto:20070602111204.808249D1F@kolab2.comcept.ch">
20070602111204.808249D1F@kolab2.comcept.ch</a>><br>> > > Jun 02 13:12:04 kolab2 <info> postfix/qmgr[7038]: C63539DE2: from=<<br>> > > <mailto:<a href="mailto:domenica@wojnowski.ch">domenica@wojnowski.ch
</a>> <a href="mailto:domenica@wojnowski.ch">domenica@wojnowski.ch</a>>, size=824,<br>> > > nrcpt=1 (queue active)<br>> > > Jun 02 13:12:04 kolab2 <info> postfix/smtpd[8898]: disconnect from
<br>> > > localhost[<a href="http://127.0.0.1">127.0.0.1</a>]<br>> > > Jun 02 13:12:04 kolab2 <info> postfix/pipe[8896]: 808249D1F: to=<<br>> > > <mailto:<a href="mailto:domenica@wojnowski.ch">
domenica@wojnowski.ch</a>> <a href="mailto:domenica@wojnowski.ch">domenica@wojnowski.ch</a>>,<br>> > > relay=kolabfilter, delay=0, status=sent (kola<br>> > > <a href="http://b2.comcept.ch">b2.comcept.ch
</a>)<br>> > > Jun 02 13:12:04 kolab2 <info> postfix/qmgr[7038]: 808249D1F: removed<br>> > ><br>> > > TEST WITH "NONE FIX IP FROM INTERNET" ENTERED IN TRUSTED NETWORK:<br>> > >
<br>> > > Jun 02 13:23:23 kolab2 <info> postfix/smtpd[10675]: connect from<br>> > > 100-132.3-85.cust.bluewin.ch[<a href="http://85.3.132.100">85.3.132.100</a>]<br>> > > Jun 02 13:23:23 kolab2 <info> postfix/smtpd[10675]: setting up TLS
<br>> > > connection from 100-132.3-85.cust.bluewin.ch[<a href="http://85.3.132.100">85.3.132.100</a>]<br>> > > Jun 02 13:23:23 kolab2 <info> postfix/smtpd[10675]: TLS connection<br>> > > established from
100-132.3-85.cust.bluewin.ch[<a href="http://85.3.132.100">85.3.132.100</a>]: TLSv<br>> > > 1 with cipher RC4-MD5 (128/128 bits)<br>> > > Jun 02 13:23:23 kolab2 <info> postfix/smtpd[10675]: 8A8E7A179:
<br>> > > client=100-132.3-85.cust.bluewin.ch[<a href="http://85.3.132.100">85.3.132.100</a>], sasl_method=LOGIN,<br>> > > sasl_username=<a href="mailto:domenica@wojnowski.ch">domenica@wojnowski.ch</a><br>
> > > Jun 02 13:23:24 kolab2 <info> postfix/cleanup[10447]: 8A8E7A179:<br>> > > message-id=<000001c7a508$5d781260$2101a8c0@Amilo><br>> > > Jun 02 13:23:24 kolab2 <info> postfix/qmgr[10181]: 8A8E7A179:
<br>> > > from=<<a href="mailto:domenica@wojnowski.ch">domenica@wojnowski.ch</a>>, size=2172, nrcpt=1 (queue active)<br>> > > Jun 02 13:23:24 kolab2 <info> postfix/smtpd[10450]: connect from<br>
> > > localhost[<a href="http://127.0.0.1">127.0.0.1</a>]<br>> > > Jun 02 13:23:24 kolab2 <info> postfix/smtpd[10450]: 69BC9A17B:<br>> > > client=localhost[<a href="http://127.0.0.1">127.0.0.1
</a>]<br>> > > Jun 02 13:23:24 kolab2 <info> postfix/cleanup[10451]: 69BC9A17B:<br>> > > message-id=<000001c7a508$5d781260$2101a8c0@Amilo><br>> > > Jun 02 13:23:24 kolab2 <info> postfix/qmgr[10181]: 69BC9A17B:
<br>> > > from=<<a href="mailto:domenica@wojnowski.ch">domenica@wojnowski.ch</a>>, size=2345, nrcpt=1 (queue active)<br>> > > Jun 02 13:23:24 kolab2 <info> postfix/smtpd[10450]: disconnect from
<br>> > > localhost[<a href="http://127.0.0.1">127.0.0.1</a>]<br>> > > Jun 02 13:23:24 kolab2 <info> postfix/pipe[10448]: 8A8E7A179:<br>> > > to=<<a href="mailto:soliva@comcept.ch">soliva@comcept.ch
</a>>, relay=kolabfilter, delay=1, status=sent (kolab<br>> > > <a href="http://2.comcept.ch">2.comcept.ch</a>)<br>> > ><br>> > > You see that is 100% a confirmation that actually all is working fine
<br>> > > but "only" within local trusted network or if the IP is configured as<br>> > > trusted network even this solution is not visible (because it is not a<br>> > > fix IP).<br>> > >
<br>> > > What is here wrong.....except within the postfix.log I have no errors<br>> > > meaning I controlled all logs (really all :-).<br>> > ><br>> > > Any help and explanation really appriciated.
<br>> > ><br>> > > Many thanks<br>> > ><br>> > > Andrea<br>> > ><br>> > ><br>> > ><br>> > ><br>> > > _____<br>> > ><br>> > > Von:
<a href="mailto:kolab-devel-bounces@kolab.org">kolab-devel-bounces@kolab.org</a><br>> > > [mailto:<a href="mailto:kolab-devel-bounces@kolab.org">kolab-devel-bounces@kolab.org</a>] Im Auftrag von Alain Spineux<br>
> > > Gesendet: Samstag, 2. Juni 2007 18:10<br>> > > An: Kolab development coordination<br>> > > Cc: <a href="mailto:kolab-users@kolab.org">kolab-users@kolab.org</a><br>> > > Betreff: Re: [Kolab-devel] Kolab2
V2.1.0 Final SMTP over SSL ><br>> > > problemtalking to server private/kolabpolicy: Socket operation<br>> ><br>> > onnon-socket<br>> ><br>> > > You should look about error messages from the kolab policy.
<br>> > > Maybe thei are in /kolab/var/resmgr/resmgr.log (not sure)<br>> > ><br>> > > Also can you give the log a the successful connection you got, when<br>> > > connected locally ?<br>
> > ><br>> > > Regards.<br>> > ><br>> > > Alain<br>> > ><br>> > ><br>> > ><br>> > ><br>> > ><br>> > > On 6/2/07, ComCept Net GmbH Andrea Soliva <
<a href="mailto:soliva@comcept.ch">soliva@comcept.ch</a>> wrote:<br>> > ><br>> > > Hi all<br>> > ><br>> > > I tested further with V2.1.0 Final and up to know it seems to work all<br>
> ><br>> > fine<br>> ><br>> > > (internal trusted networks) with one exception:<br>> > ><br>> > > I'm working with Toltec and the E-Mail account is configured with Port<br>
> > > POP over SSL TCP 995 as SMTP over SSL TCP 465. All is working fine<br>> > > without problems.<br>> > ><br>> > > The next test I did is I added a new domain wojnowski.ch and a user.
<br>> > > This user is not in my trusted network meaning this user makes requests<br>> > > somewhere from the internet. On the firewall I opened:<br>> > ><br>> > > POP over SSL TCP 995 as SMTP over SSL TCP 465
<br>> > ><br>> > > The Email account from the user is also configured with the specific<br>> > > ports as the certificat is installed. The issue we have is following:<br>> > ><br>> > > --> The user can fetch his emails over POP over SSL TCP 995 without
<br>> > > problems. As soon as he tries to send a mail over SMTP over SSL TCP 465<br>> > > it would not work:<br>> > ><br>> > > ==> /kolab/var/postfix/log/postfix.log <==<br>> > > Jun 02 12:24:55 kolab2 <info> postfix/smtpd[2815]: connect from
<br>> > > 147-164.3-85.cust.bluewin.ch[<a href="http://85.3.164.147">85.3.164.147</a>]<br>> > > Jun 02 12:24:55 kolab2 <info> postfix/smtpd[2815]: setting up TLS<br>> > > connection from 147-164.3-85.cust.bluewin.ch
[ <a href="http://85.3.164.147">85.3.164.147</a><br>> > > <<a href="http://85.3.164.147">http://85.3.164.147</a>> ] Jun 02 12:24:55 kolab2 <info><br>> > > postfix/smtpd[2815]: TLS connection<br>
> > > established from 147-164.3-85.cust.bluewin.ch[<a href="http://85.3.164.147">85.3.164.147</a>]: TLSv1 with<br>> > > cipher RC4-MD5 (128/128 bits)<br>> > > Jun 02 12:24:56 kolab2 <warning> postfix/smtpd[2815]: warning: connect
<br>> > > to private/kolabpolicy: Socket operation on non-socket<br>> > > Jun 02 12:24:56 kolab2 <warning> postfix/smtpd[2815]: warning: problem<br>> > > talking to server private/kolabpolicy: Socket operation on non-socket
<br>> > > Jun 02 12:24:57 kolab2 <warning> postfix/smtpd[2815]: warning: connect<br>> > > to private/kolabpolicy: Socket operation on non-socket<br>> > > Jun 02 12:24:57 kolab2 <warning> postfix/smtpd[2815]: warning: problem
<br>> > > talking to server private/kolabpolicy: Socket operation on non-socket<br>> > > Jun 02 12:24:57 kolab2 <info> postfix/smtpd[2815]: NOQUEUE: reject:<br>> > > RCPT from 147-164.3-85.cust.bluewin.ch
[ <a href="http://85.3.164.147">85.3.164.147</a><br>> > > <<a href="http://85.3.164.147">http://85.3.164.147</a>> ]: 450 Server configuration<br>> > > problem; from=<<a href="mailto:domenica@wojnowski.ch">
domenica@wojnowski.ch</a>> to=< <a href="mailto:soliva@comcept.ch">soliva@comcept.ch</a><br>> > > <mailto:<a href="mailto:soliva@comcept.ch">soliva@comcept.ch</a>> > proto=ESMTP<br>> > > helo=<Amilo>
<br>> > > Jun 02 12:25:00 kolab2 <info> postfix/smtpd[2815]: disconnect from<br>> > > 147-164.3-85.cust.bluewin.ch[<a href="http://85.3.164.147">85.3.164.147</a>]<br>> > ><br>> > >
<br>> > > As a test I configured the account in my local network (trusted<br>> > > network) with the same config as the user has. It works without<br>> > > problems. If I look to the error or warnings it seems to me that the
<br>> > > kolabpolicy does not<br>> ><br>> > allow<br>> ><br>> > > this even the users is authenticating. The config over the manager<br>> > > interface<br>> > ><br>> > > looks like following:
<br>> > ><br>> > > All services available except HTTP FreeBusy Service (Legacy) and POP3<br>> > > Service<br>> > ><br>> > > Quota not active<br>> > ><br>> > > Freebusy not set
<br>> > ><br>> > > Priviliged networks set to <a href="http://127.0.0.0/8">127.0.0.0/8</a>, xxx.xxx.xxx.0/24,<br>> > > xxx.xxx.xxx.0/24,, xxx.xxx.xxx.0/24<br>> > ><br>> > > No Smart Relay Host set
<br>> > ><br>> > > Accept Internet Email not active<br>> > ><br>> > > Domains both domains are visible<br>> > ><br>> > > Mail Filter settings set to "Reject the message with the except if it
<br>> > > originates"<br>> > ><br>> > ><br>> > > Temporarly I entered the IP from the user "<a href="http://85.3.164.147">85.3.164.147</a>" to the trusted<br>> > > network config and it worked fine. This user has now fix IP from this
<br>> ><br>> > point<br>> ><br>> > > of view it is not visible to use such a config. At the moment I'm a<br>> > > little bit confiused meaning is this configuration I would like to have
<br>> > > not visible meaning having user travelling around the world and using<br>> > > kolab2 for sending<br>> > ><br>> > > emails?<br>> > ><br>> > > Can somebody point me in the correct direction or is it something which
<br>> > > should work and does not in V2.1.0 (Bug?).<br>> > ><br>> > > For any answer many thanks in advanced.<br>> > ><br>> > > Kind regards<br>> > ><br>> > > Andrea
<br>> > ><br>> > > _______________________________________________<br>> > > Kolab-devel mailing list<br>> > > <a href="mailto:Kolab-devel@kolab.org">Kolab-devel@kolab.org</a><br>> > >
<a href="https://kolab.org/mailman/listinfo/kolab-devel">https://kolab.org/mailman/listinfo/kolab-devel</a><br>> > > <<a href="https://kolab.org/mailman/listinfo/kolab-devel">https://kolab.org/mailman/listinfo/kolab-devel
</a>><br>> > ><br>> > ><br>> > ><br>> > ><br>> > ><br>> > > --<br>> > > --<br>> > > Alain Spineux<br>> > > aspineux gmail com<br>> > > May the sources be with you
<br>> > ><br>> > ><br>> > > _______________________________________________<br>> > > Kolab-devel mailing list<br>> > > <a href="mailto:Kolab-devel@kolab.org">Kolab-devel@kolab.org
</a><br>> > > <a href="https://kolab.org/mailman/listinfo/kolab-devel">https://kolab.org/mailman/listinfo/kolab-devel</a><br>> ><br>> > There is a mix of tls and ssl in you above message. We have experienced
<br>> > that<br>> > tls often doesn't work from the outside especially from hotels or certain<br>> > isp's. They must block it. try ssl<br><br>--<br>Best regards<br>Thomas Spuhler<br><br>_______________________________________________
<br>Kolab-users mailing list<br><a href="mailto:Kolab-users@kolab.org">Kolab-users@kolab.org</a><br><a href="https://kolab.org/mailman/listinfo/kolab-users">https://kolab.org/mailman/listinfo/kolab-users</a><br></blockquote>
</div><br><br clear="all"><br>-- <br>--<br>Alain Spineux<br>aspineux gmail com<br>May the sources be with you<br>