I'm currently using SOGo 1.0.4 on Debian Lenny with imapproxy. Works
fine. I'm building a new server with Debian Lenny to run the latest
nightly of SOGo (1.2.2ish). Everything is working fine except SOGo won't
work with imapproxy (1.2.6-5). I have imapproxy running on port 144 and
I know it is working fine because I can connect thunderbird to the proxy
port and I can get my mail, etc. But when I use the line:
SOGoIMAPServer = "localhost:144";
when I login to SOGo via the web, it just hangs showing the mail. I'm
done some snooping on port 143 and 144. For some reason when I have sogo
use port 144 the only traffic I see is 5 packets from sogo to port 144.
If I run:
tcpflow -c -i lo port 144 or port 143
I only get one line:
127.000.000.001.00144-127.000.000.001.39757: * OK [CAPABILITY IMAP4rev1
LITERAL+ LOGIN-REFERRALS ID ENABLE Dovecot ready.
for some reason it seems that SOGo sees this header and doesn't try to
login, etc. Also, when I have sogo configured to connect to port 143
(dovecot directly), I see lots of traffic, but no login. Is there some
cacheing or other authentication to the dovecot imap server that
imapproxy is getting in the way of? I believe I have the same setup as I
do on the SOGo 1.0.4 box where imapproxy is working, but clearly
something is different.
Thanks,
Ben
--
[email protected]
https://inverse.ca/sogo/lists
