One reason to change

• A

  Open-closed: the class cannot be extended without modifying it

• B

  Single responsibility: a change to the email code risks breaking the report content

• C

  Dependency inversion: the class depends directly on one concrete mail library

• D

  Nothing: keeping related code together is good design