The following bug has been CLOSED
======================================================================
http://www.dbmail.org/mantis/bug_view_advanced_page.php?bug_id=0000154
======================================================================
Reported By: xing
Assigned To: aaron
======================================================================
Project: DBMail
Bug ID: 154
Category: Command-Line programs (dbmail-users, dbmail-util)
Reproducibility: always
Severity: trivial
Priority: normal
Status: closed
======================================================================
Date Submitted: 11-Jan-05 08:27 CET
Last Modified: 19-May-05 14:24 CEST
======================================================================
Summary: 2.0.2 dbmail-util outputing "-r" error when -r is
no longer valid
Description:
same as summary
[EMAIL PROTECTED]:/usr/local/sbin # ./dbmail-util -a
Opening connection to database...
Opening connection to authentication...
Ok. Connected.
Checking DBMAIL messageblocks integrity...
Ok. Found [0] unconnected messageblks.
Checking DBMAIL message integrity...
Ok. Found [0] unconnected messages.
Checking DBMAIL mailbox integrity...
Ok. Found [0] unconnected mailboxes.
Checking DBMAIL for NULL messages...
Ok. Found [9] NULL messages.
Checking DBMAIL for NULL physmessages...
Ok. Found [0] physmessages without messageblocks.
Checking DBMAIL for incorrect is_header flags...
Ok. Found [193957] incorrect is_header flags.
Counting messages with PURGE status...
Ok. Found [0] messages with PURGE status.
Counting messages with DELETE status...
Ok. Found [121344] messages with DELETE status.
Vacuum and optimize not performed.
Maintenance done. Errors were found but not fixed.
Try running dbmail-util with the '-r' option to repair the errors.
======================================================================
----------------------------------------------------------------------
aaron - 11-Jan-05 08:30 CET
----------------------------------------------------------------------
Well, -r still works, it's just not in the help output anymore. It is in
the manpage. I'm tempted to be lazy and leave it as it is...
----------------------------------------------------------------------
xing - 11-Jan-05 08:42 CET
----------------------------------------------------------------------
I tried -r and all I got was the help notes. =( dbmail -a or -b reveals
that most of my messages don't use the new is_header but don't see a
repair toggle to fix it within dbmail-util. Is dbmail-util equipped to
auto-populate the is_header stuff?
[EMAIL PROTECTED]:/usr/local/sbin # dbmail-util -r
*** dbmail-util ***
Use this program to maintain your DBMail database.
See the man page for more info. Summary:
-a perform all checks (in this release: -ctubpd)
-c clean up database (optimize/vacuum)
-t test for message integrity
-u null message check
-b body/header check
-p purge messages have the DELETE status set
-d set DELETE status for deleted messages
-l time clear the IP log used for IMAP/POP-before-SMTP
the time is specified as <hours>h<minutes>m
(don't include the angle brackets, though)
Common options for all DBMail utilities:
-f file specify an alternative config file
-q quietly skip interactive prompts
use twice to suppress error messages
-n show the intended action but do not perform it, no to all
-y perform all proposed actions, as though yes to all
-v verbose details
-V show the version
-h show this help message
----------------------------------------------------------------------
aaron - 11-Jan-05 09:14 CET
----------------------------------------------------------------------
Ok, here's the misunderstanding: you need to pick your tests *and* choose
to do something about it. The options c, t, u, p, d and l are for a
variety of tests, and each one will tell you something about your mail
store and whether it needs some fixing. Keep the test flags and add -y/-r
to actually fix it.
----------------------------------------------------------------------
aaron - 22-Apr-05 09:56 CEST
----------------------------------------------------------------------
Fixed.
Bug History
Date Modified Username Field Change
======================================================================
11-Jan-05 08:27xing New Bug
11-Jan-05 08:30aaron Bugnote Added: 0000502
11-Jan-05 08:42xing Bugnote Added: 0000503
11-Jan-05 09:14aaron Bugnote Added: 0000507
22-Apr-05 09:56aaron Bugnote Added: 0000672
22-Apr-05 09:56aaron Assigned To => aaron
22-Apr-05 09:56aaron Resolution open => fixed
22-Apr-05 09:56aaron Status new => resolved
19-May-05 14:24paul Status resolved => closed
======================================================================
