The preferred way to report bugs and feature request is to use the GitHub issue tracker.
But you can also send an email to schmid-thomas at gmx.net
In order to process bugs faster consider the following:
-
Try if the most recent nightly build fixes your issue.
-
Check if you issue is already reported. The list with open issues is small. Try to avoid to duplicate an issue. It slows down the development.
-
Include information about your system and server. This means which the operating System you are on. Which Thunderbird release you are using. If possible check your server's logs for any related errors.
-
Include a debug log/trace with your issue. Just go to the extensions settings and enable debugging options in the Debug tab. Dumping Byte arrays is usually not necessary. Keep in mind that the line starting with "AUTHENTICATE" contains your password. So scramble this line.
-
Mention very precisely what went wrong. "X is broken" is not a good bug report. What did you expect to happen? What happened instead? If possible describe the exact steps how to reproduce the issue.
-
Do not spam or troll issues and bug reports. I don not accept bug spam, it is considered the worst thing you can do with an open source project. It slows down development. Any bug spam will be deleted without notice and the spamming user will be blocked.
crowdin is an collaborative translation tool.
- Log into you Crowding Account or join/signup for free
- Join the project http://crowdin.net/project/sieve/invite
- Translate and vote for translations
I'll merge crowdin translation prior to a release into the source tree.
-
Make sure you have a GitHub Account
-
Fork Sieve (How to fork a repo)
-
Make your changes
-
Submit a pull request (How to create a pull request)
Just send me a patch or the changed files via email to schmid-thomas at gmx.net .