masqmail-0.2
view docs/howto-report-bugs @ 164:b8c358b2e242
replaced hmac_md5.c with an own implementation of RFC 2104
Until now the sample code of the RFC itself was used,
but it lacked a license or copyright notice.
See the comment in hmac_md5.c for details.
| author | meillo@marmaro.de |
|---|---|
| date | Sun, 18 Jul 2010 22:20:20 +0200 |
| parents | |
| children |
line source
1 Howto report bugs
2 =================
4 All non-trivial software has bugs and so does masqmail.
6 If you discover a bug then please report it. Your bug reports are an
7 important help in improving masqmail.
9 Valuable bug report include the following information. The first two
10 are essential, the others can also be added on request.
12 - A good description of what you consider to be the bug.
14 - The version of masqmail that was used. (The output of: masqmail -bV).
16 - A description on how to reproduce it. This includes information on
17 other software that is involved.
19 - The configuration files. These are probably the contents of
20 /etc/masqmail/*. Don't forget to substitute confidential data with
21 placeholders.
23 - The relevant log files. Have a look at the value of use_syslog and
24 log_dir in masqmail.conf. If use_syslog is enabled, the files are
25 probably some of /var/log/mail*. If you don't use syslog, then the
26 files reside unter the path assigned to log_dir, or by default in
27 /var/log/masqmail/. Take care to substitute confidential data if you
28 send debug files. (It's good to run masqmail with `-d 5' or `-d 6' to
29 generate debugging data that may help to track down the bug.
31 Report the bug to the mailing list <masqmail@marmaro.de>. You don't
32 have to be subscribed to write to the list. Please tell us if you're
33 not subscribed so that we set you on CC. If you want to subscribe, send
34 a mail with subject ``subscribe masqmail'' to <minimalist@marmaro.de>.