Conference iosg::all-in-1

    I am working with a MailWorks for OpenVMS client. They are not happy
    with OVMW and they are trying to decide on a future direction. They are
    not sure that they want to stay with a "Digital" solution, even though
    they are a almost total VMS shop. Their issues with OVMW and by
    implication with OfficeServer are:
    
    1) They are getting killed on disk space by OVMW's each user gets a
    copy of the message model. In their organization it is not unusual for
    people to send multi-megabyte files to hundreds of other users. I
    understand that OfficeServer will use the one copy per server model ala
    ALL-IN-1 ? 
    
    2) On read reciepts they want the read reciept to reference the subject
    of the original memo, not a "cryptic" message id. Sounds like a nit,
    but the COO of the company wants it. Any idea what OfficeServer will do
    in this area?
    
    3) They need/want Intranet integration with their mail systems.  From
    reading Nigel's directions document, it looks like that will be
    intergal to Office Server. Any additional thoughts in this area?
    
    4) They want/need a platform on which to build workflow, routing, and
    workgroup applications. Can anyone give me a rough idea of the
    development environment, particularly for routing, that will exist in
    OfficeServer?
    
    5) And the last question, which is the hardest for me since it is not a
    technical one, " ... if Office Server is going to be so good, why is
    Digtial operating its company on Exchange ...?" . Or put another way,
    is Digital really committed to OfficeServer, because, if they aren't
    why don't we break away from a Digtial solution now rather than later?
    Can anyone give me some reassurance in this area?
    
    
    Thanks in advance, Steve.

    Here's some quick answers.....
    
    1 - OS will use the shared message model. However, the migration tool
    won't turn old unshared messages into shared messages. So the customer
    will see a gradually increasing benefit once they move.
    
    2 - OS does put message subjects in as long as the original message is
    still on the sender's system. The problem is that the X.400 receipt
    notification does not carry it, so the server looks up the message id
    when the message arrives at the recipinet's system (the original
    sender) to get the subject. 
    
    3 - The ALL-IN-1 Internet access stuff will all be there.
    
    4 - It's currently proposed not to include TeamRoute in OS since it is
    effectively retired.
    
    5 - How many times have I heard this from customers???!!!! And what
    I've found is that there's no really effective answer to it. However
    much spin we put on the story it always boils down to exactly what you
    said - "Why should I use the product if Digital doesn't." Followed
    closely by "If Digital are doing this to verify a large Exchange
    deployment then who's going to verify deployment of a large OS
    system?". All you can end up saying is "Trust me!". 

    Thanks Nigel. As I said number 5 is the toughest since it is not really
    a technical question, although you are correct if we wanted a good test
    bed for OS, it would be to run our own business on it. 
    
    Do you envision any third party product filling the routing and
    workflow needs on OS, since TeamRoute won't be there?
    
    Thanks.  Steve.

    I have  broader question perhaps about OS prompted by the real possibity
    that routing will not be included. Am I correct in saying that OS will
    be a primarly electronic messaging without any (other than scheduling)
    workgroup computing tools? If that's the case, and my client is looking
    for messaging with tightly integrated workgroup computing, then should
    I be looking at Exchange or Notes or .... ?
    
    Steve

    I'd say OS was equally about the distributed file cabinet service,
    which is certainly something we'll be pushing strongly, especially as
    we move that component on to NT.
    
    I guess it depends on what your client means by "tightly integrated
    workgroup computing".
    
    By the way, I've put a short whitepaper on Office Server in our PUBLIC
    drawer. This is also being released by marketing with the addition of a
    couple of pictures.
    

    Nigel ...
    
    I am impressed with what I read about the distributed file cabinet
    service, particularly that it addresses synchronization, skew and
    integrity. These as you know are potential issues with Exchange public
    folders.
    
    It seems to me that the distributed cabinet can address workgroup needs
    in a) structured document repositorites, bulleting boards and maybe
    interactive conferencing. 
    
    By tightly integrated I meant systems that provide not only a file
    cab structure but also tools to develop forms based workflow and
    routing applications. It sounds like these will not be part of OS
    vesrion 1?
    
    Steve
                                                      

    A little more clarification on OS read receipts. If the original
    message still exists, then the subject of the orininal message will
    appear in the receipt subject line? You mentioned this in the context
    of x.400 receipts, how about a) receipts where the sended and recipient
    are on the same server and b) SMTP receipts?
    
    Steve

    Exactly the same story for co-resident sender and recipients.
    
    I don't know about SMTP  - I'll check