On 23 March 2010 03:18, Bron Gondwana wrote:
> On Mon, Mar 22, 2010 at 01:52:55PM +, Naresh V wrote:
>> Bron Gondwana fastmail.fm> writes:
>>
>> [...]
>> >
>> > Why does the auth fail on the backend server? It never should. If it does
>> > that means you've screwed up pretty badly. You can
On Mon, Mar 22, 2010 at 01:52:55PM +, Naresh V wrote:
> Bron Gondwana fastmail.fm> writes:
>
> [...]
> >
> > Why does the auth fail on the backend server? It never should. If it does
> > that means you've screwed up pretty badly. You can give the failure from
> > nginx by just passing an
Bron Gondwana fastmail.fm> writes:
[...]
>
> Why does the auth fail on the backend server? It never should. If it does
> that means you've screwed up pretty badly. You can give the failure from
> nginx by just passing an Auth-Status header.
>
It fails on the backend server when the password
On Thu, Mar 18, 2010 at 3:49 AM, ram wrote:
>
> On Wed, 2010-03-17 at 22:45 -0700, Robert Banz wrote:
> >
> >
> > memcached would certainly be fast, but what sort of authentication
> > rate are you talking about here. My bet is that you've got other bits
> > of system, such as the authentication
On Thu, Mar 18, 2010 at 04:19:37PM +0530, ram wrote:
> One more issue with nginx 0.8.34 is that when auth-fails on the real
> server the nginx returns "BAD: internal server error"
> The email clients are not able to interpret this error.
>
> Can I configure nginx to pass on the actual message f
On Wed, 2010-03-17 at 22:45 -0700, Robert Banz wrote:
>
>
> memcached would certainly be fast, but what sort of authentication
> rate are you talking about here. My bet is that you've got other bits
> of system, such as the authentication validation with the target IMAP
> server, that will be mo
memcached would certainly be fast, but what sort of authentication rate are
you talking about here. My bet is that you've got other bits of system, such
as the authentication validation with the target IMAP server, that will be
more of a dominant term when it comes to the performance of your system
> But I thought a memcache lookup will be much more inexpenisve than
> connecting to a mysql db to do lookup for every cyrus connection
Probably slightly. But what happens if the value isn't in memcached?
Where do you get the value from?
Anyway, it's still WAY better than doing:
> > > $user['u
On Thu, 2010-03-18 at 14:36 +1100, Robert Mueller wrote:
>
> > $user['user1'] = 10.1.1.1;
> > $user['user2'] = 10.1.1.2;
> >
> > $user[user15000]=10.1.1.1;
> > For 15k users this method becomes very heavy. There are too many httpd
> > processes running that suck the resources on the machine
> $user['user1'] = 10.1.1.1;
> $user['user2'] = 10.1.1.2;
>
> $user[user15000]=10.1.1.1;
> For 15k users this method becomes very heavy. There are too many httpd
> processes running that suck the resources on the machine. I want to
> store the userlist in a memcache and look it up through ng
I am using ngnix as a Load balancer for two imap servers.
Currently the nginx calls an apache php script that determines if the
user is on imap1 or imap2 by looking up a plain text file.
which contains entries like
$user['user1'] = 10.1.1.1;
$user['user2'] = 10.1.1.2;
$user[user15000]=10.1.1
11 matches
Mail list logo
