>> When I run courier-imapd-ssl on port 993, I can set imapproxy's >> listen_port and server_port to 993. > > Doing that doesn't make any sense, of course: Clients connecting to > listen_port (where imapproxy will listen) will be proxied to > server_port (where your imapd should listen). > >> When I run courier-imapd on port >> 143, I can't set imapproxy's listen_port and server_port to 143. I >> must set listen_port to another port or I get: >> >> main(): bind() failed: Address already in use >> >> Why does this work with port 993 but not 143? > > It shouldn't work in both cases. Either you're mistaken and it doesn't > actually work in the 993 case either, or possibly something to do with > how your courier imapd is being started in your environment (tcpd), > -peter
Got it, do people find it's better to make imapd accept client connections on the standard 143 or for imapproxy to do so? Or maybe there is no preference? - Grant ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ----- squirrelmail-imapproxy mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: [email protected] List archives: http://news.gmane.org/gmane.mail.squirrelmail.imapproxy List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-imapproxy
