From stanislas.leveau at ac-caen.fr Tue Jul 22 16:47:45 2008 From: stanislas.leveau at ac-caen.fr (Leveau Stanislas) Date: Tue, 22 Jul 2008 22:47:45 +0200 Subject: [imapproxy-info] imapproxy and ldap Message-ID: <20080722224745.esl6s92brycgosok@mel.ac-caen.fr> Hi I would like to know if it's possible to configure Imapproxy as Perdition with ldap. Because i have one Webmail IMP/HORDE and two store with mailbox. I want to be able to choose a back-end server based on the user's identity on the LDAP For example Perdition.conf M /usr/lib/libperditiondb_ldap.so m "ldap://ldap.domain.fr:389/o=domain,c=fr?uid,mailHost,port?sub?(uid=%s)" The same with imapproxy is it possible??Or an other solution Because Perdition is very slow when i want to display 100mails with my Webmail IMP/HORDE but very fast with Imapproxy Regards Stan From julian at lava.net Tue Jul 22 18:04:27 2008 From: julian at lava.net (Julian Cowley) Date: Tue, 22 Jul 2008 12:04:27 -1000 (HST) Subject: [imapproxy-info] imapproxy and ldap In-Reply-To: <20080722224745.esl6s92brycgosok@mel.ac-caen.fr> References: <20080722224745.esl6s92brycgosok@mel.ac-caen.fr> Message-ID: On Tue, 22 Jul 2008, Leveau Stanislas wrote: > I would like to know if it's possible to configure Imapproxy as > Perdition with ldap. Because i have one Webmail IMP/HORDE and two > store with mailbox. I > want to be able to choose a back-end server based on the user's > identity on the LDAP > > For example Perdition.conf > M /usr/lib/libperditiondb_ldap.so > m "ldap://ldap.domain.fr:389/o=domain,c=fr?uid,mailHost,port?sub?(uid=%s)" > > The same with imapproxy is it possible??Or an other solution > Because Perdition is very slow when i want to display 100mails with my > Webmail IMP/HORDE but very fast with Imapproxy We have a similar setup. What we do for Horde/IMP is to set it use localhost:14300 for the IMAP server: $servers['imap'] = array( 'name' => 'IMAP Server', 'server' => 'localhost', 'protocol' => 'imap/notls', 'port' => 14300, ... ); imapproxy is set to listen on that port: listen_port 14300 listen_address 127.0.0.1 Then imapproxy connects to perdition listening again on localhost port 143: server_hostname localhost This has been working well for years now. From Richard.Frovarp at sendit.nodak.edu Tue Jul 22 23:53:18 2008 From: Richard.Frovarp at sendit.nodak.edu (Richard Frovarp) Date: Tue, 22 Jul 2008 22:53:18 -0500 Subject: [imapproxy-info] imapproxy and ldap In-Reply-To: References: <20080722224745.esl6s92brycgosok@mel.ac-caen.fr> Message-ID: <4886AB2E.2010002@sendit.nodak.edu> Julian Cowley wrote: > On Tue, 22 Jul 2008, Leveau Stanislas wrote: > >> I would like to know if it's possible to configure Imapproxy as >> Perdition with ldap. Because i have one Webmail IMP/HORDE and two >> store with mailbox. I >> want to be able to choose a back-end server based on the user's >> identity on the LDAP >> >> For example Perdition.conf >> M /usr/lib/libperditiondb_ldap.so >> m "ldap://ldap.domain.fr:389/o=domain,c=fr?uid,mailHost,port?sub?(uid=%s)" >> >> The same with imapproxy is it possible??Or an other solution >> Because Perdition is very slow when i want to display 100mails with my >> Webmail IMP/HORDE but very fast with Imapproxy >> > > We have a similar setup. What we do for Horde/IMP is to set it use > localhost:14300 for the IMAP server: > > $servers['imap'] = array( > 'name' => 'IMAP Server', > 'server' => 'localhost', > 'protocol' => 'imap/notls', > 'port' => 14300, > ... > ); > > imapproxy is set to listen on that port: > > listen_port 14300 > listen_address 127.0.0.1 > > Then imapproxy connects to perdition listening again on localhost > port 143: > > server_hostname localhost > > This has been working well for years now. I concur. Have imapproxy talk to perdition. From stanislas.leveau at ac-caen.fr Wed Jul 23 03:58:21 2008 From: stanislas.leveau at ac-caen.fr (Leveau Stanislas) Date: Wed, 23 Jul 2008 09:58:21 +0200 Subject: [imapproxy-info] imapproxy and ldap In-Reply-To: References: <20080722224745.esl6s92brycgosok@mel.ac-caen.fr> Message-ID: <20080723095821.hc5k0ov2p5ass4so@mel.ac-caen.fr> Thanks for your answer, the configuration is ok but very slow I think it's the same if you don't use Imapproxy and you configure directly with perdition because In finality it's perdition talk with back-end server based on the user's identity on the LDAP and not Imapproxy so it's very slow... When you use directly Imapproxy it's very fast $servers['imap'] = array( 'name' => 'IMAP Server', 'server' => 'localhost', 'protocol' => 'imap/notls', 'port' => 143, ... ); In finality i's perdition talk with back-end server based on the user's identity on the LDAP and not Imapproxy so it's very slow... > On Tue, 22 Jul 2008, Leveau Stanislas wrote: >> I would like to know if it's possible to configure Imapproxy as >> Perdition with ldap. Because i have one Webmail IMP/HORDE and two >> store with mailbox. I >> want to be able to choose a back-end server based on the user's >> identity on the LDAP >> >> For example Perdition.conf >> M /usr/lib/libperditiondb_ldap.so >> m "ldap://ldap.domain.fr:389/o=domain,c=fr?uid,mailHost,port?sub?(uid=%s)" >> >> The same with imapproxy is it possible??Or an other solution >> Because Perdition is very slow when i want to display 100mails with my >> Webmail IMP/HORDE but very fast with Imapproxy > > We have a similar setup. What we do for Horde/IMP is to set it use > localhost:14300 for the IMAP server: > > $servers['imap'] = array( > 'name' => 'IMAP Server', > 'server' => 'localhost', > 'protocol' => 'imap/notls', > 'port' => 14300, > ... > ); > > imapproxy is set to listen on that port: > > listen_port 14300 > listen_address 127.0.0.1 > > Then imapproxy connects to perdition listening again on localhost > port 143: > > server_hostname localhost > > This has been working well for years now. > _______________________________________________ > imapproxy-info mailing list > imapproxy-info at lists.andrew.cmu.edu > https://lists.andrew.cmu.edu/mailman/listinfo/imapproxy-info > From pont_imapproxy_info at soua.net Wed Jul 23 06:19:40 2008 From: pont_imapproxy_info at soua.net (Pontus Freyhult) Date: Wed, 23 Jul 2008 12:19:40 +0200 Subject: [imapproxy-info] imapproxy and ldap In-Reply-To: <20080723095821.hc5k0ov2p5ass4so@mel.ac-caen.fr> References: <20080722224745.esl6s92brycgosok@mel.ac-caen.fr> <20080723095821.hc5k0ov2p5ass4so@mel.ac-caen.fr> Message-ID: <488705BC.6050300@soua.net> Hi, > Thanks for your answer, the configuration is ok but very slow > > I think it's the same if you don't use Imapproxy and you configure > directly with perdition because In finality it's perdition talk with > back-end server based on the user's identity on the LDAP and not > Imapproxy so it's very slow... > > When you use directly Imapproxy it's very fast > > $servers['imap'] = array( > 'name' => 'IMAP Server', > 'server' => 'localhost', > 'protocol' => 'imap/notls', > 'port' => 143, > ... > ); > [..] That sounds weird - when imapproxy talks to perdition it should keep it's connections alive and reuse them instead of making new connections. Thus, the LDAP lookup should only be done on login (or if a connection has expired from the cache of imapproxy, but that would give problems no matter if you use perdition or not). It's not related to this issue, but I can also recommend those looking into using perdition to also check out nginx (primarily a web proxy, but it has a mail module which has helped us). regards Pontus -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature Url : http://lists.andrew.cmu.edu/pipermail/imapproxy-info/attachments/20080723/4a301681/attachment.bin From stanislas.leveau at ac-caen.fr Wed Jul 23 11:27:36 2008 From: stanislas.leveau at ac-caen.fr (Leveau Stanislas) Date: Wed, 23 Jul 2008 17:27:36 +0200 Subject: [imapproxy-info] imapproxy and ldap In-Reply-To: <488705BC.6050300@soua.net> References: <20080722224745.esl6s92brycgosok@mel.ac-caen.fr> <20080723095821.hc5k0ov2p5ass4so@mel.ac-caen.fr> <488705BC.6050300@soua.net> Message-ID: <20080723172736.zunle79rgh8kgo8s@mel.ac-caen.fr> thanks for your answer nginx is very interesting but with nginx is it possible to configure it as Perdition with ldap Because i want to be able to choose a back-end server based on the user's identity on the LDAP Perdition.conf M /usr/lib/libperditiondb_ldap.so m "ldap://ldap.domain.fr:389/o=domain,c=fr?uid,mailHost,port?sub?(uid=%s)" The same with nginx is it possible?? regards Stan > Hi, > >> Thanks for your answer, the configuration is ok but very slow >> >> I think it's the same if you don't use Imapproxy and you configure >> directly with perdition because In finality it's perdition talk with >> back-end server based on the user's identity on the LDAP and not >> Imapproxy so it's very slow... >> >> When you use directly Imapproxy it's very fast >> >> $servers['imap'] = array( >> 'name' => 'IMAP Server', >> 'server' => 'localhost', >> 'protocol' => 'imap/notls', >> 'port' => 143, >> ... >> ); >> > [..] > > That sounds weird - when imapproxy talks to perdition it should keep > it's connections alive and reuse them instead of making new connections. > Thus, the LDAP lookup should only be done on login (or if a connection > has expired from the cache of imapproxy, but that would give problems no > matter if you use perdition or not). > > It's not related to this issue, but I can also recommend those looking > into using perdition to also check out nginx (primarily a web proxy, but > it has a mail module which has helped us). > > regards > Pontus > > From peter.schober at univie.ac.at Wed Jul 23 12:13:27 2008 From: peter.schober at univie.ac.at (Peter Schober) Date: Wed, 23 Jul 2008 18:13:27 +0200 Subject: [imapproxy-info] imapproxy and ldap In-Reply-To: <20080723172736.zunle79rgh8kgo8s@mel.ac-caen.fr> References: <20080722224745.esl6s92brycgosok@mel.ac-caen.fr> <20080723095821.hc5k0ov2p5ass4so@mel.ac-caen.fr> <488705BC.6050300@soua.net> <20080723172736.zunle79rgh8kgo8s@mel.ac-caen.fr> Message-ID: <20080723161327.GE31730@wssp.cc.univie.ac.at> * Leveau Stanislas [2008-07-23 17:45]: > The same with nginx is it possible?? maybe you should ask the nginx people? http://nginx.net/ http://wiki.codemongers.com/ cheers, -peter From jani+imapproxy-info at ifi.uio.no Wed Jul 23 17:11:41 2008 From: jani+imapproxy-info at ifi.uio.no (Jan Ingvoldstad) Date: Wed, 23 Jul 2008 23:11:41 +0200 Subject: [imapproxy-info] imapproxy and ldap In-Reply-To: <20080723161327.GE31730@wssp.cc.univie.ac.at> (Peter Schober's message of "Wed, 23 Jul 2008 18:13:27 +0200") References: <20080722224745.esl6s92brycgosok@mel.ac-caen.fr> <20080723095821.hc5k0ov2p5ass4so@mel.ac-caen.fr> <488705BC.6050300@soua.net> <20080723172736.zunle79rgh8kgo8s@mel.ac-caen.fr> <20080723161327.GE31730@wssp.cc.univie.ac.at> Message-ID: On Wed, 23 Jul 2008 18:13:27 +0200, Peter Schober said: > * Leveau Stanislas [2008-07-23 17:45]: >> The same with nginx is it possible?? It should be possible, since nginx would require you to code a little bit yourself. > maybe you should ask the nginx people? > http://nginx.net/ > http://wiki.codemongers.com/ If you're first considering an alternative to imapproxy, remember to check out HAProxy before making a decision. I don't know whether there's a pre-made LDAP thingumybob for it, though. http://haproxy.1wt.eu/ http://affectioncode.wordpress.com/2008/06/11/comparing-nginx-and-haproxy-for-web-applications/ http://affectioncode.wordpress.com/2008/06/28/another-comparison-of-haproxy-and-nginx/ -- In the beginning was the Bit, and the Bit was Zero. Then Someone said, Let there be One, and there was One. And Someone blessed them, and Someone said unto them, Be fruitful, and multiply, and replenish the Word and subdue it: and have dominion over every thing that is. From julian at lava.net Wed Jul 23 17:57:47 2008 From: julian at lava.net (Julian Cowley) Date: Wed, 23 Jul 2008 11:57:47 -1000 (HST) Subject: [imapproxy-info] imapproxy and ldap In-Reply-To: <20080723095821.hc5k0ov2p5ass4so@mel.ac-caen.fr> References: <20080722224745.esl6s92brycgosok@mel.ac-caen.fr> <20080723095821.hc5k0ov2p5ass4so@mel.ac-caen.fr> Message-ID: On Wed, 23 Jul 2008, Leveau Stanislas wrote: > Thanks for your answer, the configuration is ok but very slow > > I think it's the same if you don't use Imapproxy and you configure > directly with perdition because In finality it's perdition talk with > back-end server based on the user's identity on the LDAP and not > Imapproxy so it's very slow... > > When you use directly Imapproxy it's very fast > > $servers['imap'] = array( > 'name' => 'IMAP Server', > 'server' => 'localhost', > 'protocol' => 'imap/notls', > 'port' => 143, > ... > ); > > In finality i's perdition talk with back-end server based on the > user's identity on the LDAP and not Imapproxy so it's very slow... Hmm, from what I can tell, imapproxy is caching the IMAP connections from our webmail server and helping to reduce the load on our mailbox servers. It sounds like perhaps it's perdition which is causing the problem for you, although I can't think of why. Even if the LDAP lookups from perdition are slow, it should only be doing them on initial login, but not during the IMAP session. Here's an example of why we're using imapproxy. The logs show Horde/IMP constantly logging in and out of IMAP, but the connection between imapproxy and perdition stays up and steady. Jul 23 11:39:41 webmail perdition[5016]: Auth: 127.0.0.1->127.0.0.1 user="testuser" server="mailbox03.lava.net" port="143" status="ok" Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGIN: 'testuser' (127.0.0.1:34188) on new sd [34] Jul 23 11:39:41 webmail perdition[5019]: Auth: 127.0.0.1->127.0.0.1 user="testuser" server="mailbox03.lava.net" port="143" status="ok" Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGIN: '"testuser"' (127.0.0.1:34191) on new sd [45] Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGOUT: '"testuser"' from server sd [45] Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from server sd [34] Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGIN: 'testuser' (127.0.0.1:34195) on existing sd [34] Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from server sd [34] Jul 23 11:39:42 webmail in.imapproxyd[3115]: LOGIN: 'testuser' (127.0.0.1:34199) on existing sd [34] Jul 23 11:39:42 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from server sd [34] Jul 23 11:39:51 webmail in.imapproxyd[3115]: LOGIN: 'testuser' (127.0.0.1:34223) on existing sd [34] Jul 23 11:39:51 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from server sd [34] Jul 23 11:41:00 webmail in.imapproxyd[3115]: LOGIN: 'testuser' (127.0.0.1:34422) on existing sd [34] Jul 23 11:41:00 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from server sd [34] Jul 23 11:41:02 webmail in.imapproxyd[3115]: LOGIN: 'testuser' (127.0.0.1:34430) on existing sd [34] Jul 23 11:41:02 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from server sd [34] Jul 23 11:41:03 webmail in.imapproxyd[3115]: LOGIN: 'testuser' (127.0.0.1:34435) on existing sd [34] Jul 23 11:41:03 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from server sd [34] Jul 23 11:41:11 webmail in.imapproxyd[3115]: LOGIN: 'testuser' (127.0.0.1:34460) on existing sd [34] Jul 23 11:41:12 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from server sd [34] Jul 23 11:44:41 webmail perdition[5016]: Auth: 127.0.0.1->127.0.0.1 user="testuser" server="mailbox03.lava.net" port="143" status="ok" Jul 23 11:44:41 webmail perdition[5019]: Auth: 127.0.0.1->127.0.0.1 user="testuser" server="mailbox03.lava.net" port="143" status="ok" Jul 23 11:45:18 webmail perdition[5019]: Close: 127.0.0.1->127.0.0.1 user="testuser" received=114 sent=567 Jul 23 11:46:18 webmail perdition[5016]: Close: 127.0.0.1->127.0.0.1 user="testuser" received=3227 sent=305302 -=- julian >> On Tue, 22 Jul 2008, Leveau Stanislas wrote: >>> I would like to know if it's possible to configure Imapproxy as >>> Perdition with ldap. Because i have one Webmail IMP/HORDE and two >>> store with mailbox. I >>> want to be able to choose a back-end server based on the user's >>> identity on the LDAP >>> >>> For example Perdition.conf >>> M /usr/lib/libperditiondb_ldap.so >>> m "ldap://ldap.domain.fr:389/o=domain,c=fr?uid,mailHost,port?sub?(uid=%s)" >>> >>> The same with imapproxy is it possible??Or an other solution >>> Because Perdition is very slow when i want to display 100mails with my >>> Webmail IMP/HORDE but very fast with Imapproxy >> >> We have a similar setup. What we do for Horde/IMP is to set it use >> localhost:14300 for the IMAP server: >> >> $servers['imap'] = array( >> 'name' => 'IMAP Server', >> 'server' => 'localhost', >> 'protocol' => 'imap/notls', >> 'port' => 14300, >> ... >> ); >> >> imapproxy is set to listen on that port: >> >> listen_port 14300 >> listen_address 127.0.0.1 >> >> Then imapproxy connects to perdition listening again on localhost >> port 143: >> >> server_hostname localhost >> >> This has been working well for years now. From stanislas.leveau at ac-caen.fr Wed Jul 23 18:57:24 2008 From: stanislas.leveau at ac-caen.fr (Leveau Stanislas) Date: Thu, 24 Jul 2008 00:57:24 +0200 Subject: [imapproxy-info] imapproxy and ldap In-Reply-To: References: <20080722224745.esl6s92brycgosok@mel.ac-caen.fr> <20080723095821.hc5k0ov2p5ass4so@mel.ac-caen.fr> Message-ID: <20080724005724.al0qgjb536gc8sg0@mel.ac-caen.fr> ok but how many time for display all the message? one minute? Jul 23 11:45:18 webmail perdition[5019]: Close: 127.0.0.1->127.0.0.1 user="testuser" received=114 sent=567 Jul 23 11:46:18 webmail perdition[5016]: Close: 127.0.0.1->127.0.0.1 user="testuser" received=3227 sent=305302 regards Stan Julian Cowley a ecrit: > On Wed, 23 Jul 2008, Leveau Stanislas wrote: >> Thanks for your answer, the configuration is ok but very slow >> >> I think it's the same if you don't use Imapproxy and you configure >> directly with perdition because In finality it's perdition talk with >> back-end server based on the user's identity on the LDAP and not >> Imapproxy so it's very slow... >> >> When you use directly Imapproxy it's very fast >> >> $servers['imap'] = array( >> 'name' => 'IMAP Server', >> 'server' => 'localhost', >> 'protocol' => 'imap/notls', >> 'port' => 143, >> ... >> ); >> >> In finality i's perdition talk with back-end server based on the >> user's identity on the LDAP and not Imapproxy so it's very slow... > > Hmm, from what I can tell, imapproxy is caching the IMAP connections from > our webmail server and helping to reduce the load on our mailbox servers. > It sounds like perhaps it's perdition which is causing the problem for > you, although I can't think of why. Even if the LDAP lookups from > perdition are slow, it should only be doing them on initial login, but not > during the IMAP session. > > Here's an example of why we're using imapproxy. The logs show Horde/IMP > constantly logging in and out of IMAP, but the connection between > imapproxy and perdition stays up and steady. > > Jul 23 11:39:41 webmail perdition[5016]: Auth: 127.0.0.1->127.0.0.1 > user="testuser" server="mailbox03.lava.net" port="143" status="ok" > Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34188) on new sd [34] > Jul 23 11:39:41 webmail perdition[5019]: Auth: 127.0.0.1->127.0.0.1 > user="testuser" server="mailbox03.lava.net" port="143" status="ok" > Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGIN: '"testuser"' > (127.0.0.1:34191) on new sd [45] > Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGOUT: '"testuser"' > from server sd [45] > Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34195) on existing sd [34] > Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:39:42 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34199) on existing sd [34] > Jul 23 11:39:42 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:39:51 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34223) on existing sd [34] > Jul 23 11:39:51 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:41:00 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34422) on existing sd [34] > Jul 23 11:41:00 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:41:02 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34430) on existing sd [34] > Jul 23 11:41:02 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:41:03 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34435) on existing sd [34] > Jul 23 11:41:03 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:41:11 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34460) on existing sd [34] > Jul 23 11:41:12 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:44:41 webmail perdition[5016]: Auth: 127.0.0.1->127.0.0.1 > user="testuser" server="mailbox03.lava.net" port="143" status="ok" > Jul 23 11:44:41 webmail perdition[5019]: Auth: 127.0.0.1->127.0.0.1 > user="testuser" server="mailbox03.lava.net" port="143" status="ok" > Jul 23 11:45:18 webmail perdition[5019]: Close: 127.0.0.1->127.0.0.1 > user="testuser" received=114 sent=567 > Jul 23 11:46:18 webmail perdition[5016]: Close: 127.0.0.1->127.0.0.1 > user="testuser" received=3227 sent=305302 > > -=- julian > >>> On Tue, 22 Jul 2008, Leveau Stanislas wrote: >>>> I would like to know if it's possible to configure Imapproxy as >>>> Perdition with ldap. Because i have one Webmail IMP/HORDE and two >>>> store with mailbox. I >>>> want to be able to choose a back-end server based on the user's >>>> identity on the LDAP >>>> >>>> For example Perdition.conf >>>> M /usr/lib/libperditiondb_ldap.so >>>> m "ldap://ldap.domain.fr:389/o=domain,c=fr?uid,mailHost,port?sub?(uid=%s)" >>>> >>>> The same with imapproxy is it possible??Or an other solution >>>> Because Perdition is very slow when i want to display 100mails with my >>>> Webmail IMP/HORDE but very fast with Imapproxy >>> >>> We have a similar setup. What we do for Horde/IMP is to set it use >>> localhost:14300 for the IMAP server: >>> >>> $servers['imap'] = array( >>> 'name' => 'IMAP Server', >>> 'server' => 'localhost', >>> 'protocol' => 'imap/notls', >>> 'port' => 14300, >>> ... >>> ); >>> >>> imapproxy is set to listen on that port: >>> >>> listen_port 14300 >>> listen_address 127.0.0.1 >>> >>> Then imapproxy connects to perdition listening again on localhost >>> port 143: >>> >>> server_hostname localhost >>> >>> This has been working well for years now. > _______________________________________________ > imapproxy-info mailing list > imapproxy-info at lists.andrew.cmu.edu > https://lists.andrew.cmu.edu/mailman/listinfo/imapproxy-info > From stanislas.leveau at ac-caen.fr Wed Jul 23 19:22:11 2008 From: stanislas.leveau at ac-caen.fr (Leveau Stanislas) Date: Thu, 24 Jul 2008 01:22:11 +0200 Subject: [imapproxy-info] imapproxy and ldap In-Reply-To: References: <20080722224745.esl6s92brycgosok@mel.ac-caen.fr> <20080723095821.hc5k0ov2p5ass4so@mel.ac-caen.fr> Message-ID: <20080724012211.r0jkmjjqnkwg8wcw@mel.ac-caen.fr> My configuration : HORDE Configuration /horde3/config/conf.php $conf['auth']['params']['hostspec'] = 'localhost'; $conf['auth']['params']['port'] = 143; $conf['auth']['params']['protocol'] = 'imap'; $conf['auth']['params']['imapconfig'] = 'separate'; $conf['auth']['driver'] = 'imap'; /horde3/imp/config/servers.php 'name' => 'IMAP Server', 'server' => 'localhost', 'hordeauth' => true, 'protocol' => 'imap', 'port' => 14300, Imapproxy configuration /etc/imapproxy.conf server_hostname localhost cache_size 3072 listen_port 14300 listen_address 127.0.0.1 server_port 143 cache_expiration_time 300 enable_select_cache no Perdition configuration /etc/perdition/perdition.conf M /usr/lib/libperditiondb_ldap.so m "ldap://ldap.domain.fr:389/o=domain,c=fr?uid,mailhost,port?sub?(uid=%s)" I think it's a good configuration? Imapproxy only it's very fast (but not possibility to use back-end server based on the user's identity on the LDAP) Perdition only it's very slow Imapproxy and perdition it's very slow > On Wed, 23 Jul 2008, Leveau Stanislas wrote: >> Thanks for your answer, the configuration is ok but very slow >> >> I think it's the same if you don't use Imapproxy and you configure >> directly with perdition because In finality it's perdition talk with >> back-end server based on the user's identity on the LDAP and not >> Imapproxy so it's very slow... >> >> When you use directly Imapproxy it's very fast >> >> $servers['imap'] = array( >> 'name' => 'IMAP Server', >> 'server' => 'localhost', >> 'protocol' => 'imap/notls', >> 'port' => 143, >> ... >> ); >> >> In finality i's perdition talk with back-end server based on the >> user's identity on the LDAP and not Imapproxy so it's very slow... > > Hmm, from what I can tell, imapproxy is caching the IMAP connections from > our webmail server and helping to reduce the load on our mailbox servers. > It sounds like perhaps it's perdition which is causing the problem for > you, although I can't think of why. Even if the LDAP lookups from > perdition are slow, it should only be doing them on initial login, but not > during the IMAP session. > > Here's an example of why we're using imapproxy. The logs show Horde/IMP > constantly logging in and out of IMAP, but the connection between > imapproxy and perdition stays up and steady. > > Jul 23 11:39:41 webmail perdition[5016]: Auth: 127.0.0.1->127.0.0.1 > user="testuser" server="mailbox03.lava.net" port="143" status="ok" > Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34188) on new sd [34] > Jul 23 11:39:41 webmail perdition[5019]: Auth: 127.0.0.1->127.0.0.1 > user="testuser" server="mailbox03.lava.net" port="143" status="ok" > Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGIN: '"testuser"' > (127.0.0.1:34191) on new sd [45] > Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGOUT: '"testuser"' > from server sd [45] > Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34195) on existing sd [34] > Jul 23 11:39:41 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:39:42 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34199) on existing sd [34] > Jul 23 11:39:42 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:39:51 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34223) on existing sd [34] > Jul 23 11:39:51 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:41:00 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34422) on existing sd [34] > Jul 23 11:41:00 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:41:02 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34430) on existing sd [34] > Jul 23 11:41:02 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:41:03 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34435) on existing sd [34] > Jul 23 11:41:03 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:41:11 webmail in.imapproxyd[3115]: LOGIN: 'testuser' > (127.0.0.1:34460) on existing sd [34] > Jul 23 11:41:12 webmail in.imapproxyd[3115]: LOGOUT: 'testuser' from > server sd [34] > Jul 23 11:44:41 webmail perdition[5016]: Auth: 127.0.0.1->127.0.0.1 > user="testuser" server="mailbox03.lava.net" port="143" status="ok" > Jul 23 11:44:41 webmail perdition[5019]: Auth: 127.0.0.1->127.0.0.1 > user="testuser" server="mailbox03.lava.net" port="143" status="ok" > Jul 23 11:45:18 webmail perdition[5019]: Close: 127.0.0.1->127.0.0.1 > user="testuser" received=114 sent=567 > Jul 23 11:46:18 webmail perdition[5016]: Close: 127.0.0.1->127.0.0.1 > user="testuser" received=3227 sent=305302 > > -=- julian > >>> On Tue, 22 Jul 2008, Leveau Stanislas wrote: >>>> I would like to know if it's possible to configure Imapproxy as >>>> Perdition with ldap. Because i have one Webmail IMP/HORDE and two >>>> store with mailbox. I >>>> want to be able to choose a back-end server based on the user's >>>> identity on the LDAP >>>> >>>> For example Perdition.conf >>>> M /usr/lib/libperditiondb_ldap.so >>>> m "ldap://ldap.domain.fr:389/o=domain,c=fr?uid,mailHost,port?sub?(uid=%s)" >>>> >>>> The same with imapproxy is it possible??Or an other solution >>>> Because Perdition is very slow when i want to display 100mails with my >>>> Webmail IMP/HORDE but very fast with Imapproxy >>> >>> We have a similar setup. What we do for Horde/IMP is to set it use >>> localhost:14300 for the IMAP server: >>> >>> $servers['imap'] = array( >>> 'name' => 'IMAP Server', >>> 'server' => 'localhost', >>> 'protocol' => 'imap/notls', >>> 'port' => 14300, >>> ... >>> ); >>> >>> imapproxy is set to listen on that port: >>> >>> listen_port 14300 >>> listen_address 127.0.0.1 >>> >>> Then imapproxy connects to perdition listening again on localhost >>> port 143: >>> >>> server_hostname localhost >>> >>> This has been working well for years now. > _______________________________________________ > imapproxy-info mailing list > imapproxy-info at lists.andrew.cmu.edu > https://lists.andrew.cmu.edu/mailman/listinfo/imapproxy-info > From pont_imapproxy_info at soua.net Thu Jul 24 05:46:23 2008 From: pont_imapproxy_info at soua.net (Pontus Freyhult) Date: Thu, 24 Jul 2008 11:46:23 +0200 Subject: [imapproxy-info] imapproxy and ldap In-Reply-To: <20080724012211.r0jkmjjqnkwg8wcw@mel.ac-caen.fr> References: <20080722224745.esl6s92brycgosok@mel.ac-caen.fr> <20080723095821.hc5k0ov2p5ass4so@mel.ac-caen.fr> <20080724012211.r0jkmjjqnkwg8wcw@mel.ac-caen.fr> Message-ID: <48884F6F.8020403@soua.net> Hi, > HORDE Configuration > > /horde3/config/conf.php > > $conf['auth']['params']['hostspec'] = 'localhost'; > $conf['auth']['params']['port'] = 143; > $conf['auth']['params']['protocol'] = 'imap'; > $conf['auth']['params']['imapconfig'] = 'separate'; > $conf['auth']['driver'] = 'imap'; > > > /horde3/imp/config/servers.php > > 'name' => 'IMAP Server', > 'server' => 'localhost', > 'hordeauth' => true, > 'protocol' => 'imap', > 'port' => 14300, > > > Imapproxy configuration > > /etc/imapproxy.conf > > server_hostname localhost > cache_size 3072 > listen_port 14300 > listen_address 127.0.0.1 > server_port 143 > cache_expiration_time 300 > enable_select_cache no > > Perdition configuration > > /etc/perdition/perdition.conf > M /usr/lib/libperditiondb_ldap.so > m "ldap://ldap.domain.fr:389/o=domain,c=fr?uid,mailhost,port?sub?(uid=%s)" > > I think it's a good configuration? Your problem is probably that you refer to ldap.domain.fr, which doesn't exist. (No, I don't believe that, but obfuscating is generally not a good idea when asking for help). Except for that, your configuration looks OK, kind of. IIRC it shouldn't do authentication more than once, but I would have used imapproxy (port 14300) for authentication as well. (For interactive use that configuration should work well enough, but for those using the automatic reload feature of horde, chances are connections have expired and it will need a ldap lookup and server login, so I'd consider increasing the cache_expiration_time.) Looking carefully through your logs should give a hint to where the problem might be. regards, Pontus -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature Url : http://lists.andrew.cmu.edu/pipermail/imapproxy-info/attachments/20080724/f07c51ef/attachment.bin