From tss@iki.fi Thu Jun 13 08:04:40 2013 Return-Path: X-Original-To: lemonade@ietfa.amsl.com Delivered-To: lemonade@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE2D021F8C1A for ; Thu, 13 Jun 2013 08:04:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.299 X-Spam-Level: X-Spam-Status: No, score=-110.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_36=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ohPmCkTE7NyX for ; Thu, 13 Jun 2013 08:04:35 -0700 (PDT) Received: from dovecot.org (dovecot.org [193.210.130.67]) by ietfa.amsl.com (Postfix) with ESMTP id 28C9C21F99AB for ; Thu, 13 Jun 2013 08:04:28 -0700 (PDT) Received: from [192.168.10.100] (cs181255018.pp.htv.fi [82.181.255.18]) by dovecot.org (Postfix) with ESMTP id 37B9D1AE87EE; Thu, 13 Jun 2013 18:04:26 +0300 (EEST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Timo Sirainen In-Reply-To: <440F9363.5000104@andrew.cmu.edu> Date: Thu, 13 Jun 2013 18:04:25 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: References: <440F9363.5000104@andrew.cmu.edu> To: Ken Murchison X-Mailer: Apple Mail (2.1508) Cc: ietf-imapext@imc.org, lemonade@ietf.org Subject: Re: [lemonade] BINARY & CATENATE X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jun 2013 15:04:41 -0000 On 9.3.2006, at 4.30, Ken Murchison wrote: > With the help of the good folks at Lucent I've been working on adding = support for BINARY APPEND to Cyrus (to go along with its existing = support for BINARY FETCH). >=20 > I'm now wondering if I need to support BINARY (literal8) for CATENATE = (TEXT parts)? I don't see any mention of BINARY or literal8 in the = CATENATE draft. >=20 > And what about CTE=3Dbinary in messages/parts fetched via URLs? Old message :) How was this eventually implemented to Cyrus? Or how do = people think it should work? I was also wondering about this a year ago: = http://mailman2.u.washington.edu/pipermail/imap-protocol/2012-June/001787.= html I'm now again wondering if I should change how it works. From dave@cridland.net Fri Jun 14 02:50:18 2013 Return-Path: X-Original-To: lemonade@ietfa.amsl.com Delivered-To: lemonade@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D90B21F94DC for ; Fri, 14 Jun 2013 02:50:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.426 X-Spam-Level: X-Spam-Status: No, score=-2.426 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_36=0.6, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D7riSjOq8EN7 for ; Fri, 14 Jun 2013 02:50:14 -0700 (PDT) Received: from mail-lb0-f171.google.com (mail-lb0-f171.google.com [209.85.217.171]) by ietfa.amsl.com (Postfix) with ESMTP id 9D45F21F9A10 for ; Fri, 14 Jun 2013 02:50:05 -0700 (PDT) Received: by mail-lb0-f171.google.com with SMTP id 13so390026lba.2 for ; Fri, 14 Jun 2013 02:50:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FqwAjXJYpTue6d94e2PBUT92Y4XewNSl92H7J2CZ+ec=; b=UPKwNdSRS3ixOEQgCNQz7wBfublspJ2YTxhUObO+RVwXnGy7UPykp2HvfgMy/2Oguu Iq7Fx0+7JoH4dJmdJD9OJB+00GxftVARdqVlHjQGtbBY+f02t3T5QOf/vEZIYL/tQMST yFQHizQH2/tElSQwI4MGJRgMAOc0z7sclTj88= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=FqwAjXJYpTue6d94e2PBUT92Y4XewNSl92H7J2CZ+ec=; b=d/LGDaq5RNeV/IgIDCb8XQmr2UHqGGc5yIHEZSp6042uo19EXSgjnyvfuB7soV5+nm sEBXo4oLhLSOcAZ7di8gNwyBBxhIipI7oflO6ynvnJgI6Vb86gRAmeB4IctG8C5ywhj3 99C5vC2RThxNix0EyCwBs+80djk70u7QaAIvDO9dxOgY4x2aK1M9U388++iVrZyfBw54 NNZL2W4lrGmREkVn3xr6bdl0y3e5uE7ZESF5tnV91anZiixt3wP0s5lgS8IQSigKkfZ4 +/ss/GELmK6ZLV2K19om6limVp9oMc859HHi30lpB//OpmNbiHTM/nSk8IR/dZlEtwD1 odBQ== MIME-Version: 1.0 X-Received: by 10.152.27.137 with SMTP id t9mr776200lag.28.1371203404569; Fri, 14 Jun 2013 02:50:04 -0700 (PDT) Received: by 10.114.7.42 with HTTP; Fri, 14 Jun 2013 02:50:04 -0700 (PDT) In-Reply-To: References: <440F9363.5000104@andrew.cmu.edu> Date: Fri, 14 Jun 2013 10:50:04 +0100 Message-ID: From: Dave Cridland To: Timo Sirainen Content-Type: multipart/alternative; boundary=089e0160bd0ed82ce204df1a2bc9 X-Gm-Message-State: ALoCoQmOYxeCKQtpOuPsrI+7OK6/jfaCKBeyfHxXVAG1VnAk2qoPPrO+1lWJn9JNkuFZxhlGODar Cc: ietf-imapext@imc.org, lemonade@ietf.org Subject: Re: [lemonade] BINARY & CATENATE X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jun 2013 09:50:18 -0000 --089e0160bd0ed82ce204df1a2bc9 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Jun 13, 2013 at 4:04 PM, Timo Sirainen wrote: > On 9.3.2006, at 4.30, Ken Murchison wrote: > > > With the help of the good folks at Lucent I've been working on adding > support for BINARY APPEND to Cyrus (to go along with its existing support > for BINARY FETCH). > > > > I'm now wondering if I need to support BINARY (literal8) for CATENATE > (TEXT parts)? I don't see any mention of BINARY or literal8 in the > CATENATE draft. > > > > And what about CTE=binary in messages/parts fetched via URLs? > > Old message :) How was this eventually implemented to Cyrus? Or how do > people think it should work? I was also wondering about this a year ago: > http://mailman2.u.washington.edu/pipermail/imap-protocol/2012-June/001787.html > > I'm now again wondering if I should change how it works. > So looking at that, I note that literal8 is actually literalNUL - is defined as being made up of , which is any octet except NUL. So you can have messages you need to rewrite even if they don't use literal8 syntax in the upload. I would, in general, scan and if needs be reformat the message on any APPEND. You're allowed to do this by RFC 3501, which specifically allows it in the case where your underlying message store is only 7-bit capable. Dave --089e0160bd0ed82ce204df1a2bc9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Thu, Jun 13, 2013 at 4:04 PM, Timo Sirainen <tss@iki.fi= > wrote:
On 9.3.2006, at 4.30, Ken Murchison <murch@andrew.cmu.edu> wrote:

> With the help of the good folks at Lucent I've been working on add= ing support for BINARY APPEND to Cyrus (to go along with its existing suppo= rt for BINARY FETCH).
>
> I'm now wondering if I need to support BINARY (literal8) for CATEN= ATE (TEXT parts)? =A0I don't see any mention of BINARY or literal8 in t= he CATENATE draft.
>
> And what about CTE=3Dbinary in messages/parts fetched via URLs?

Old message :) How was this eventually implemented to Cyrus? Or how do peop= le think it should work? I was also wondering about this a year ago: http://mailman2.u.washington.edu/pipermail/imap= -protocol/2012-June/001787.html

