Re: Problems setting up and properly compiling imap-uw.
Steven Lake wrote: Looking for some help in this rather baffling issue. I'm trying to get a new mail server setup with webmail capabilities (via squirrelmail) and I'm hitting a little snag. Squirrelmail says that the imap server won't accept plain text passwords, yet I compiled from source for plaintext using make -E WITHOUT_SSL and I also tried make -E WITH_SSL_AND_PLAINTEXT. Neither worked. Squirrelmail still complains saying that the imap server doesn't allow plaintext passwords. Any idea what I can do to fix this? Is it a config file I have to change or something? I don't want nor need to do ssl for logins as this will be located on a secure lan, so I'd like to avoid all the crazy stuff that comes with doing an SSL setup. Any help is appreciated. You're forgetting to assign values to your variables. # make -E WITHOUT_SSL=yes or # make -E WITH_SSL_AND_PLAINTEXT=yes Cheers, Mikhail. -- Mikhail Goriachev Webanoide Telephone: +61 (0)3 62252501 Mobile Phone: +61 (0)4 38255158 E-Mail: [EMAIL PROTECTED] Web: http://www.webanoide.org PGP Key ID: 0x4E148A3B PGP Key Fingerprint: D96B 7C14 79A5 8824 B99D 9562 F50E 2F5D 4E14 8A3B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems setting up and properly compiling imap-uw.
You're forgetting to assign values to your variables. # make -E WITHOUT_SSL=yes or # make -E WITH_SSL_AND_PLAINTEXT=yes Ok, tried that and I got this at compile time: [EMAIL PROTECTED] imap-uw]# make -E WITH_SSL_AND_PLAINTEXT=yes === Vulnerability check disabled, database not found === Extracting for imap-uw-2004g_1,1 = MD5 Checksum OK for imap-2004g.tar.Z. = SHA256 Checksum OK for imap-2004g.tar.Z. === Patching for imap-uw-2004g_1,1 === Applying FreeBSD patches for imap-uw-2004g_1,1 === imap-uw-2004g_1,1 depends on shared library: c-client4.8 - found === Configuring for imap-uw-2004g_1,1 === Building for imap-uw-2004g_1,1 Your imap-uw port matches the version of your cclient port. Fine. SSL check passed. We want SSL support, and cclient has it. Good. make sslunix.nopwd + + Building in full compliance with RFC 3501 security + requirements: ++ TLS/SSL encryption is supported ++ Unencrypted plaintext passwords are prohibited + Followed below here by the typical compile stuff. When I run the config test script I still get this error: ERROR: Your server doesn't allow plaintext logins. Try enabling another authentication mechanism like CRAM-MD5, DIGEST-MD5 or TLS-encryption in the SquirrelMail configuration. Am I still missing something, or didn't the compile go right? --- - Steve Lake --- Mutton is no fun unless it's still kicking - Hax the Acker ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems setting up and properly compiling imap-uw.
Steven Lake wrote: You're forgetting to assign values to your variables. # make -E WITHOUT_SSL=yes or # make -E WITH_SSL_AND_PLAINTEXT=yes Ok, tried that and I got this at compile time: [EMAIL PROTECTED] imap-uw]# make -E WITH_SSL_AND_PLAINTEXT=yes === Vulnerability check disabled, database not found === Extracting for imap-uw-2004g_1,1 = MD5 Checksum OK for imap-2004g.tar.Z. = SHA256 Checksum OK for imap-2004g.tar.Z. === Patching for imap-uw-2004g_1,1 === Applying FreeBSD patches for imap-uw-2004g_1,1 === imap-uw-2004g_1,1 depends on shared library: c-client4.8 - found === Configuring for imap-uw-2004g_1,1 === Building for imap-uw-2004g_1,1 Your imap-uw port matches the version of your cclient port. Fine. SSL check passed. We want SSL support, and cclient has it. Good. make sslunix.nopwd + + Building in full compliance with RFC 3501 security + requirements: ++ TLS/SSL encryption is supported ++ Unencrypted plaintext passwords are prohibited + Followed below here by the typical compile stuff. When I run the config test script I still get this error: ERROR: Your server doesn't allow plaintext logins. Try enabling another authentication mechanism like CRAM-MD5, DIGEST-MD5 or TLS-encryption in the SquirrelMail configuration. Am I still missing something, or didn't the compile go right? My memory is a bit rusty, but you also have to (re)compile cclient[1] with the same knob. If I may ask, out of curiosity. Why imap-uw and not something else that supports maildir format instead of mbox? For instance, courier-imap or dovecot are far better options. Cheers, Mikhail. [1] - /usr/ports/mail/cclient -- Mikhail Goriachev Webanoide Telephone: +61 (0)3 62252501 Mobile Phone: +61 (0)4 38255158 E-Mail: [EMAIL PROTECTED] Web: http://www.webanoide.org PGP Key ID: 0x4E148A3B PGP Key Fingerprint: D96B 7C14 79A5 8824 B99D 9562 F50E 2F5D 4E14 8A3B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems setting up and properly compiling imap-uw.
If I may ask, out of curiosity. Why imap-uw and not something else that supports maildir format instead of mbox? For instance, courier-imap or dovecot are far better options. Well, I don't normally work with Imap, so I was experimenting to find out which client would work best for me. This just happened to be the first one I picked. Courier would have been next. I may still go with that one. Steven Lake Business Support Representative CoreComm Business Services Contact Number: 1-877-557-2724 Direct Line: 1-517-664-8176 Duct Tape takes over where skill leaves off - Larry the Cucumber from Veggie Tales. But I was only trying to improve it! - Dago - Monk: The Comic Strip (www.monkcomic.com) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
