Dear List,

I am finally going to swallow my pride and ask for help...

I've tried re-reading the docs + mailing lists and reinstalling over and
over again, but I keep having the same problem. I'm sure there is something
simple that I must be doing wrong.


I think my problem is related to SSL. When I try running the following test,
I get:

[EMAIL PROTECTED] conf]# openssl s_client -connect localhost:993 -crlf
CONNECTED(00000003)
write:errno=104


My bincimap.pem file looks like [1] below, and I've tried this a few other
ways as well.
And my bincimap.conf file looks like [2] below.

I think that the following is related...

In my bincimap-ssl log file, all the entries look like:

 tcpserver: fatal: unable to bind: address already used

When I check via ps, I find:

  root      5828  0.0  0.0     0    0 ?        Z    14:31   0:00 [tcpserver]
<defunct>

Whenever I try to kill the process, another one just pops up until I do:

  svc -d /service/bincimaps/



Any help would be VERY MUCH appreciated!!!

Dave








*****[1] bincimap.pem

-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,1C23253E9E96C778

blablabla
-----END RSA PRIVATE KEY-----

-----BEGIN CERTIFICATE REQUEST-----
blablabla
-----END CERTIFICATE REQUEST-----



*****[2] bincimap.conf

Authentication {
    allow plain auth in non ssl = "no",
    auth penalty = 4,
    disable starttls = "no"
}

Security {
    jail path = "/var/qmail/supervise/bincimap",
    jail user = "nobody",
    jail group = "nobody"
}

Log {
    type = "multilog",
    environment ip variable = "TCPREMOTEIP"
}

Mailbox {
    depot = "IMAPdir",
    type = "Maildir",
    path = "Maildir",
    auto create inbox = "yes",
    auto subscribe mailboxes = "INBOX",
    umask = "077"
}

Session {
    idle timeout = 1860,
    auth timeout = 60,
    transfer timeout = 1200,
    transfer buffer size = 1024
}

SSL {
    pem file = "/var/qmail/control/bincimap.pem",
    ca file = "",
    cipher list = "!ADH:RC4+RSA:HIGH:MEDIUM:LOW:EXP:+SSLv2:+EXP",
    verify peer = "no"
}


Reply via email to