I'm now again wondering if I should change how it works.

So looking at that, I note that literal8 is act= ually literalNUL - <literal> is defined as being made up of <CHAR8= >, which is any octet except NUL. So you can have messages you need to r= ewrite even if they don't use literal8 syntax in the upload.

I would, in general, scan and if needs be r= eformat the message on any APPEND. You're allowed to do this by RFC 350= 1, which specifically allows it in the case where your underlying message s= tore is only 7-bit capable.

Dave
--089e0160bd0ed82ce204df1a2bc9-- From tss@iki.fi Sat Jun 15 00:43:20 2013 Return-Path: X-Original-To: lemonade@ietfa.amsl.com Delivered-To: lemonade@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C710C21F9B1C for ; Sat, 15 Jun 2013 00:43:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.199 X-Spam-Level: X-Spam-Status: No, score=-110.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_36=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N9xJskHHLuUt for ; Sat, 15 Jun 2013 00:43:15 -0700 (PDT) Received: from dovecot.org (dovecot.org [193.210.130.67]) by ietfa.amsl.com (Postfix) with ESMTP id 6EB2621F9B14 for ; Sat, 15 Jun 2013 00:43:15 -0700 (PDT) Received: from [192.168.10.100] (cs181255018.pp.htv.fi [82.181.255.18]) by dovecot.org (Postfix) with ESMTP id BBCDA1AE882C; Sat, 15 Jun 2013 10:43:13 +0300 (EEST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) From: Timo Sirainen In-Reply-To: Date: Sat, 15 Jun 2013 10:43:16 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <42F1D15A-1F6C-412B-851B-B0BB409EDD61@iki.fi> References: <440F9363.5000104@andrew.cmu.edu> To: Dave Cridland X-Mailer: Apple Mail (2.1508) Cc: ietf-imapext@imc.org, lemonade@ietf.org Subject: Re: [lemonade] BINARY & CATENATE X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jun 2013 07:43:20 -0000 On 14.6.2013, at 12.50, Dave Cridland wrote: > On Thu, Jun 13, 2013 at 4:04 PM, Timo Sirainen wrote: > On 9.3.2006, at 4.30, Ken Murchison wrote: >=20 > > I'm now wondering if I need to support BINARY (literal8) for = CATENATE (TEXT parts)? I don't see any mention of BINARY or literal8 in = the CATENATE draft. > > > > And what about CTE=3Dbinary in messages/parts fetched via URLs? >=20 > Old message :) How was this eventually implemented to Cyrus? Or how do = people think it should work? I was also wondering about this a year ago: = http://mailman2.u.washington.edu/pipermail/imap-protocol/2012-June/001787.= html >=20 > I'm now again wondering if I should change how it works. >=20 > So looking at that, I note that literal8 is actually literalNUL - = is defined as being made up of , which is any octet = except NUL. So you can have messages you need to rewrite even if they = don't use literal8 syntax in the upload. >=20 > I would, in general, scan and if needs be reformat the message on any = APPEND. You're allowed to do this by RFC 3501, which specifically allows = it in the case where your underlying message store is only 7-bit = capable. Hmh. Maybe this should be done the other way around. Save C-T-E=3Dbinary = mails as is, and do the necessary translation at FETCH time instead so = any digital signatures wouldn't break either. But it would be nice if = clients could get C-T-E=3Dbinary BODYSTRUCTURE replies and such. Perhaps = a new BINARY extension that supports "ENABLE BINARY" for clients that = allows sending them literal8 for FETCH replies? Although how common is C-T-E=3Dbinary support anyway? Is it required by = something? Is it becoming more common in future? Is there any point in = spending time on this?..