flea is a shell script which helps you to submit a bug report against the mutt(1) mail user agent.
If you invoke flea, you'll first be prompted for a short description of the problem you experience. This will be used as the bug report's subject line, so it should be concise, but informative.
You are then asked to assign an initial severity level to the problem you observe; flea will give you a description which severity level is appropriate or not.
Then, you are asked for the location of a core dump (normally named core) which may have been left over by a crash of your mutt(1). You can just type ``no'' here, or you can enter the path leading to a core dump. flea will try to use either sdb(1)?, dbx(1)?, or gdb(1) to extract some information from this core dump which may be helpful to developers in order to determine the reason for the crash.
Finally, you are asked whether or not you want to include personal and system mutt(1) configuration files with the bug report. If at all possible, we urge you to answer these questions with ``yes'', since a reference configuration makes it incredibly easier to track down a problem.
If you are using Debian GNU/Linux, flea will now check whether or not mutt has been installed as a Debian package on your system, and suggest to file the bug against the mutt(1) and Debian bug tracking systems. This option was added since the mutt(1) project uses another instantiation of the Debian bug tracking system, so submitting bugs against both systems in one pass is simple.
You are then dropped into your favorite editor as determined by the EDITOR and VISUAL environment variables.
Please give us details about the problem in the empty space below the line reading ``Please type your report below this line''. We are most interested in precise information on what symptoms you observe and what steps may be used to reproduce the bug. Chances are that problems which can easily be reproduced will be fixed quickly. So please take some time when filling out this part of the template.
The remainder of the template contains various kinds of information gathered from your system, including output of the uname(1) command, output from mutt(1) itself, and your system's mutt(1) configuration files. You may wish to browse through this part of the bug report form in order to avoid leaking confidential information to the public.
If you leave the editor, flea will give you the option to review, re-edit, submit, or abandon your bug report. If you decide to submit it, a mail message containing your report will be sent to __
While your bug report is being processed by the bug tracking system, you will receive various e-mail messages from the bug tracking system informing you about what's going on: Once your bug report has been entered into the bug tracking system, it will be assigned a unique serial number about which you are informed via e-mail. If you wish to submit additional information about the bug, you can just send it to the address firstname.lastname@example.org.
Later, you will most likely receive questions from the developers about the problem you observed, and you will eventually be informed that your bug report has been closed. This means that the bug has been fixed at least in the cvs(1) repository. If the answers you receive don't satisfy you, don't hesitate to contact the developers directly under email@example.com.
flea will use the following environment variables:
Your electronic mail address. Will be used to set the bug report's From header, and to send you a copy of the report.
Your login name. If the EMAIL environment variable isn't set, this will be used instead to send you a copy of the report. Setting the sender will be left to sendmail(1)? on your system.
If set, the bug report will contain a Reply-To header with the e-mail address contained in this environment variable.
If set, the bug report will contain an Organization header with the contents of this environment variable.
If set, this environment variable will be expected to contain the path to your favorite pager for viewing the bug report. If unset, more(1) will be used.
If set, this environment variable will be expected to contain the path to your favorite visual editor.