Greets, Many smooth months running Courier-IMAP. No complaints. I am grateful!
The problem: pop3d on port 110 is being encrypted. It needs to be Unencrypted. Until now, we've been running only pop3d-ssl and imapd-ssl (and imapd only on localhost), but we need to start offering pop3d to the outside world. I remember having the same problem when I started running imapd on localhost -- it was being encrypted even though I hadn't told it to - or so I thought - I hadn't realized that setting IMAP_TLS_REQUIRED=1 also had an effect on imapd. So, I have made sure that POP3_TLS_REQUIRED=0 but still no luck. My personal mail client of course barfs, telling me something to the effect of "connection was interrupted". A raw telnet session to port 110 shows that it is most definitely encrypted. What other setting could be doing this??? Many thanks for any advice! Cheers! PS - Other obvious settings: SSLPORT is set to 995, regular PORT for pop is set to 110, both ADDRESSES are 0, I have stopped all auth services and imap/pop daemons and started them again multiple times.... Oh, and yes, pop3d-ssl on 995 works wonderfully (has for some time). ------------------------------------------------------- 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
