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 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 -- http://panda.com/mrc Democracy is two wolves and a sheep deciding what to eat for lunch. Liberty is a well-armed sheep contesting the vote. _______________________________________________ Imap-uw mailing list [email protected] https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
