BuildSmart wrote: > > On Mar 6, 2006, at 24:49 , Mark Crispin wrote: > >> On Mon, 6 Mar 2006, BuildSmart wrote: >>> What I'm trying to achieve is true virtual users, all required >>> authentication is currently done with mysql, what I'd like to avoid >>> is adding 9263 users to /etc/passwd and creating 9263 homes. >> >> By design, UW imapd uses UNIX users and the UNIX security model. >> Some other IMAP implementations (e.g., Cyrus from CMU) has its own >> user scheme and security model. So, Cyrus may be more suitable for >> your purposes. >> >> However, I don't quite understand the cost of adding 9263 users to >> /etc/passwd -- you have to define the users someplace. >> >>> What occurs if they don't have home directories??? >> >> IMAP has secondary (non-INBOX) mailboxes. So the lack of a home >> directory means this important capability of IMAP isn't usable. >> >> For that reason, I don't quite understand the cost of creating 9263 >> homes either -- you have to have a per-user directory for the users' >> non-INBOX mailboxes anyway. >> >>> I was thinking of replacing the qpopper binary with the ipop3d from >>> uw-imap however it doesn't appear to be a drop in replacement, is >>> there any additional configurating required??? >> >> No additional configuration is required. In POP3, unlike IMAP, there >> is only the INBOX. >> >> People have replaced qpopper with ipop3d successfully. Just remember >> that ipop3d works just like imapd (internally, it's the same library) >> so requires a UNIX userid just like imapd does. > > I've set up the mail app to use an existing system user (listed in > /etc/passwd), authentication is set to use pam_unix and with qpopper I > can log in and read mail. > > I'm assuming password is plain-text or clear but tried md5-challenge > which also didn't work. > > I renamed qpopper to ipop3d, restarted everything, mail still works. > > Replaced the working ipop3d (qpopper) with the one from wu-imap, can't > read mail due to authentication problem so it's not exactly a drop in > replacement for qpopper. > > I grabbed a newer version of qpopper, built it, dropped it in, it worked. > > If it's a build issue, I'll build it any way you specify, drop it in > and see if it works cause currently I can't get the ipop3d to work at > all. > >>> I couldn't find any inetd or xinetd config files and the >>> documentation didn't tell me anything special was required for >>> arguments or did I miss something? >> >> There isn't anything special required for arguments. Arguments are >> only used with the SecureWare package used on some Tru64 UNIX and SCO >> systems; and that is determined by SecureWare, not by imapd/ipop3d. >> >> -- Mark --
One thing you could do is use nss-mysql so that your password and other related files are stored in MySQL. This will save you the performance cost of having 10,000 or 100,000 users in flat file databases. This should work with UW-IMAPd, right Mark? -Erik Kangas _______________________________________________ Imap-uw mailing list [email protected] https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
