Re: [SM-imapproxy] listen_port=server_port: 993 works, 143 doesn't

[Grant <ema...@gm...>]

>> 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