From vfaronov@gmail.com Tue Feb 18 06:15:13 2014 Return-Path: X-Original-To: ietf-822@ietfa.amsl.com Delivered-To: ietf-822@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9F001A01DE for ; Tue, 18 Feb 2014 06:15:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IBFEx-Eabq5c for ; Tue, 18 Feb 2014 06:15:11 -0800 (PST) Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id E6A371A01CB for ; Tue, 18 Feb 2014 06:15:09 -0800 (PST) Received: by mail-pa0-f43.google.com with SMTP id rd3so16775733pab.30 for ; Tue, 18 Feb 2014 06:15:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=pVwkVeorslaKbvOL6A0ks26aNO2vwZbvndzn/bZzn8k=; b=0dH+1JvLdw68YCZ/vt5Rp0UF3E1FInWKkgQP/fiB+M3nCFxfYzES4h1IWnjtJfcPmT bLtsXhj7dcJh71Tfy7kEJRgV15w3O/+PMowWd6qcJFIeND7qsjzvlVZ3uJBB3CSbEYJa tl/DNtYVYhRzhUx8bCEAAaKmrAPF2kLJyIna/GFSE3QsOzTK1WNbSQtojMEbavz31Eda IIkoxuT33nukhMPQFNvaMmuagH7Wglsqwg5JIk7iXVDsN46NwEKnWbPa247/O3fVFzZc JpJGS+KEHdnlwOONORyL9ElhcyTEnC7/3p6QV73gkK34Vxqurj+0bKCaF4MSGmMXe54w cgTQ== MIME-Version: 1.0 X-Received: by 10.66.141.165 with SMTP id rp5mr33387735pab.90.1392732907194; Tue, 18 Feb 2014 06:15:07 -0800 (PST) Received: by 10.68.215.7 with HTTP; Tue, 18 Feb 2014 06:15:06 -0800 (PST) Date: Tue, 18 Feb 2014 18:15:06 +0400 Message-ID: From: Vasiliy Faronov To: ietf-822@ietf.org Content-Type: multipart/alternative; boundary=001a113312ea334f1d04f2aee6f7 Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/qSXJOBgIcrdrdx359M6c3Gs_smY X-Mailman-Approved-At: Tue, 18 Feb 2014 09:32:04 -0800 Subject: [ietf-822] List-Id on the receiving end X-BeenThere: ietf-822@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Feb 2014 14:16:02 -0000 --001a113312ea334f1d04f2aee6f7 Content-Type: text/plain; charset=UTF-8 Hi, I'm looking for information on what receiving software does anything with the List-Id header as defined in RFC 2919. I'm especially interested in whether (and how) they process the list description phrase (section 3) if it's included. Thanks for any pointers. (Not subscribed so please Cc.) -- Vasiliy Faronov http://vasiliy.faronov.name/ --001a113312ea334f1d04f2aee6f7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

I'm looking for info= rmation on what receiving software does anything with the List-Id header as= defined in RFC 2919. I'm especially interested in whether (and how) th= ey process the list description phrase (section 3) if it's included.

Thanks for any pointers. (Not subscribed so please Cc.)=


--
--001a113312ea334f1d04f2aee6f7--