Brian Kendig wrote: > Thank you for the help. Removing -Wno-pointer-sign from > src/osdep/unix/Makefile allowed imapd-2006f to compile with gcc 3.3 on > Mac OS X 10.3.9. > > Compiling with "make oxp" resulted in a binary which wouldn't let my > mail client (Mac OS X Mail) authenticate, but compiling with "make oxp > SSLTYPE=none" solved that problem, so now I'm good to go! Thank you for > the tip!
If your client does use authentication there shouldn't be any problem, you just need to install a certificate on the server and set the client to use TLS or SSL. > Though, using that option resulted in my being warned that the binary > was being built "in NON-COMPLIANCE with RFC 3501 security requirements" > because "TLS/SSL encryption is NOT supported and unencrypted plaintext > passwords are permitted". It tells me to build with "SSLTYPE=nopwd" to > overcome this. Is "SSLTYPE=nopwd" a safe option to use? It sounds like > it removes the need for a password, which wouldn't be good...? What > does that option do, exactly - should I use it? Read docs/SSLBUILD. I prefer to use "SSLTYPE=unix" to allow clients that need plaintext authentication as well as those that do use SSL and then authenticate. -- René Berber _______________________________________________ Imap-uw mailing list [email protected] https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
