[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::mailworks-unix

Title:Mailworks-unix
Notice:V2.0.4 now available -- see Note 4.375
Moderator:TAMARA::NEUMAN::Neumann
Created:Wed Jun 02 1993
Last Modified:Tue Jun 03 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1384
Total number of notes:5851

1340.0. "Not a happy client" by DV780::SHAWS () Tue Jan 28 1997 19:42

    I am going to visit a customer who is less that satisfied with
    DECMail Works for UNIX. They serve about a 1000 user base (not sure
    how many concurrent) using a 4000 model 90. The clients are mixture of
    TeamLinks PC and MAC and X-Windows terminals.  Three things seem to be
    major issues for this client:
    	1) When an user send mail to a large distribution list (like to all
           999 other users) the server "freezes" and must be re-booted.
        2) the server ocasionally "just stops" and needs to be re-booted.
        3) The customer because of disk space requirements would much
           perfer a shared memo concept, such as implemented in ALL-IN-1
           and Exchange.
    
    What do I look at for #1 and #2, besides telling the client that it is not
    a good practice to allow sending of mail to all subscribers.  Is the
    "freeze" caused by running out of some resource?  Memory, swap space or
    ??
     
    What can I say to this client about the shared memo concept.
    
    Thanks in advance.
    
    Steve
    
T.RTitleUserPersonal
Name
DateLines
1340.1What version?KOALA::LAVASHWed Jan 29 1997 13:078
    What version of the product is the customer using?
    Quite a few improvements and recommendations have been made in the
    last two ECO kits.
    Additionally, a few extremely large memory leaks caused by the MAC
    client have been fixed in V2.0-ECO2.  This may contribute to having
    to restart the servers.
    
    -diana
1340.2KOALA::ANKANIdle words waste timeWed Jan 29 1997 19:5617
>...using a 4000 model 90...
Eh, sounds like a VAX to me!

>    	1) When an user send mail to a large distribution list (like to all
>           999 other users) the server "freezes" and must be re-booted.
They should not need to reboot or restart the MailWorks. Many of our
customers have a "subscribers" list. 
       2) the server ocasionally "just stops" and needs to be re-booted.
Well, that should not happen, next time it does save the log files and
send them to us.
        3) The customer because of disk space requirements would much
           perfer a shared memo concept, such as implemented in ALL-IN-1
           and Exchange.
We have been looking into that and might implement it one day. Notice, however
that if Exchange and ALL-IN-1 one day want to become DMS (Defense Message
System) compliant, shared messages are a no no...

1340.3OOPS it is VMSDV780::SHAWSMon Feb 03 1997 18:3913
    re .2
    
    You are right, it is a VAX. Once on-site I found out hte clinet uses
    both Mail Works for VMS and UNIX, and his major problems are with the
    VMS server. What appears to be his biggest problem is contiunally
    running out of disk space.  All was well when mail messages were a K or
    two in size, but now when it is easy to send a multi mega byte file to
    a thouand users with one or two mouse clicks disk space can disappear
    in an instant!
    
    Regarding DMS, isn't exchange one of the few certified products, today?
    
    Steve.