Engineering manages two types of email aliases:
- ea.ucla.edu
- seas.ucla.edu
ea.ucla.edu Aliases (Scripted)
Aliases under ea.ucla.edu are automatically generated and maintained through campus data sources, including:
- Student records
- UCPath
- Campus Directory
- Other campus staffing systems
These aliases are updated on a nightly basis via automated scripts. Because of this:
- Manual changes are not supported and will be overwritten during the next data sync.
- In limited cases, temporary additions may be possible, but most aliases do not support manual modifications.
seas.ucla.edu Aliases (Google Groups)
Aliases under seas.ucla.edu are Google Groups–based and managed manually.
- Typically maintained by users with a “Manager” role
- Group Managers are responsible for maintaining membership
- In some cases, additions or removals can be requested through SEASnet, but this is handled on a request basis
Sending Guidelines
When sending emails to any alias:
- Use aliases only for matriculation-related communications
-
Email aliases are intended for official, academic, or administrative matters related to matriculation
-
Sending non-matriculation or unrelated messages increases the risk of recipients marking messages as spam
-
If messages are flagged as spam, future important communications may also be filtered or blocked
- Always use the BCC field
- Prevents unintended “reply all” messages
- Avoids exposing recipients to each other
- Reduces the risk of messages being sent to unintended audiences
Important Note on Google Groups (seas.ucla.edu)
- These aliases do not have restricted sender (“allowed sender”) lists configured
- This means anyone can send email to these aliases
Because of this, it is especially important to:
- Use BCC to avoid exposing alias addresses
- Prevent potential misuse or unintended distribution
Additional Resource
Guidance for faculty and staff on sending messages via MyEngineering is available here: