Problems setting up and properly compiling imap-uw.
Steven Lake
steven.lake at corecomm.com
Sun Jul 30 15:58:15 UTC 2006
>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:
[root at mail 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
More information about the freebsd-questions
mailing list