Hi, > The problem turned out to be a documentation problem. cyrus knows about > services "tcp", "tcp4" and "tcp6". "tcp6" means IPv6 only and not both > IPv4 and IPv6 as the submitter expected. Changing the service from "tcp6" > to "tcp" fixed the problem. The current version of cyrus IMAP in Debian > has a better documentation in the man page.
Thanks, yes, that solved the problem. I"ve been out of office for some days now, so I just could try it now, but with proto=tcp it seems to work fine. cyrusmaster binds to both ipv6 and ipv4 stack. Just one more question: why not handle ipv4 also via ipv6 stack (via 6to4 adresses) like most other software does? Thanks, Michael
