On Dec 23, 2003, at 6:44 AM, Andrea Riela wrote:
QUESTION
My question now is: how could I say Courier, use vchkpw_ssl and not
vchkpw? It's possible to change the path to vchkpw in the Courier-Imap
config, or I've to change the vchkpw in vchkpw_nossl and my
/var/qmail/supervise/qmail-pop3d/run script?
If you're using courier, it will be harder to accomplish your goals.
Courier-IMAP links libvpopmail in instead of using vchkpw. So, like
Jeremy explained in another email, you'll have to do the following:
Configure, make and install vpopmail without roaming user support.
Configure, make and install courier-imap. Rename this copy to
something like courier-imap-noroaming.
`make clean` your vpopmail source, reconfigure, make and install
without roaming user support.
`make clean` your courier-imap source, reconfigure, make and install.
Now, heavily edit /usr/lib/courier-imap/libexec/imapd.rc so it starts
the noroaming version for non-SSL connections, and the other version
for SSL connections. It won't be easy -- you're going to have to do a
lot of tweaking to that RC file. It might be easier to switch to
another IMAP server (like Binc), but I really don't know.
You may want to reconsider your reasons for setting this policy. It
will be difficult to maintain (if you ever upgrade vpopmail, you'll
have to recompile it and courier twice). It will probably lead to more
support calls as well. Consider SMTP AUTH with CRAM-MD5 (which doesn't
work at the moment, but should hopefully once I apply a patch to the
last release).
--
Tom Collins - [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/
