MiddleMail is an email sending middleware: It offers an API for transaction email delivery and activity logging and acts as a middleware for other delivery services. Because all parts of MiddleMail are pluggable it can be used in different configurations for both production and staging applications: E.g. you can turn off actual delivery for a staging deployment but leave activity logging enabled to view recent email activity.

Project	Package	Description
MiddleMail		Core library and abstractions
MiddleMail.Model		Message model shared by most other projects
MiddleMail.Server		Ready to use server application
MiddleMail.Client.RabbitMQ		Client library that uses RabbitMQ as a backend
MiddleMail.MessageSource.RabbitMQ	-	MessageSource implementation that uses RabbitMQ as a backend
MiddleMail.Delivery.Smtp	-	Delivery implementation via SMTP
MiddleMail.Storage.Memory	-	Activity storage in-memory
MiddleMail.Storage.ElasticSearch	-	Activity storage in ElasticSearch

The three most important concepts in MiddleMail are MessageSource, Storage and Delivery.

A MiddleMail.IMessageSource defines how MiddleMail consumes emails. Those emails then enter the processing pipeline.

To persist information about email activity MiddleMail uses a MiddleMail.IStorage. Depending on the implementation this makes email activity easily searchable and debuggable.

For actual delivery an MiddleMail.IMailDeliverer is used: MiddleMail.Delivery.Smtp implements such a deliverer for SMTP but it is easy to plugin your prefered Email Delivery SaaS or disable delivery for debugging and testing.

The following table lists the configurable parameters for MiddleMail. To pass them as environment variables on bash replace : with __.

This setup assumes the use of Visual Studio Code as an editor. If not using VSCode, configure environment variables in whatever way is appropriate for your preferred launch mechanism. This setup also runs the dependencies in Docker. You don't have to do this, but it sure is convenient.

1. Clone this repository.
2. Create a launch.json in which you configure the environment variables described above in the Configuration section. This launch.json should target the build of the MiddleMail.Server project, since that's the standalone process. You probably also need to create a tasks.json to run it, with a build task, but that's no different from the standard launch.json setup.
3. Run the docker-compose.dev.yml file to spin up dependency services. It mainly includes:

• A RabbitMQ container as an email message queue.
• An Elasticsearch container as a storage solution.
  • Note that if you're not using Elasticsearch, you can edit the services found in MiddleMail/Server/Program.cs to replace ElasticSearchStorage in services.AddSingleton<IStorage, ElasticSearchStorage>(); with MemoryStorage, an in-memory storage solution. You will also need to edit the dependencies in MiddleMail.Server.csproj to depend on MiddleMail.Storage.Memory instead of MiddleMail.Storage.Elastic.
• A Redis container as a caching solution.
• An smtp4dev container as an SMTP server for development and testing.

1. Run the MiddleMailServer process (with your launch.json).
2. Optional: Test your new MiddleMail instance using the tools/EmailMessageGenerator project to send test emails.