El 23/8/22 a les 14:54, Nicolas Höft (nico...@hoeft.de) ha escrit:
Could be even if localhost resolves to 127.0.0.1
$ host localhost
localhost has address 127.0.0.1
$ nslookup localhost
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
Name: localhost
Address: 127.0.0.1
but now that I'm looking at the tcpdump capture closely I see that it is
trying to connect to ::1 (wireshark fooled me since it replaced the ::1
with localhost).
Bye
Hi Luca, > > is it be possible that localhost resolved to the ipv6 localhost,
ie. ::1
and your imap proxy is not listening on ipv6?
The ipv6 support is new in sogo 5.7.1
Nicolas
Am 23.08.22 um 10:10 schrieb Luca Olivetti (l...@wetron.es):
El 23/8/22 a les 9:32, Luca Olivetti (l...@wetron.es) ha escrit:
It seems the problem is due to imapproxy (I tried to remove cas
authentication and even with the built-in auth it couldn't login to
the authentication server). If I connect directly to the imap server
then it works.
that should be "it couldn't login to the imap server"
In any case the only thing that's been upgraded is SOGo.
I traced the connection to the imapproxy port with tcpdump and I could
see that for some reason SOGo cannot manage to connect to "localhost",
changing it to "127.0.0.1" made it work again
i.e. I changed
SOGoIMAPServer = imap://localhost:1143;
to
SOGoIMAPServer = imap://127.0.0.1:1143;
For the record, using "localhost" SOGo replied with RST,ACK to every
SYN coming from the proxy.
Now, if only I could find a similar easy fix for
https://www.mail-archive.com/users%40sogo.nu/msg31396.html ....
Bye
--
Luca Olivetti
Wetron Automation Technology http://www.wetron.es/
Tel. +34 93 5883004 (Ext.3010) Fax +34 93 5883007
