miaplaza / middlemail Goto Github PK

View Code? Open in Web Editor NEW

3.0 3.0 3.0 191 KB

Transactional Email

License: MIT License

Dockerfile 0.70% C# 93.05% Smarty 6.25%

middlemail's People

Contributors

Stargazers

Watchers

Forkers

saraedum leo-labs ahammoudeh-mia

middlemail's Issues

Upgrade EasyNetQ

We are currently at using EasyNetQ at version 5.2.0 but should try to upgrade to the current major version. We would need to test if we could still consume messages from 5.2.0 when using 6.x. That would make simplify the upgrade.

Run tests on GitHub

probably using Kubernetes-in-Docker as this makes it easy to run the dependencies?

Release nuget packages from actions

README should mention required RabbitMQ plugins

Add creation timestamp to message model

The operation requested on PersistentChannel timed out

Sometimes MiddleMail crashes with the following stack trace:

Unhandled exception. System.TimeoutException: The operation requested on PersistentChannel timed out
   at EasyNetQ.Producer.PersistentChannel.InvokeChannelAction(Action`1 channelAction)
   at EasyNetQ.Producer.ClientCommandDispatcherSingleton.<>c__DisplayClass7_0`1.<InvokeAsync>b__0()
--- End of stack trace from previous location where exception was thrown ---
   at EasyNetQ.Producer.ClientCommandDispatcherSingleton.Invoke[T](Func`2 channelAction)
   at EasyNetQ.Producer.ClientCommandDispatcher.Invoke[T](Func`2 channelAction)
   at EasyNetQ.RabbitAdvancedBus.QueueDeclare(String name, Boolean passive, Boolean durable, Boolean exclusive, Boolean autoDelete, Nullable`1 perQueueMessageTtl, Nullable`1 expires, Nullable`1 maxPriority, String deadLetterExchange, String deadLetterRoutingKey, Nullable`1 maxLength, Nullable`1 maxLengthBytes)
   at EasyNetQ.RabbitBus.SubscribeAsync[T](String subscriptionId, Func`2 onMessage, Action`1 configure)
   at EasyNetQ.RabbitBus.SubscribeAsync[T](String subscriptionId, Func`2 onMessage)
   at MiddleMail.MessageSource.RabbitMQ.RabbitMQMessageSource.Start(Func`2 callback) in /app/src/MiddleMail.MessageSource.RabbitMQ/RabbitMQMessageSource.cs:line 35
   at MiddleMail.MiddleMailService.ExecuteAsync(CancellationToken cancellationToken) in /app/src/MiddleMail/MiddleMailService.cs:line 31
   at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)
   at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
   at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
   at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.Run(IHost host)
   at MiddleMail.Server.Program.Main(String[] args) in /app/src/MiddleMail.Server/Program.cs:line 17

Upload docker images to GitHub

the future of the Docker Hub is a bit uncertain. And it's probably easier to upload to GitHub.

Deploy helm charts to github pages

so we can actually helm install them.

Create tool to recover message from EasyNetQ error queue

Test helm deployment with Github Actions

probably using the Kubernetes-in-Docker action.

Fix reconnection logic in SmtpMimeMessageSender

Do we really need to execute the NoOp command or can we just check for a ServiceNotConnectedException when calling SendAsync
Investigate when exactly we can throw a MimeMessageSenderException (it is better to be conservative here and do not throw if we are unsure)

ElasticSearch storage: Use multiple indices to make it possible to use curator for retention management

It should be possible to use instead of one very large index multiple indices e.g. one per week. That would allow the use of curator (https://www.elastic.co/guide/en/elasticsearch/client/curator/5.8/index.html) for automatic deletion of older data.

Upgrade README

the badge is broken in the README. We should fix it.

Message versioning / model upgrade

We need to find a way to version or upgrade the model of EmailMessage. EasyNetQ routes by typename so we cannot just add fields to the model when running producers and consumer with different model versions. https://github.com/EasyNetQ/EasyNetQ/wiki/Versioning-Messages does not work with future publish (which we use).