> On Sun, Feb 23, 2003 at 10:24:23AM -0800, Jeff Shevlen wrote: > > Thanks Laurence, > > > > No dice though. > > > > > > > > ADDRESS=192.168.0.0 > > > > > > Is the address correct? > > > > ... cleverly faked for the mailing list. > > 192.168.0.1 would have been cleverer. > > Just to be clear, this is the address of the IMAP server itself, not the > netblock of the clients who are using it. Normally you would just leave this > at 0.0.0.0 (or 0), which binds to all interfaces. You'd only change it if > your server has more than one network port, *and* you only want it to accept > connections on one of its IP addresses. >
I have other services running on this machine, each on a different interface. The imap server has it's own address. Also, as the logs seem to indicate, a conversation is started: imapd: couriertls: accept: error:140890B2:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:no certificate returned imapd: couriertls: accept: error:1408F071:SSL routines:SSL3_GET_RECORD:bad mac decode F ... so I'm not sure that my network is the issue. That said, and other ideas? Is there anything else I'm missing? FTR, I've gotten Postfix with TLS up and running with Opera 7 as a client, so half of my mojo is working. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
