Simple Java Mail is maintained in the open. Use the right public channel so the question and its answer can help the next developer too.
Usage questions
Start with the documentation index, search the reference pages, and check the current Javadocs.
If the docs still leave you stuck, open a GitHub issue. Include a minimal example, the Simple Java Mail and Java versions, and any relevant failure output.
Bug reports and feature ideas
Use the public GitHub issue tracker for bugs you can reproduce and feature ideas you can explain with a real use case.
Before posting, remove credentials, private keys, access tokens, message content, and personal recipient data. Include the smallest configuration that still reproduces the behavior.
- Simple Java Mail version
- Java runtime and framework version
- Transport strategy and relevant module
- Expected and observed behavior
- Minimal code or property sample
- Sanitized exception and debug output
Documentation and code contributions
The main repository contains the library source, tests, release history, and development guidance. Website corrections belong in the website repository. Focused issues and pull requests are welcome.
Roadmap
New requirements and planned improvements live in the public issue tracker. If you have a concrete use case, add it there so it can be discussed alongside the rest of the project work.
Sensitive reports
Never put credentials, private keys, tokens, personal mail, exploit details, or unsanitized test cases in a public issue. Instead, open an issue with a short, non-sensitive description. I will reply with a private channel or ask for an email address so we can continue away from the public issue tracker.
Maintainer
Simple Java Mail is maintained by Benny Bottema with contributions from its users and the surrounding open-source projects. It was first published as Vesijama (Very Simple Java Mail) on Google Code in April 2009 and was reintroduced as Simple Java Mail on GitHub in 2015.