Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 43387 invoked from network); 5 Oct 2009 17:01:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Oct 2009 17:01:15 -0000 Received: (qmail 7546 invoked by uid 500); 5 Oct 2009 17:01:15 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 7514 invoked by uid 500); 5 Oct 2009 17:01:15 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 7504 invoked by uid 99); 5 Oct 2009 17:01:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 17:01:15 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of vdichev@gmail.com designates 209.85.218.226 as permitted sender) Received: from [209.85.218.226] (HELO mail-bw0-f226.google.com) (209.85.218.226) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 17:01:06 +0000 Received: by bwz26 with SMTP id 26so2483884bwz.12 for ; Mon, 05 Oct 2009 10:00:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=D/5KXJZMHAOjpMYz6Cx1DstZ7kqUHHisP4xA7cbmi7g=; b=FhjBYsRbkThsXMz+er8rHXQoC5nydXyjlmc0feh7A7ZHWnnToR1t9ZYWF9pw4Z5CoH VB9eXmV6mS6P+sfKflb1NLTFB9+7QKiX53jutBXK6ZfvyBkhBNuCuCBy+HKPkSLg1gSe m35mEePzL6XxyNDDz9Y8HUgErIe9fEZyibjAc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=LTbky1cem+sYpxHfk/nE5bENH+ycwa2plAlsBvNWHH2dEAO8LbL6SJsRI0gAKi0jfQ y+2k2dy/hDNGW+e4M3th7YMP/AJ5OBxLx6aGTHjuRM06DBF2zmFzSefgubxlFdQHk6Wi 4ACsurINwBhHJ/x3F8/8/ytKnvK+XX/PffIj8= MIME-Version: 1.0 Sender: vdichev@gmail.com Received: by 10.204.5.138 with SMTP id 10mr4186058bkv.110.1254762046272; Mon, 05 Oct 2009 10:00:46 -0700 (PDT) In-Reply-To: <4db64d890910050756i2093355ey4347dc543a7f3136@mail.gmail.com> References: <4db64d890910010425n7b3f6ae6nd0cc820e3167ba59@mail.gmail.com> <4db64d890910010443l22e94871xab078a7a7a73a960@mail.gmail.com> <4db64d890910010530h4377ce8eq698597fc8e48e483@mail.gmail.com> <4db64d890910042247h18a3e807tca6683fd11e08475@mail.gmail.com> <4db64d890910050756i2093355ey4347dc543a7f3136@mail.gmail.com> Date: Mon, 5 Oct 2009 20:00:46 +0300 X-Google-Sender-Auth: 39ed770c54f1092d Message-ID: Subject: Re: Deleting user from access pool From: Vassil Dichev To: esme-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org > Sorry, I mean I found two wrong things when I'm trying to resolve this > task(delete user from pool). > Yes I know it's not thing we want and I'm trying to find what's the reason > and resolution. Oops, sorry, I knew I must be getting it wrong.