Subject: Re: Courier-imap 4.0.2 setup with qmail-ldap -
msg#00005

Previous Message by Date:

Re: Courier-imap 4.0.2 setup with qmail-ldap

"Tomas Kuliavas" <tokul@xxxxxxxxxxxxxxxxxxxxx> 04/27/05 09:08 PM To qmail-ldap@xxxxxxxxxxxxxx cc Subject Re: Courier-imap 4.0.2 setup with qmail-ldap > "Tomas Kuliavas" <tokul@xxxxxxxxxxxxxxxxxxxxx> wrote on 04/23/2005 > 01:04:31 AM: > >> Courier IMAP supports IMAP Quota extension >> >> There are SquirrelMail plugins that utilize IMAP Quota extension. >> >> Possible issue - message deletion when user is over quota. >> > > sorry if this post is more on courier-imap than qmail-ldap > > i've read the courier-imap docs on maildir quota saying that this will not > work if > "This is the best solution when the default Maildir is located in each > account's home directory. This solution will NOT work if Maildirs are > stored elsewhere, or if you have a large virtual domain setup where a > single userid is used to hold many individual Maildirs, one for each > virtual user. " > > so is it true that if i am using vmail as user and group, i will not be > able to use this functionality? > all my user maildirs are inside /var/vmail (virtual user setup) > > any suggestions? because i would like all my webmail users (squirrelmail) > to see their maildir usage. courier-authlib 0.55. ./configure --prefix=/opt/courier4 \ --without-authpam --without-authuserdb --without-authpwd \ --without-authshadow --without-authcram --with-authldap \ --without-authmysql --without-authvchkpw --without-authpgsql \ --without-authcustom it is possible that some flags are not correct. I've only copied options from courier-imap 3.0.8 config and courier docs argue about not using them. authldaprc diff attached courier-imap 4.0.2 export COURIERAUTHCONFIG=/opt/courier4/bin/courierauthconfig export CFLAGS=-I/opt/courier4/include ./configure --prefix=/opt/courier4 \  --enable-workarounds-for-imap-client-bugs \  --enable-unicode imap configuration file modified to increase maxperip and enabled imap start. main issues - no default quota value. must set it in ldap. - courier can use combined size and count quota format. qmail uses two ldap attributes. Quota Usage plugin 1.3 http://www.squirrelmail.org/plugin_view.php?id=59 - Works. config file is copied from sample file. nothing changed. Check Quota plugin 1.4 http://www.squirrelmail.org/plugin_view.php?id=237 - Works. config file is copied from sample file. nothing changed. You can use courier's authldap module with qmail-ldap, but courier 3.0.8 with qmail's auth-imap is better. It is provides better support and flexibility. I suspect that with courier authldap module ldap server must support authentication schemas used in passwords. openldap does not support some of schemas used by qmail-ldap. It would be better to write own authentication module designed for qmail-ldap, but use of courier's authentication daemon only adds one more point of failure and limits number of concurrent connections. -- Tomas looks like i have some problems with my imap settings but i can't figure it out, maybe need a little help here my /service/imapd/run #!/bin/sh IPADDR=10.0.0.124 exec_prefix=/usr/lib/courier-imap . /usr/lib/courier-imap/etc/imapd.dist exec /usr/local/bin/tcpserver -c 100 -l mail.syahid.com -v -R $IPADDR 143\   ${exec_prefix}/sbin/imaplogin \   /var/qmail/bin/auth_imap \   ${exec_prefix}/bin/imapd Maildir 2>&1 but i think the problem is here, in the CAPABILITY part root@mail:/usr/lib/courier-imap/etc# telnet mail.syahid.com 143 Trying 10.0.0.124... Connected to mail.syahid.com. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 ACL ACL2=UNION] Courier-IMAP ready. Copyright 1998-2004 Double Precision, Inc.  See COPYING for distribution information. . . . but in /usr/lib/courier-imap/etc/imapd.dist, i've already specified quota as needed by courier-imap IMAP_CAPABILITY="IMAP4rev1 QUOTA" i can't figure out where the source of the problem is, it seems that the setting is ignored by courier-imap, any help will be most useful. TQ authldaprc.diff Description: Binary data

Next Message by Date:

patch to allow qmail-ldap to work with recordio

Hello, I had some trouble getting qmail-ldap in cluster mode to work with recordio, which I have fixed. I thought I would pass on the solution: This patch is required for qmail-ldap: http://www.davideous.com/qmail/qmail-1.03-qldap-recordio-ok.patch Before this patch, connection forwarding would write to fd 0, which was okay with sockets, but was bad with pipes created by recordio. This patch makes connection forwarding read from fd 0 and write to fd 1. This patch is required for recordio: http://www.davideous.com/qmail/ucspi-tcp-0.88-recordio-nochild.patch This patch modifies the recordio program in ucspi-tcp so that the process does the monitoring of the input/output of the program is not a child process of that program. (The process that does the monitoring ends up not having a parent becuase we fork twice to create it and leave it orphaned.) This is for use with courier-imap or with qmail-ldap, where the authentication modules do a wait() system call and end up waiting for the monitoring program to end, which is not what we want. David

Previous Message by Thread:

Re: Courier-imap 4.0.2 setup with qmail-ldap

"Tomas Kuliavas" <tokul@xxxxxxxxxxxxxxxxxxxxx> 04/27/05 09:08 PM To qmail-ldap@xxxxxxxxxxxxxx cc Subject Re: Courier-imap 4.0.2 setup with qmail-ldap > "Tomas Kuliavas" <tokul@xxxxxxxxxxxxxxxxxxxxx> wrote on 04/23/2005 > 01:04:31 AM: > >> Courier IMAP supports IMAP Quota extension >> >> There are SquirrelMail plugins that utilize IMAP Quota extension. >> >> Possible issue - message deletion when user is over quota. >> > > sorry if this post is more on courier-imap than qmail-ldap > > i've read the courier-imap docs on maildir quota saying that this will not > work if > "This is the best solution when the default Maildir is located in each > account's home directory. This solution will NOT work if Maildirs are > stored elsewhere, or if you have a large virtual domain setup where a > single userid is used to hold many individual Maildirs, one for each > virtual user. " > > so is it true that if i am using vmail as user and group, i will not be > able to use this functionality? > all my user maildirs are inside /var/vmail (virtual user setup) > > any suggestions? because i would like all my webmail users (squirrelmail) > to see their maildir usage. courier-authlib 0.55. ./configure --prefix=/opt/courier4 \ --without-authpam --without-authuserdb --without-authpwd \ --without-authshadow --without-authcram --with-authldap \ --without-authmysql --without-authvchkpw --without-authpgsql \ --without-authcustom it is possible that some flags are not correct. I've only copied options from courier-imap 3.0.8 config and courier docs argue about not using them. authldaprc diff attached courier-imap 4.0.2 export COURIERAUTHCONFIG=/opt/courier4/bin/courierauthconfig export CFLAGS=-I/opt/courier4/include ./configure --prefix=/opt/courier4 \  --enable-workarounds-for-imap-client-bugs \  --enable-unicode imap configuration file modified to increase maxperip and enabled imap start. main issues - no default quota value. must set it in ldap. - courier can use combined size and count quota format. qmail uses two ldap attributes. Quota Usage plugin 1.3 http://www.squirrelmail.org/plugin_view.php?id=59 - Works. config file is copied from sample file. nothing changed. Check Quota plugin 1.4 http://www.squirrelmail.org/plugin_view.php?id=237 - Works. config file is copied from sample file. nothing changed. You can use courier's authldap module with qmail-ldap, but courier 3.0.8 with qmail's auth-imap is better. It is provides better support and flexibility. I suspect that with courier authldap module ldap server must support authentication schemas used in passwords. openldap does not support some of schemas used by qmail-ldap. It would be better to write own authentication module designed for qmail-ldap, but use of courier's authentication daemon only adds one more point of failure and limits number of concurrent connections. -- Tomas looks like i have some problems with my imap settings but i can't figure it out, maybe need a little help here my /service/imapd/run #!/bin/sh IPADDR=10.0.0.124 exec_prefix=/usr/lib/courier-imap . /usr/lib/courier-imap/etc/imapd.dist exec /usr/local/bin/tcpserver -c 100 -l mail.syahid.com -v -R $IPADDR 143\   ${exec_prefix}/sbin/imaplogin \   /var/qmail/bin/auth_imap \   ${exec_prefix}/bin/imapd Maildir 2>&1 but i think the problem is here, in the CAPABILITY part root@mail:/usr/lib/courier-imap/etc# telnet mail.syahid.com 143 Trying 10.0.0.124... Connected to mail.syahid.com. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 ACL ACL2=UNION] Courier-IMAP ready. Copyright 1998-2004 Double Precision, Inc.  See COPYING for distribution information. . . . but in /usr/lib/courier-imap/etc/imapd.dist, i've already specified quota as needed by courier-imap IMAP_CAPABILITY="IMAP4rev1 QUOTA" i can't figure out where the source of the problem is, it seems that the setting is ignored by courier-imap, any help will be most useful. TQ authldaprc.diff Description: Binary data

Next Message by Thread:

patch to allow qmail-ldap to work with recordio

Hello, I had some trouble getting qmail-ldap in cluster mode to work with recordio, which I have fixed. I thought I would pass on the solution: This patch is required for qmail-ldap: http://www.davideous.com/qmail/qmail-1.03-qldap-recordio-ok.patch Before this patch, connection forwarding would write to fd 0, which was okay with sockets, but was bad with pipes created by recordio. This patch makes connection forwarding read from fd 0 and write to fd 1. This patch is required for recordio: http://www.davideous.com/qmail/ucspi-tcp-0.88-recordio-nochild.patch This patch modifies the recordio program in ucspi-tcp so that the process does the monitoring of the input/output of the program is not a child process of that program. (The process that does the monitoring ends up not having a parent becuase we fork twice to create it and leave it orphaned.) This is for use with courier-imap or with qmail-ldap, where the authentication modules do a wait() system call and end up waiting for the monitoring program to end, which is not what we want. David