Conference iosg::all-in-1_v30

813.0. "Using new BLP in EM C" by NCCODE::HARRIS (oooppps) Thu Jun 04 1992 20:57

    the legal dept here at the customer site wants a seperate template used
    when they are creating new documents (in both EM and WP). the only
    thing different on this template is that it says
    
    	CONFIDENTIAL - DO NOT FORWARD
    
    at the top of the document. and obviously the toher thing they want is
    the document to be non-forwardable by the recipients.  i've created the
    template and the menu option to call its use.  but it doesn't seem to
    be right in the named data. it "worked" once in that the new template
    was brought up, but the template had the message header information in
    it.  since then, it won't get past entering CNF on the EMC menu.
    
    to make this non-forwardable, i was thinking of using the MAIL
    NON_FORWARDABLE function, but where would it go in the ND?  should it
    be in a script.  in fact, would i be better off putting this into a
    script?  that is, if user enters C on EM or WP screen they are prompted
    with "Do you wish this document to be labeled as confidential and
    non-forwardable?".  if YES, then go do a script (or an XOP) otherwise
    continue on normally.
    
    	ann
    
    
    ;;CNF;;
    
    CHECK_DISKQUOTA\IFSTATUS
     \MAIL CREATE/NOSEND/TEMPLATE=OA$SITE_DEV_ENGLISH:LEGALMEMO.BLP
     /METER=CREATE_MEMO /HARD=Create no forward
    
    
    
    

Ann,

There's no point in making a document non-forwardable as you can't mail 
documents (if you do S from WP, as I'm sure you know, it'll create a new 
message and attach the document). So it's the actual message that is sent that 
you want made non-forwardable - it may be easier to add the ND to the S option 
(all of them!)

grahame

Is it really worth making a message non-forwardable?

All the user has to do is FT, etc, and send that, or GOLD-GET the text into
another message.  Non-forwardable is just a hint/suggestion/request that the
message shouldn't be forwarded, but can't be enforced (cf writing "please do
not photocopy this" on the back of a piece of paper; it doesn't actually stop
someone photocopying it!).  Hence the non-forwardable attribute shouldn't be
used as a security measure, and in fact will give the na�ve user a false
impression of the security of their message.

Just my humble thought...

Scott

    The only reason I can think of is to prevent it being auto-forwarded by
    the intended recipient. So it will go to that person and no other.
    
    But you are right Scott, it only safeguards against "unintentional"
    forwarding.
    
    Dick