Fork?
daemonfire300 opened this issue · 5 comments
Should we create a fork with an extended set of maintainers? Because this rather simple PR #72 is hanging there for a long time.
Also I would be willing to move this project to use go modules, if it doesn't already do it in newer versions.
In a similar vein, this is the "actively maintained fork" however it doesn't have a commit since 2018?
At Shopify, we are maintaining Shopify/gomail (forked from go-mail/mail).
Our fork is focused on stability / quality.
I've recently released https://github.com/wneessen/go-mail which is similar to this package. It forks/ports some parts of this package but follows modern and idomatic Go patterns. Feel free to test it out.
There's also a fork used by Ory (e.g. in their Kratos identity server): https://github.com/ory/mail
I've recently released https://github.com/wneessen/go-mail which is similar to this package. It forks/ports some parts of this package but follows modern and idomatic Go patterns. Feel free to test it out.
still the most actively maintained, thanks for sharing