Proxyd connecting to backend on 143, not 993
criggins at gmail.com
Fri Oct 1 22:06:44 EDT 2010
Thanks for the confirmation! I figured this out earlier this afternoon, and should've posted the solution. The answer was masked because I had specified LOGIN as a mechanism, and not PLAIN, so that when the backend_connect happened, I got a SIGSEV.
On Oct 1, 2010, at 9:31 PM, Matt Selsky wrote:
> On Thu, 30 Sep 2010, Chris Riggins wrote:
>> I'm running Cyrus IMAP 2.3.16, trying to get a murder working, but the "proxyd -s" daemon on the frontend isn't connecting to my
>> backend on the secure port. How does one make that happen? An strace on the proxyd process shows that it never even attempts the IMAPS
> Your backends should be listening on port 143. proxyd is meant to listen on 143 and 993 and forward connections to the backends on 143. proxyd will use TLS to secure the connection.
More information about the Info-cyrus