• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • UC Berkeley
  • Berkeley Engineering
  • EECS

Header Search Widget

IRIS

Instructional & Research Information Systems

  • About Us
  • Get Started
  • Get Help
  • FAQ
    • FAQ: Accounts
    • FAQ: EECS Slack
    • FAQ: File Storage
    • FAQ: Hardware
    • FAQ: MacOS
    • FAQ: Mail
    • FAQ: Mailing Lists
    • FAQ: Network
    • FAQ: Security
    • FAQ: Unix
    • FAQ: Web
    • FAQ: Windows
  • Services
    • Accounts
    • Backups
    • E-mail
    • EECS Login Servers
    • File Storage
    • Infrastructure
    • Mailing Lists
    • Network
    • Printing
    • Room Reservations
    • Security
    • Software
    • Unix
    • Web
  • Policies
  • Forms
    • System Registration/Update
    • Account Request Form
    • Network Problem Report
    • SSL Certificate Request
    • All Other Forms
  • Rates
  • FAQ: Accounts
  • FAQ: EECS Slack
  • FAQ: File Storage
  • FAQ: Hardware
  • FAQ: MacOS
  • FAQ: Mail
  • FAQ: Mailing Lists
  • FAQ: Network
  • FAQ: Security
  • FAQ: Unix
  • FAQ: Web
  • FAQ: Windows

FAQ: Mail

See Also:

  • IRIS/EECS Mailing Lists FAQ
  • bMail Migration FAQ

Historical information:

  • CalMail Migration FAQ
  • CalMail Forwarding

Where is my @eecs.berkeley.edu or @cs.berkeley.edu mail delivered?

Since the 2010 migration to bMail, all mail sent to @eecs.berkeley.edu or @cs.berkeley.edu addresses is handled first by Google’s servers. For people with active bMail accounts, the most reliable configuration is to make any @eecs.berkeley.edu or @cs.berkeley.edu addresses a bMail alias for the primary bMail account. This is what IRIS does by default for all new accounts. See the bConnected website to list your current aliases or create new @berkeley.edu aliases.

How does @eecs.berkeley.edu forwarding work for addresses not on bMail?

For mailing lists, or closed bMail accounts using @eecs or @cs addresses, IRIS can set up our own local forwarding. Google is supposed to deliver to our alias servers any messages sent to @eecs.berkeley.edu or @cs.berkeley.edu addresses which do not map to active bMail accounts or aliases, so that we can forward them as appropriate.

Why did a message to my @eecs.berkeley.edu forwarding address bounce?

Unfortunately, if Google’s servers think an email is likely to be spam, they do not deliver the message to us, and instead return the misleading message to the sender ** Address not found ** Your message wasn’t delivered to xyz@eecs.berkeley.edu because the address couldn’t be found, or is unable to receive mail.” The net effect of this is that @eecs.berkeley.edu mail forwarding is not 100% reliable for non-bMail accounts. We regret that we have been unable to negotiate a satisfactory solution with Google to improve this situation.

How can I improve the reliabilty of my @eecs.berkeley.edu forwarding address?

There are 2 options to improving reliability for @eecs mailing list aliases.

  1. Your alias could be made into a bConnected list (aka “Google Group”) with its only subscriber being the destination list. If Google classifies a message as spam, it will place the email in a moderation queue instead of bouncing it as** Address not found **. See the bConnected Lists FAQ in the campus Knowledge Base.
  2. Alternately, the alias could be made into a “Special Purpose Account” (SPA) with a bConnected account that is configured to forward to the destination address. If Google classifies a message as spam, it will label the message as Spam in the SPA’s bMail account. See the campus Knowledge Base for more information on creating a SPA.

If you create an @berkeley.edu SPA, we can create @eecs and @cs bMail aliases for it to replace the current @eecs mail forwarding.

Primary Sidebar

IRIS Service Status

Green
We have 0 Active Incidents, and 0 Scheduled Maintenances noted.

IST Service Status

Outages to campus services are listed at berkeley.statusdashboard.com.

Recent Highlights

IRIS to begin syncing names from CalNet

March 9, 2023 by Lars Rohrbach

Upcoming Change to EECS Firewall Handling of SSH

September 22, 2022 by Lars Rohrbach

  • About
  • Contact
  • PRIVACY
  • ACCESSIBILITY
  • NONDISCRIMINATION

© 2022–2023 UC Regents  |  Log in