Terms of Service: bConnected On-Premise Service
The bConnected On-Premise (bCOP) service is provided to campus services/hosts to meet outbound email sending needs that cannot be met in other ways (e.g. cloud-based solution, Gmail SMTP). bCOP can only be used if the alternative solutions are not viable (see eligibility requirements below).
While the bConnected team has a long term goal to eventually eliminate the bCOP service and rely on purely cloud-based solutions for email. To date, we do not have an alternative cloud-based solution available.
Campus applications, systems, or devices that need to use bCOP must be able to use an authenticated connection*, and meet at least one of the following minimum requirements:
- Account sends more than 2,000 individual messages per day (exceeding Google's current sending limits);
- Needs the ability to send from multiple user addresses;
- Uses private IP (RFC-1918) network connection
*A Minimum Security Standards Exception is required to relay mail unauthenticated via bCOP.
- As with all campus email, email content is restricted to P3 data
- Applications/systems may only send mail on behalf of a user with that user’s informed consent
- Applications/systems may only send from email addresses that are valid and monitored
- Applications/systems owners are responsible for maintaining current email distribution lists, ensuring unsubscribe requests are handled in a timely manner, and bouncing addresses are regularly removed
Applicable University Policies
In order to use bCOP, all users must adhere to all applicable laws and University policies, including (but not limited to):
- Email Service Policy (enumerates the principles and practices of operation for the Campus Email Service) https://security.berkeley.edu/email-service-policy?destination=node/131
- Campus Online Activities Policy (establishes policy and guidelines where existing policies do not specifically address issues particular to the use of electronic resources. It also clarifies the applicability of law and of other University or Campus policies to online activities) https://security.berkeley.edu/campus-online-activities-policy
- Computer Use Policy for UC Berkeley (governs all campus computing and networking activities) https://security.berkeley.edu/computer-use-policy
- UC Electronic Communications Policy (establishes policy on allowable use and privacy of electronic communications, and also clarifies limits on privacy protections) http://policy.ucop.edu/doc/7000470/ElectronicCommunications
- CAN-SPAM Act: A compliance Guide for Business https://www.ftc.gov/tips-advice/business-center/guidance/can-spam-act-compliance-guide-business
Violations could result in loss of privileges or disciplinary action.
Privacy & Security
When it comes to privacy and security, protecting the confidentiality and integrity of Berkeley campus data is everyone’s responsibility. UC Berkeley expects all users to employ reasonable and appropriate safeguards concerning the information they transmit and store utilizing bCOP. Email that is deemed suspicious will not be delivered through bCOP, as a way to protect the service reputation and ensure deliverability for bCOP users. Users should familiarize themselves with Data Classifications Standard and Keeping Data Safe before utilizing these services.
Access to bCOP
Submit bCOP Access Request Form