We have been using an email service for years and years. We are starting to outgrow that service and looking at ideas for what is next. These are just some ideas that I had written down on a post-it note but wanted to make sure and put them in digital form.

- Steve said to call and see what the provider of the service says as far as upgrades, ideas, and what not.

- We could always roll things back (we've done this as a temporary band-aid). We are currently using an older shared server to service the internal and API socket connections for the email service. It is called adilasuniveristy.biz. We wanted to move the code to a server that we have deeper access to (dedicated server vs a shared server). We tried moving it to the adilascontent.biz server but couldn't get it to work with all of the emails. It would work fine for adilas.biz email addresses but not for gmail, hotmail, yahoo, etc.

- We could check the certs on the content server

- Get Wayne's help

- Do a whole new rebuild, from the ground up

- Check whitelists and blacklists

- Include better error handling and record errors in log files and/or in the database