On Mon, 6 Mar 2006, BuildSmart wrote:
I have an app set up that sends the password to retrieve mail to be read (no clue what format, only that it works), when I build with the nopwd option I can no longer retrieve e-mail.
Do you know if that application uses SSL? What is the application?
When I try "telnet loalhost 993" it refuses connection (obviously not set to watch this port).
You can't telnet to an SSL port. You have to use an SSL-enabled program such as the s_client in OpenSSL.
I have no issues with using SSL options to hide plain-text passowrds but pam_mysql expects the password to be plain-text when it processes it.
SSL has nothing to do with your password validation. SSL encrypts the entire session, not just SSL.
Forcing only SSL connections for mail is probably a good idea however the instructions for making it work are unclear to me, I understand drag and drop and it works but if I build with SSLTYPE=unix it's no longer drag and drop and I couldn't find simple explanations in the documentation to make it work.
Did you set up separate xinetd startup files for both the IMAP port (port 143) and the SSL IMAP port (port 993)? You have to do that.
xinetd is a completely different program, which I neither develop nor maintain. What's more, there are different ways that xinetd is set up on different systems. You have to consult the xinetd documentation on your system for how this should be done.
Aside from the port change, what else do I need to change to get mail working again?
All you need to do is to set up the appropriate configuration files *for your operating system* that will start imapd on port 143 and 993 and ipop3d on port 110 and 995. That's four separate server listen/startup rules that you have to set up.
There are too many variations for me to offer a "one shoe fits all". The documentation tried to do such for inetd, but even inetd has many variations. xinetd also has variations.
What's more, if you use Mac OS X, you may have to use a launchd configuration file instead of xinetd. xinetd doesn't seem to work reliably on Mac OS X. I don't know much about launchd, other than the fact that it uses XML (shudder) and follows Apple's typical contempt of standards.
Your best bet is to consult your system's documentation and/or the vendor of your system; alternatively, ask a expert on your system type.
imapd and ipop3d do no TCP I/O on their own. All their I/O is via stdio; thus they are always invoked by the system's TCP listener (inetd or xinetd or launchd).
-- Mark -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list [email protected] https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
