Add release URL for version 1.21.6 and update configuration files for mailpit version 1.21.6

[N6REJ]

PR Type

enhancement, configuration changes

---

Description

• Added a new configuration file for Mailpit version 1.21.6, specifying version, executable, web root, UI port, SMTP port, and listen address.
• Updated the bundle release date in build.properties to 2024.12.9.
• Added a release URL for Mailpit version 1.21.6 in releases.properties.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	bearsampp.conf Add configuration file for Mailpit version 1.21.6                bin/mailpit1.21.6/bearsampp.conf Added configuration file for Mailpit version 1.21.6. Set Mailpit version, executable, web root, UI port, SMTP port, and listen address. +6/-0      build.properties Update bundle release date in build properties                      build.properties Updated bundle release date to 2024.12.9. +1/-1
Enhancement	releases.properties Add release URL for Mailpit version 1.21.6                              releases.properties Added release URL for Mailpit version 1.21.6. +2/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Configuration Validation Verify that the SMTP port 25 is available and not blocked by system policies or other services

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Security	Use non-privileged ports by default to avoid permission requirements and potential security issues The SMTP port 25 typically requires admin/root privileges. Consider using a non-privileged port (>1024) by default to avoid permission issues. bin/mailpit1.21.6/bearsampp.conf [5] -mailpitSmtpPort = "25" +mailpitSmtpPort = "1025" Apply this suggestion Suggestion importance[1-10]: 9 Why: Using port 25 requires root/admin privileges which can cause startup failures and pose security risks. Changing to port 1025 is a crucial security best practice that ensures the application can run with regular user permissions.	9

💡 Need additional feedback ? start a PR chat