In order to comply with the recent campus IT security policies (http://itpolicy.berkeley.edu), some changes will be made to the main EECS outgoing email relays. Please customize your settings accordingly. If you have further questions, please contact help@eecs.
- If you use “gateway.eecs.berkeley.edu” as your outgoing email relay, these changes will not impact you. If you are not, we strongly suggest that you update the outgoing email relay to “gateway.eecs.berkeley.edu”. Please note that most ISPs have started blocking port 25, so if you have problem sending email via “gateway.eecs.berkeley.edu”, the helpdesk can assist you.
- Effective 3/29, if your outgoing email relay is “smtp.eecs.berkeley.edu”, authenticated relay will start. If your client (outlook, netscape, thunderbird, etc.) uses ‘secure connections’ “when possible”, you might see a warning about mismatch of SSL certificate (which you can ignore). If you use Eudora, this mismatch cannot be ignored, and you will need to change your outgoing relay and might need to re-import the Entrust certificate chain. Again, the helpdesk can assist you.
- Effective 4/26, only authenticated email relays will be accepted by our outgoing email relay servers. If your client (outlook, netscape, etc.) does not have the ‘secure connection’ set, please set it to “when possible” to allow authentication.
- If any servers within EECS that use “smtp.eecs.berkeley.edu” as a relay server, this will also cease to function after 4/26. Please have your system administrator make the appropriate changes. More information will be sent in the near future.
The Entrust certificate is attached.