Re: [plasma] "Recipient List" thread and Distribution Lists

"Jim Schaad" <> Fri, 04 January 2013 19:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 49AD421F8716 for <>; Fri, 4 Jan 2013 11:09:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ftF9iXz31HTP for <>; Fri, 4 Jan 2013 11:09:46 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 51D5921F870E for <>; Fri, 4 Jan 2013 11:09:46 -0800 (PST)
Received: from Philemon ( []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: by (Postfix) with ESMTPSA id 757FA38F1D; Fri, 4 Jan 2013 11:09:38 -0800 (PST)
From: "Jim Schaad" <>
To: "'Alan Borland'" <>, <>
References: <>
In-Reply-To: <>
Date: Fri, 4 Jan 2013 11:09:17 -0800
Message-ID: <00de01cdeaae$ff1be640$fd53b2c0$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DF_01CDEA6B.F0FB3E50"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJ5rI3B+tobmEG9RDVCFDlVKhxk5ZbiAxTw
Content-Language: en-us
Subject: Re: [plasma] "Recipient List" thread and Distribution Lists
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The PoLicy Augmented S/Mime \(plasma\) bof discussion list." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 04 Jan 2013 19:09:47 -0000

For a DL that is not Plasma enhanced, it will result in the final recipient
being unable to read the message as the Plasma server will refuse to grant
access to the message.  However this would assume that the DL is not
security aware and thus it is not expanding CMS lockboxes to begin with.
How the DL processes a message for which it cannot find a lockbox for itself
is going to be DL dependent.  It might just reject the message rather than
distributing it.  A Plasma server that knows a DL is not plasma enhanced
could create a lockbox for the DL which is not externally policy enforced,
thus the DL would process as today.


For a DL that is Plasma enhanced, the DL will create a new Plasma recipient
list and give it to the Plasma server.  The Plasma server will then return
either a new or an updated plasma CMS Recipient object to be placed in the


A DL that is partly Plasma enhanced would get the key from the Plasma
server, and then create new CMS lock boxes for all of the individuals on the
DL just as it does today.  This would lose the external policy enforcement
and might cause the originating plasma server to no longer grant access to
that DL.





From: [] On Behalf Of
Alan Borland
Sent: Friday, January 04, 2013 1:55 AM
To: ''
Subject: [plasma] "Recipient List" thread and Distribution Lists


Ignoring the syntax of the "Recipient List" for the moment, but how will the
recipient list mechanism work with distribution lists, especially those DLs
expanded by the mail server?  If on send I supply the plasma server
"" as a <Recipient> and "" receives a copy of the
message as a result of the DL expansion then will fred be able to read the




Alan Borland

Boldon James Limited, a QinetiQ company 

Mobile:        +44 (0)7810 556709
Direct:         +44 (0)1270 507841
Switch:        +44 (0)1270 507800
Email:           <>
Email (R):     <>







Email classified by Boldon James Classifier -  <>