Update mailpit properties from release Mailpit-2026.1.15

[N6REJ]

User description

🤖 Automated Module Properties Update

This PR updates the mailpit.properties file with new versions from release Mailpit-2026.1.15.

Changes:

• Extracted assets starting with mailpit (.7z, .exe, or .zip files)
• Added version entries with download URLs
• Maintained semver ordering (newest first)

Release URL: https://github.com/Bearsampp/modules-untouched/releases/tag/Mailpit-2026.1.15

Next Steps:

1. ⏳ Link validation will run automatically
2. ✅ Once validation passes, this PR will auto-merge
3. ❌ If validation fails, please review and fix invalid URLs

---

PR Type

Enhancement

---

Description

• Add mailpit version 1.28.2 with download URL

• Update module tracking from ghostscript to mailpit

• Maintain semver ordering with newest version first

---

Diagram Walkthrough

flowchart LR
  A["mailpit Release 2026.1.15"] -- "Extract version 1.28.2" --> B["Update mailpit.properties"]
  B -- "Add new entry" --> C["Version 1.28.2 at top"]
  D["module_name.txt"] -- "Update module reference" --> E["ghostscript → mailpit"]

Loading

File Walkthrough

	Relevant files
Configuration changes	module_name.txt Update module name reference                                                          module_name.txt Changed module reference from ghostscript to mailpit Indicates current module being updated +1/-1
Enhancement	mailpit.properties Add mailpit 1.28.2 release entry                                                  modules/mailpit.properties Added version 1.28.2 entry with GitHub release URL Maintains semver ordering with newest version first Preserves existing version entries (1.28.0, 1.27.11, etc.) +1/-0

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
⚪	Supply chain risk Description: The new 1.28.2 entry introduces an unpinned binary download URL (no checksum/signature/immutable digest reference), which can enable a supply-chain compromise if the release asset or repository is tampered with or replaced. mailpit.properties [1-1] Referred Code 1.28.2 = https://github.com/Bearsampp/modules-untouched/releases/download/Mailpit-2026.1.15/mailpit-windows-amd64.zip 1.28.0 = https://github.com/Bearsampp/modules-untouched/releases/download/mailpit-2025.12.10/mailpit-windows-amd64.zip
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Correct potential typo in URL casing Correct the casing of the release tag in the URL from Mailpit-2026.1.15 to mailpit-2026.1.15. This change will prevent potential "404 Not Found" errors and ensure consistency with other entries in the file. modules/mailpit.properties [1] -1.28.2 = https://github.com/Bearsampp/modules-untouched/releases/download/Mailpit-2026.1.15/mailpit-windows-amd64.zip +1.28.2 = https://github.com/Bearsampp/modules-untouched/releases/download/mailpit-2026.1.15/mailpit-windows-amd64.zip Apply / Chat Suggestion importance[1-10]: 9 __ Why: This suggestion correctly identifies a critical typo in the URL's casing (Mailpit vs. mailpit) which would likely cause download failures, thus breaking the main functionality of this PR.	High
Security	Add checksum for download Add a SHA-256 checksum to the new version entry to verify the integrity of the downloaded file. This would follow the format version = url, sha256=. modules/mailpit.properties [1] -1.28.2 = https://github.com/Bearsampp/modules-untouched/releases/download/Mailpit-2026.1.15/mailpit-windows-amd64.zip +1.28.2 = https://github.com/Bearsampp/modules-untouched/releases/download/Mailpit-2026.1.15/mailpit-windows-amd64.zip, sha256=<insert_sha256_here> Apply / Chat Suggestion importance[1-10]: 5 __ Why: This is a good security practice suggestion to ensure file integrity. However, it introduces a new format inconsistent with existing entries in the file, which would require additional changes to the codebase to support.	Low
General	Add trailing newline to file Add a trailing newline to module_name.txt to adhere to POSIX conventions. module_name.txt [1] +mailpit - Apply / Chat Suggestion importance[1-10]: 3 __ Why: The suggestion addresses a common convention of ending files with a newline, which improves compatibility with some command-line tools. It is a minor style improvement with low impact.	Low
More