Too many exceptions are swallowed in the email models

[gravesm]

To some extent, this is a question of style, but there are two primary reasons why this practice should generally be avoided:

1. You lose important information about the exception.
2. The codebase gets bloated with conditional statements checking for True/False return values. There's an added burden on the developer to remember to check return values.

To the last point, see issue #102.

The better solution is to just let the exceptions bubble up. This is especially true when the only action taken during a failure is to log the failure. The exception should only be caught if you need to take some special action as a result.

Some examples of methods that could use rewriting:

• https://github.com/MITLibraries/solenoid/blob/master/solenoid/emails/models.py#L205
• https://github.com/MITLibraries/solenoid/blob/master/solenoid/emails/models.py#L232
• https://github.com/MITLibraries/solenoid/blob/master/solenoid/emails/models.py#L265