On 13-04-10 1:59 PM, Vilius Baušys wrote:
I believe there is some misconfiguration in sogo. But cannot find out what I did wrong. How can I debug sogo connection to sieve?
Try to sniff the connection using either tcpdump -X or tcpflow -c -i lo port 4190 that should give a good insight. -- Jean Raby jr...@inverse.ca :: +1.514.447.4918 (x120) :: www.inverse.caInverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org)
-- users@sogo.nu https://inverse.ca/sogo/lists
