Wow.  Thanks, Nerijus, but I seem to have a different problem 
than the one Andrew repaired.  In the hope that it will shed 
some light on the ultimate cure(s), here is what happened:

I ran mbxfix on the problem file; it showed only one repair 
(as expected).  When I changed the selected folder in M 
(running with a differetn folder selected during this repair 
pass) I got the "Mahogany : Please choose" dialog with nothing 
in the window.  Since M was now unresponsive I killed M and 
restarted it.

Thinking I might have confused a cache in M the last time I 
just selected the problem folder again and got the "Mahogany : 
Please choose" dialog with "The folder 'Linux/OCLUG' could not 
be opened, would you like to change its settings?" but neither 
"Yes" nor "No" does anything so I killed M again.

I ran mbxfix again and got two repairs this time.  I started M 
again and selected the problem folder, but again got the blank 
"Mahogany : Please choose" dialog (and frozen M) so I killed M 
again.

I searched freshmeat and SourceForge for a similar utility with
zero results.

I searched Google for a similar utility and found Andrew's Perl 
script as the first result.  Most of the rest is about 
Microsoft Outlook Express.

Thought I'd try multiple passes through mbxfix, but it keeps 
finding and fixing the same problems:

[steve@mandrake .M]$ df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/hda1              3526172   2730252    616800  82% /
none                    159864         0    159864   0% /dev/shm
/dev/hda6              6087776    348308   5430220   7% /home
//win98se/documents   10480128   2441728   8038400  24% /mnt/documents
[steve@mandrake .M]$ mv OCLUG OCLUG.3
[steve@mandrake .M]$ ./mbxfix.pl OCLUG.3 OCLUG
* 21-Apr-2002 06:50:00 -0700  uid 2070 length mismatch 3602 repair 3160
* 21-Apr-2002 06:50:00 -0700  uid 2070  mismatch 3604 repair 3602
2 length repairs
 UID repairs
repair 21-Apr-2002 06:50:00 -0700,3602;000000000001-00000816
 with 3602
[steve@mandrake .M]$ mv OCLUG OCLUG.4
[steve@mandrake .M]$ ./mbxfix.pl OCLUG.4 OCLUG
* 21-Apr-2002 06:50:00 -0700  uid 2070 length mismatch 3602 repair 3160
* 21-Apr-2002 06:50:00 -0700  uid 2070  mismatch 3604 repair 3602
2 length repairs
 UID repairs
repair 21-Apr-2002 06:50:00 -0700,3602;000000000001-00000816
 with 3602

Two enhancements come to mind for Mahogany:  (1) Try to trap 
message corruption before it hangs M (or a component -- same 
thing until threaded processes).  (2) Add utilities to repair 
damaged mailbox files, preferrably to the M menu.  I think it 
makes the most sense to start with MBX as the recommended 
mailbox format.  The others can be added as there is enough 
demand.

Meanwhile, I'm no Perl guru.  Since this script obviously 
solved Andrew's problem he is probably not interested in adding
to the script.  Do you know of any other MBX repair utilities 
or where I can find the MBX standard?  (There seems to be no
RFC for MBX.)

Thanks,
Steve


On Tue, 23 Apr 2002 03:09:48 Nerijus Baliunas wrote:

NB> On Mon, 22 Apr 2002 17:33:07 Steve Florkey wrote:
NB> 
NB> SF> Oops!  I broke the MBX mail folder for my most active
NB> SF> Linux Users Group.  I looked briefly for the RFC for
NB> SF> MBX to try to fix it, but couldn't find it.
NB> 
NB> Date: Wed, 17 Oct 2001 13:45:23 -0700 (PDT)
NB> From: Andrew Daviel <[EMAIL PROTECTED]>
NB> 
NB> ... I ended up writing a repair script in Perl which is able
NB> to repair the list in 2 passes by finding the  message
NB> lengths and rewriting the links...
NB> 
NB> ftp://andrew.triumf.ca/pub/mbxfix or
NB> http://andrew.triumf.ca/pub/mbxfix
NB> 



_______________________________________________
Mahogany-Users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mahogany-users

Reply via email to