Re: Student/Staff Email

[Bob Bayn <bob.bayn () USU EDU>]

Our branded gmail (aggiemail.usu.edu) is permanently available to anyone with a university ID number - students, staff, 
alumni, emeriti, etc.   However, @usu.edu addresses (on our Exchange server) are only available to current employees, 
although they can be used for personal communications.  Transitioning the personal use at the end of  employment can be 
problematic so we tend to recommend that employees have another email (even aggiemail) for their long term personal use.

Bob Bayn      SER 301      (435)797-2396    IT Security Team
Office of Information Technology,         Utah State University
    Do you know the "Skeptical Hover Technique" and
    how to tell where a web link really goes?  See:
    https://it.usu.edu/computer-security/computer-security-threats/articleID=23737

________________________________
From: The EDUCAUSE Security Constituent Group Listserv [SECURITY () LISTSERV EDUCAUSE EDU] on behalf of Spaller, Mary 
E. [MESpaller () MILLIGAN EDU]
Sent: Thursday, January 08, 2015 11:27 AM
To: SECURITY () LISTSERV EDUCAUSE EDU
Subject: Re: [SECURITY] Student/Staff Email

Back on this issue (sort of) if you don’t mind….

Is there any regulation or guidance on student e-mail accounts and using the .edu when they are no longer students but 
have graduated and become alumni?  How long do you continue to provide e-mail access for graduating students?

Your advice is greatly appreciated!!

Thanks,

Mary Spaller
Network & Security Analyst
P: 423.461.8985
[small logo]



From: The EDUCAUSE Security Constituent Group Listserv [mailto:SECURITY () LISTSERV EDUCAUSE EDU] On Behalf Of Bob Bayn
Sent: Wednesday, December 17, 2014 5:02 PM
To: SECURITY () LISTSERV EDUCAUSE EDU
Subject: Re: [SECURITY] Student/Staff Email

Our contract employees have an enterprise email account on our Exchange server for the duration of their employment.  
Anyone with a USU ID number can get a branded-gmail account (we call ours AggieMail) for as long as google will have 
them.  That applies to students, alumni, employees, former employees and any other gremlins that manage to get an ID 
number.

We are just now going through growing pains to get rid of Exchange accounts for employees who retired in the 
not-too-recent past.  And angst from our emeriti is the result.

Bob Bayn      SER 301      (435)797-2396    IT Security Team
Office of Information Technology,         Utah State University
    Do you know the "Skeptical Hover Technique" and
    how to tell where a web link really goes?  See:
    https://it.usu.edu/computer-security/computer-security-threats/articleID=23737<UrlBlockedError.aspx>
________________________________
From: The EDUCAUSE Security Constituent Group Listserv [SECURITY () LISTSERV EDUCAUSE EDU] on behalf of Knights, John 
[knightsj () WIT EDU]
Sent: Wednesday, December 17, 2014 2:25 PM
To: SECURITY () LISTSERV EDUCAUSE EDU<mailto:SECURITY () LISTSERV EDUCAUSE EDU>
Subject: [SECURITY] Student/Staff Email
Good Afternoon All-

I’ve seen many of you provide feedback on how you handle graduated student email accounts (May 2014 thread), but we 
have a potentially unique twist to this.

We have hired some of our graduates in the past, as I’m sure others have. Our staff, faculty, and students will soon 
all be using the same email system (Office365). I believe that we may be coming to a consensus that we will move away 
from “eternal" emails for students and retirees, instead we would implement eternal email forwarding to their own, 
personal email account instead for development and future engagement opportunities.

The one unique case is when a student that becomes a staff member, leaves but is still a student (usually finishing 
their graduate degree). Since all roles used the same identity and email account, we are looking for suggestions and/or 
comments on what would be best for how to handle the email account for this former staff, current student. We have 
considered setting up a different account to generate a new student email, but there are concerns with this.

Thanks,
John


John Knights
Information Security Officer
Wentworth Institute of Technology
Division of Technology Services