| |
 
[ Introduction |
Resources |
Screenshots |
FAQ |
Feature Requests |
Download |
License |
Paid Support |
Sponsors |
Mirrors ]
To report a known bug, please subscribe to and send a message to dspam-dev
with the prefix "BUG REPORT: " in the subject heading. Include the following
information about your bug:
- 1. System information:
- a. Version of DSPAM you are using (bugs will only be accepted for the most
current STABLE and DEVEL releases).
- b. Operating system and version
- c. DSPAM configure flags (dspam --version)
- 2. Brief synopsis of the problem. Please include:
- General description of your problem
- Steps to reproduce this problem
- What the expected results were, and what the actual results were.
- 3. A copy of the VERBOSE dspam.debug output for the session in which the error manifested is REQUIRED.
- 4. Any relevant portions of your dspam.conf.
- 5. If the bug report is related to a specific message, or DSPAM's altering
of a message, please send a gzipped copy of the original message
(from dspam.messages) and the post-processed copy from the user's mailbox. It's
very important that you compress these messages so that they arrive in
pristine format (and my DSPAM filter doesn't parse them).
- 6. If the problem is a crash, a gdb backtrace or valgrind output is REQUIRED in order to diagnose the problem.
If your bug is accepted, it will be updated in the list below. Once a bug
has been fixed, it will remain in this list with a 'FIXED' status for 30 days.
| BUG ID |
PRIORITY |
STATUS |
COMPONENT |
DESCRIPTION |
| 000004 |
LOW |
FIXED 2/15/2006 |
CGI |
Performance reported as 100% accurate when TS=0, SM>0 |
| 000005 |
LOW |
OPEN |
CGI |
Stats for users in groups are skewed. Cause: group stats get updated
more frequently than individual user stats. |
[ Introduction |
Resources |
Screenshots |
FAQ |
Feature Requests |
Download |
License |
Paid Support |
Sponsors |
Mirrors ]
|
