chore: software quality improvement

[soulteary]

For some reason, the project has not been actively maintained for a while.

Now we need some volunteers to work together to make this project come alive again, If you are interested, please contact us.

tasks:

• Merge code forked by upstream and downstream projects @soulteary
  • security fixes
  • dependency upgrade
• Update project test cases to support Node LTS version
• Handling accumulated issues
  • feat: Maildev v2.x Docker image update #382
  • Security issue npm audit #374
  • Add a security policy #373
  • d.com #370
  • 10 vulnerabilities (2 moderate, 3 high, 5 critical) #362
  • maildev http server not working #360
  • Critical vulnerability reported #359
  • Upgrade socket.io #352
  • FIX READ.ME: mistakes at docker command #351
  • Wsl Docker setup #345
  • Is maildev dead? No future maintenance? EOL? #339
  • Test do not run #332
  • API enchancements #350
  • tests failing on windows #151 fix for windows tests #150
  • Latest docker image not parsing environment variables #326
  • Feature - log incoming mail to console #354
  • Feature Request - Dispaly From Email Address #363
  • Error: connect ECONNREFUSED 192.168.0.16:9990 #310
  • Upgrade xmlhttprequest-ssl #356
  • feat: More robust docker image #396
• accept pr
  • bcc any plan to support bcc? #233
  • cli improve fix: Program unknown argument #368
  • website new ui New, refreshed website #347
  • Enable compression when fetching all mails #305 feat: Api with compression #388
  • feat: allow filtering of emails in http endpoint #334 feat: email api support filter #389
• deal with accumulated pr
  • Update conservative #344
  • Fix docker port binding #376
  • doc: corrected ports in readme #371
  • Fix docker port mapping #364
  • Enable logging of mail contents via CLI option #357
  • Update Docker Ducumentation on README.md #355
  • Update README.md #353
  • Corrected port mapping for SMTP & Web GUI in docker run command #328
  • Correct docker run ports in readme.md #314
  • Support clustered processes #321
  • docs: adjust document wording #311
  • feat: Add email embedded favicon supports #323
• update the documentation
• release new version
  • GitHub release
  • DockerHub image upgrade feat: Maildev v2.x Docker image update #382
  • NPM package upgrade
• Update github action to automatically publish npm and docker hub

[san-chang]

It's great to see this project go back to live again
I have a few queries as well as suggestions here

1. [Queries] Dose "Contributor" got the ability to update docker image and npm package to push updates?
2. [Suggestion] Migrate to TypeScript
3. [Suggestion] Improve Helm chart to store mail file to k8s PV
4. [Suggestion] Pagination support on mail list UI
5. [Suggestion] Multiple types of outgoing support like HTTP

In my case, I have a private fork with some changes and the purpose is to make the project a production-ready proxy to audit all the email sent out form system not just a development smtp server.

[soulteary]

Hello @idears-org 👋, thank you for your interest in the project. I try to answer your question:

1. yes, @djfarrelly will update the software version after double-check. Until then, if someone is in a hurry, they can use the new dockerfile in the repository to build. Or at a later date, I can also provide a version for temporary use. feat: Maildev v2.x Docker image update #382
2. TypeScript is a good suggestion, but the unfinished tasks in this issue may need to be completed first.
3. If there are interested people to contribute together, the progress will be faster https://github.com/maildev/helm
4. This is also a good suggestion, it looks like it only takes a bit of code to improve the user experience, Talking about the interface, let's continue in another issue feat: Web UI improvements #381
5. This is in my personal plan, but how to implement it into this community version needs to be discussed with other maintainers. Maybe we can open a new issue to discuss in detail?

In my case, I have a private fork with some changes and the purpose is to make the project a production-ready proxy to audit all the email sent out form system not just a development smtp server.

In my personal private fork, I was originally working on improving this feature, but after being suggested by @djfarrelly , I think making the code public can help public good. Maybe we can play together?

[san-chang]

Maybe we can play together?

Sure, I'll keep my eyes on this project and may also contribute on code base.

[soulteary]

We look forward to discussing specific functions and reviewing code with each other in other issues to make the software more practical. 🍻 @idears-org