On Sun, 14 Jul 2002, jan groene wrote:
> > Hi all, > > i finally got Courier IMAP running with XMail - more or less flawlessly... > Basically the XMail Maildirs are co-maintained my Courier too now, but > I see some drawbacks with this setup. If someone has a solution/remedy for > the points pls. mail them to the list. This should NOT be treated as > criticism or a bug list of XMail in any way, it's just my approach to ease > the implementation of IMAP with XMail. (Some of the issues may be solved > using root for accessing the IMAP boxes with Courier which is undesireable > in most cases) > > > 1) Inconsistent UserDB > XMail itself only uses it's own userbase, not being able to share with > one of > Couriers authentication modules. Thus I have to admin a 2nd userbase and > manually have to keep it up-to-date on every change (new/deleted users). > An option to authenticate against the XMail UserDB would be a solution > here, > unfortunately I don't know of any. > > 2) Unreachable Maildir by default > As i do all XMail administration via CTRL I have to manually correct > permissions beginning from the domains/ directory upwards to the Maildir > and > it's subdirs for each user as XMail creates the directories with 700 > owned by > root:root. This is also an undesired task as Courier cannot access the > directories by default. XMail uses it's own db because 1) it's fast 2) does not introduce any "external" dependency in the code. since it's very likely that imap users will not use pop3 i like much more the idea of having imap messages redirected to the imap machine. maintaining two db is not a problem if you do a minimum of automation in your process. - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
