Re: [Micronet] CalMail

Hi Jonathon and Jon,

At 09:10 AM 1/8/2004 -0800, Jon Johnsen wrote:
>> Am I reading the migration information correctly?
>>
>> Eudora users must be upgraded to version 5.2.1 before
>>Monday or they will not be able to access their email?
>>
>> So if I'm supporting 200 Eudora users, at least half of
>>whom (probably) are not running 5.2.1 or higher, and are not
>>running as local admin . . . . Will it be necessary to visit all
>>those computers between now and Monday morning to upgrade the
>>Eudora version?

At 11:19 -0800 2004-01-08, Johnathon P Kogelman wrote:
>Thank you Jon, I'm glad to fine I was not the only one caught off
>guard by this. I find a number of issues with the way this is being
>handled:
>
>-Why was not notice to MicroNet, MAGNet in advanced about this, for
>the IT folks that are not on pilot project with CalMail or that do
>not use UCLink as their email server.
>
>-Why give only two day notice for this? Ignore the fact you have
>just over loaded most IT units on Campus, the users need more time
>to adjust to a changes like this.

   In the past, UCLink downtimes and other significant system changes
with impacts on users and support providers, have typically been
announced at least one week in advance. This is an exception;
hopefully one that will not be repeated.

>- Is there detailed information: What happens with Departmental Role
>Accounts? Will there be changes to SMTP/Incoming Mail Servers?
>(Frankly since the notice was forwarded to me, I haven't had time to
>research these questions.)

   The CalMail Help and FAQ documents cover some of these issues, and
will be revised soon to include an QA item regarding departmental
role accounts:

   http://bert.berkeley.edu/calmail/help/
   http://bert.berkeley.edu/calmail/help/faqs.html

   Other than the two questions you mentioned, are there any other
issues that you or others might wish to see added to the FAQs or help
documents? (Please note that some of the client-specific help
documents have yet to be updated from the pilot test, and will be
revised during the next several days.)

>Like Public Health, Chemistry has a large number of Eudora users
>that do not have Eudora 5.2.1 or admin rights on their machines. In
>addition many of our users will need help just doing the setting
>changes, and we simply do not have the man power or time to go to
>most/all of our users in time for Sunday.

   Some approaches that you might wish to use or combine include:

   - Send an email message to your users describing the changes
     they will need to make in their email program.

     A draft of this message appears below, which you and others are
     welcome to use as a starting point. ** This message covers just
     the mechanics of making the change, and does not address the issue
     of the administrative rights required to do so. **

   - Provide direct reconfiguration help to selected users prior to
     (and after) Sunday.

   - Offer users the alternative of checking and sending mail via either
     of the campus's Web-based email clients, until they can either make
     this change themselves or receive help from support providers.

       https://bearmail.berkeley.edu
       https://calmail.berkeley.edu (beginning Sunday evening, January 11)

   - Refer users to the CalMail support service for assistance:

       support@berkeley.edu
       or
       510-642-7776

Aron Roberts
Workstation Software Support Group

--
   The UCLink system is being migrated to a new campus email system, 
CalMail, on Sunday, January 11, 2004.  The transition is being 
represented as being transparent: it has been stated that the vast 
majority of UCLink users will not need to change any settings in 
their email programs.
   If you are using Eudora 5.1 or 5.2 for Windows, however, you *will* 
need to make a change to your settings to avoid encountering "SSL 
Negotiation Failed" errors when you check mail, following the 
transition to the new CalMail system.
   To make this change:
   1. Open the Eudora application.
   2. From the Tools menu, select "Options..."
      This will open the "Options" window.
   3. In the left side of the "Options" window, click "Checking Mail".
   4. From the pull-down menu below "Secure Sockets when Receiving",
      select "Never".
   5. In the left side of the "Options" window, click
      "Sending Mail".
   6. From the pull-down menu below "Secure Sockets when Sending",
      select "Never".
   7. Close the "Options" window.
   Please make this change prior to Sunday, if at all possible, to 
avoid encountering errors when checking mail.
   However, if necessary, you can still make this change at any time 
on or after Sunday, as well.  When you do so, the error messages 
should no longer appear, and you will once again be able to 
successfully check mail.
Aron
------------------------------------------------------------------------
The following was automatically added to this message by the list server:
For information about MAGNet, its meetings and events, and its
mailing list, including information on subscribing and unsubscribing,
see the MAGNet Web site at <http://magnet.berkeley.edu/>.