Reporting Bugs

Help us improve Cypht by reporting bugs and issues you encounter. Your feedback is essential for maintaining the quality and reliability of this open-source email client. Cypht is an entirely volunteer effort, and we rely on community contributions to identify and fix issues. Every bug report helps make Cypht better for everyone.
Follow these steps to ensure your bug report is effective and helps us resolve the issue quickly.

Before creating a new report, search the GitHub issues to see if the bug has already been reported.

Try to reproduce the bug consistently. Note the exact steps that trigger the problem and any patterns you observe.

Collect relevant details about your environment that might help diagnose the problem.

Helpful Information
  • Cypht version
  • PHP version
  • Web server (Apache/Nginx)
  • Browser and version
  • Operating system
  • Email provider(s) affected
When to Report

Report issues that are reproducible and affect functionality. Minor UI improvements or feature requests should use the contribution guidelines instead.

We take security seriously. If you discover a security vulnerability, please report it responsibly.
Security Reporting

For security issues, do not use public GitHub issues. Instead, report them privately through our security channels.

  1. Visit the Cypht Security page
  2. Follow the private reporting instructions
  3. Provide detailed information about the vulnerability
  4. Include steps to reproduce if possible
Security Recognition

Security issues reported before release receive a quick response, thorough review, sincere thanks, and honorable mention on our security page.

Choose the appropriate channel based on your issue type and urgency.
GitHub Issues

Best for: Bug reports, feature requests, technical issues

Submit detailed issues with reproduction steps and system information.

Submit Issue
Gitter Chat

Best for: Quick questions, general discussions, community support

Real-time chat with developers and community members.

Join Chat
Use this template to ensure your bug report includes all necessary information for effective troubleshooting.

Provide a clear and concise description of the problem:

**Bug Description**

A clear and brief description of what the bug is.

**Expected Behavior**
What you expected to happen.

**Actual Behavior**
What actually happened instead.
**To Reproduce**

1.  Go to '...'
2.  Click on '....'
3.  Scroll down to '....'
4.  See error
**Environment**

- Cypht version: [e.g., 1.3.0]
- PHP version: [e.g., 8.1.0]
- Web server: [e.g., Apache 2.4.41]
- Database: [e.g., MySQL 8.0]
- Browser: [e.g., Chrome 91.0]
- OS: [e.g., Ubuntu 20.04]

Include any additional information that might help:

  • Screenshots or screen recordings
  • Error messages from logs
  • Browser console errors
  • Network requests that failed
  • Recent changes to your setup
Have an idea for improving Cypht? We'd love to hear your suggestions!
  • Check if the feature already exists or is planned
  • Explain the problem your feature would solve
  • Describe the proposed solution clearly
  • Consider if it fits Cypht's modular design
  • Be open to discussion and feedback
Contribution Welcome

The best way to get a feature implemented is often to contribute it yourself! Check our developer documentation to get started.

Thank You!

Whether you're reporting a bug, suggesting a feature, or contributing code, your involvement helps make Cypht better for everyone. We appreciate your support!