Re: Working Group Last Call for draft-ietf-sieve-refuse-reject-00.txt

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 18 August 2005 18:02 UTC

Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j7II21ST048167; Thu, 18 Aug 2005 11:02:01 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j7II21ug048166; Thu, 18 Aug 2005 11:02:01 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j7II20pR048159 for <ietf-mta-filters@imc.org>; Thu, 18 Aug 2005 11:02:01 -0700 (PDT) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.2.178] (shiny.isode.com [62.3.217.250]) by rufus.isode.com via TCP (internal) with ESMTPA; Thu, 18 Aug 2005 19:01:34 +0100
Message-ID: <4304CCFD.8060501@isode.com>
Date: Thu, 18 Aug 2005 19:01:33 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
To: Michael Haardt <michael@freenet-ag.de>
CC: ietf-mta-filters@imc.org
Subject: Re: Working Group Last Call for draft-ietf-sieve-refuse-reject-00.txt
References: <E1E5l6n-0008UN-Qy@nostromo.freenet-ag.de>
In-Reply-To: <E1E5l6n-0008UN-Qy@nostromo.freenet-ag.de>
MIME-version: 1.0
Content-type: text/plain; charset="KOI8-R"; format="flowed"
Content-transfer-encoding: 7bit
Sender: owner-ietf-mta-filters@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-mta-filters/mail-archive/>
List-ID: <ietf-mta-filters.imc.org>
List-Unsubscribe: <mailto:ietf-mta-filters-request@imc.org?body=unsubscribe>

Michael Haardt wrote:

>>>Section 5.1:
>>>
>>>  If the "reason" string is multiline, than the reason text MUST be
>>>  returned as a multiline SMTP/LMTP response, per [SMTP], section
>>>  4.2.1.
>>>
>>>What should happen for plain old SMTP sessions?
>>>      
>>>
>>I am not sure I understand the question.
>>    
>>
>
>I just read again and although there are clients using HELO and not
>understanding multiline responses, RFC 821 already allowed multiline
>responses under all circumstances.  So forget what I said.
>
>Section 5.1 covers not allowed characters, but should add that it is
>an error if messages generated from the response messages would
>have lines exceeding 512 bytes in length.
>  
>
I've added:

 Any line MUST NOT exceed SMTP limit on the maximal line length. The 
server MAY insert CRLFs to make the reason string conform to any such 
limits.

Does this address your issue?

Alexey