|  |     This should be possible via customisation.
    
    One way might be to change the MAIL CREATE ... in the EMC menu to
    MAIL/CREATE/TEMPLATE=file.blp ...
    
    This will merge the boilerplate file file.blp into the text before the
    user gets to edit it. (Of course, the user could edit it out again.)
    
    Another way might be to customise the Send option to do a Print to
    document (which will merge in the local mail header) and then send (and
    perhaps delete?) that document. This would be idiot-proof, but would
    require more work both for you (or whoever does the changes) and for
    ALL-IN-1 at runtime.
    
    Dave.
 | 
|  |     Hi Dave,
    
    I would go for the easy approach "MAIL/CREATE/TEMPLATE=file.blp" and
    that was my first thought.  However a stamp has to be put in the EM
    and be un-editable so approach 2 is more secure but time consuming. If
    the MAIL function could be changed to have this additional functionality
    it would be the solution.
    
    My thoughts on the subject are that the folowing should be added to the
    qualifiers the "/STAMP=template".  When the em is sent the "/STAMP"
    would merge the em with the template and send the EM. A system wide
    logical or perhaps a system permanent symbol should be set-up like
    SYS$MAIL_STAMP="Y".  An option in the Message Management sub-system
    called Mail Stamp should be introduced to set this to "Y" or "N".
    
    The big problem are distribution lists that contain internal and
    external addresses.  This will require a change in the distribution
    lists fuctionality, in that when an external address is entered a count
    for that DL called "external address" is increased by 1 and decremented
    if deleted.  The MAIL/SEND should check this count if it's >= 1 than
    stamp else no stamp.
    
    My point of putting this request in here was to have this functionality
    introduced in a PFR.  I am sure that other countries require by law
    certain information to be "stamped"/printed on letter heads and EM's.
    Having this option available would make ALL-IN-1 IOS "legal" 8^) as an
    Electronic Office Messaging system.
    
    As ALL-IN-1 IOS moves more towards X.400 compliance hopefully more
    organisations will start sending EM's to other organisations.  I am not
    sure if the X.400 protocol actually address the issue of "stamping"
    EM's with information that is legally required.
    
    The bottom line is that it would be a useful feature to have as part of
    the standard functionality of ALL-IN-1 IOS.  Or put it another way
    let's make ALL-IN-1 IOS "legal" !!!
    
    Regards,
    
    Sunil
 |