A knowledge base article about bConnected On-Premise (bCOP) Terms of Service provided by the UC Berkeley IT Service Hub - Knowledge Portal
Service Definition
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).
Assumptions
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.
Eligibility Requirements
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:
*A Minimum Security Standards Exception is required to relay mail unauthenticated via bCOP.
Usage Rules
Applicable University Policies
In order to use bCOP, all users must adhere to all applicable laws and University policies, including (but not limited to):
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