IETF Logo Mail Archive

POP handling commands given in wrong state

Mykyta Yevstifeyev <evnikita2@gmail.com> Tue, 26 July 2011 04:58 UTC

Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p6Q4wWLJ080403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 25 Jul 2011 21:58:32 -0700 (MST) (envelope-from owner-ietf-pop3ext@mail.imc.org)
Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id p6Q4wWVY080402; Mon, 25 Jul 2011 21:58:32 -0700 (MST) (envelope-from owner-ietf-pop3ext@mail.imc.org)
X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-ietf-pop3ext@mail.imc.org using -f
Received: from mail-ey0-f176.google.com (mail-ey0-f176.google.com [209.85.215.176]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p6Q4wT1L080397 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for <ietf-pop3ext@imc.org>; Mon, 25 Jul 2011 21:58:31 -0700 (MST) (envelope-from evnikita2@gmail.com)
Received: by eya28 with SMTP id 28so111565eya.21 for <ietf-pop3ext@imc.org>; Mon, 25 Jul 2011 21:58:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=sljlMajfcW6n1jndOjYWXmuspqNOjO0Cl+0l1VOAwQs=; b=otfpnPe5i0yfYLaXEIMcuHrhjUgzhA4RVFK6rQFRkR5HY/MoEU6tx+aEc5r9eC0ZvU zrmrAxxU7rGL1BPwC4pGSv/FJhZzaYDVgW/c82TXVGoNVAyqnZLv4ZXT34mJpxv22V2f h8g+wWOoUovWHDioxNfARNRtrPjRjxYkdC/xU=
Received: by 10.204.23.74 with SMTP id q10mr1624895bkb.270.1311656324165; Mon, 25 Jul 2011 21:58:44 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id i14sm32722bkd.6.2011.07.25.21.58.42 (version=SSLv3 cipher=OTHER); Mon, 25 Jul 2011 21:58:43 -0700 (PDT)
Message-ID: <4E2E49AC.9090207@gmail.com>
Date: Tue, 26 Jul 2011 07:59:24 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf-pop3ext@imc.org
Subject: POP handling commands given in wrong state
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-pop3ext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-pop3ext/mail-archive/>
List-ID: <ietf-pop3ext.imc.org>
List-Unsubscribe: <mailto:ietf-pop3ext-request@imc.org?body=unsubscribe>

Hello,

Post Office Protocol (POP) currently has no means of explicit indicating 
that the command is given in the wrong state.

>     A server MUST respond to a command issued when the
>     session is in an incorrect state by responding with a negative status
>     indicator.

doesn't give enough information to the client.  The -ERR response 
indicating wrong state may override -ERR response given with its natural 
meaning.  I propose to define the new POP extension response code (RFC 
2449), WRONG-STATE, to indicate this.  Eg.:

> C: <connects to the server>
> S: +OK server ready
> C: STAT
> S: -ERR [WRONG-STATE] Not in TRANSACTION state yet

Any thoughts?

Mykyta Yevstifeyev

v2.23.0 | Report a Bug | By Email