Re: POP handling commands given in wrong state

Randall Gellens <randy@Qualcomm.Com> Tue, 26 July 2011 14:30 UTC

Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p6QEUT94006852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Jul 2011 07:30:29 -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 p6QEUT6I006851; Tue, 26 Jul 2011 07:30:29 -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 wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p6QEURIl006845 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pop3ext@imc.org>; Tue, 26 Jul 2011 07:30:28 -0700 (MST) (envelope-from randy@qualcomm.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1311690643; x=1343226643; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p0624060fca547fd8792c@[130.129.83.90]> |In-Reply-To:=20<4E2EC28A.3020301@pscs.co.uk>|References: =20<4E2E49AC.9090207@gmail.com>=20<4E2E7708.3080004@pscs. co.uk>=0D=0A=20<4E2E8762.5030805@gmail.com>=20<p0624060cc a546d8a1a68@[130.129.83.90]>=0D=0A=20<4E2EC28A.3020301@ps cs.co.uk>|X-Mailer:=20Eudora=20for=20Mac=20OS=20X|Date: =20Tue,=2026=20Jul=202011=2007:30:15=20-0700|To:=20Paul =20Smith=20<paul@pscs.co.uk>|From:=20Randall=20Gellens=20 <randy@qualcomm.com>|Subject:=20Re:=20POP=20handling=20co mmands=20given=20in=20wrong=20state|CC:=20Mykyta=20Yevsti feyev=20<evnikita2@gmail.com>,=20<ietf-pop3ext@imc.org>, =20Alexey=0D=0A=20Melnikov=20<alexey.melnikov@isode.com> |MIME-Version:=201.0|Content-Type:=20text/plain=3B=20char set=3D"us-ascii"=3B=20format=3Dflowed|X-Random-Sig-Tag: =201.0b28|X-Originating-IP:=20[172.30.39.5]; bh=oaM/C9AYBZ+sekHr5SZQZ4AgWydZwj+rRMLYL6uG1Gc=; b=EQsZ1xuYAhBl8M+lFf8h9zHtJ24n0rRRzD6iXhhXEUruqDF9oYCdBJ0N RaVcNSzuFI4iQH0UhbliWqN8YH6BWHDugdCZOWEoazjmb6FXdNNgluLiC PlWBVFtA5RGo5IRMmx7RCsEImetrW0zSrOWInYw5e0Xvh5FfkWYxa+79y M=;
X-IronPort-AV: E=McAfee;i="5400,1158,6418"; a="105983040"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine01.qualcomm.com with ESMTP; 26 Jul 2011 07:30:20 -0700
X-IronPort-AV: E=Sophos;i="4.67,269,1309762800"; d="scan'208";a="53570300"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 26 Jul 2011 07:30:20 -0700
Received: from [130.129.83.90] (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.323.0; Tue, 26 Jul 2011 07:30:19 -0700
Message-ID: <p0624060fca547fd8792c@[130.129.83.90]>
In-Reply-To: <4E2EC28A.3020301@pscs.co.uk>
References: <4E2E49AC.9090207@gmail.com> <4E2E7708.3080004@pscs.co.uk> <4E2E8762.5030805@gmail.com> <p0624060cca546d8a1a68@[130.129.83.90]> <4E2EC28A.3020301@pscs.co.uk>
X-Mailer: Eudora for Mac OS X
Date: Tue, 26 Jul 2011 07:30:15 -0700
To: Paul Smith <paul@pscs.co.uk>
From: Randall Gellens <randy@Qualcomm.Com>
Subject: Re: POP handling commands given in wrong state
CC: Mykyta Yevstifeyev <evnikita2@gmail.com>, <ietf-pop3ext@imc.org>, Alexey Melnikov <alexey.melnikov@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
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>

At 2:35 PM +0100 7/26/11, Paul Smith wrote:

>  On 26/07/2011 14:17, Randall Gellens wrote:
>
>>
>>  Per RFC 4206, the server should issue the AUTH-RESP-CODE 
>> capability tag, indicating "that the server includes the AUTH 
>> response code with any authentication error caused by a problem 
>> with the user's credentials" and then in the case you cite, don't 
>> issue the AUTH response code in an -ERR response to USER.
>>
>
>  Hmm - maybe you have the wrong RFC number there - or I'm missing 
> something in our implementation because our mail server doesn't do 
> anything about "Label Switched Paths (LSP) Hierarchy with 
> Generalized Multi-Protocol Label Switching (GMPLS) Traffic 
> Engineering (TE)"... :)

Sorry about that, slip of the fingers.  It's RFC 3206 (not 4206).

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
See, in my line of work, you got to keep repeating things over and
over and over again for the truth to sink in, to kind of catapult
the propaganda.
        --U.S. President George W. Bush in New York, May 24, 2005