Re: mailbox corruption
* Marc Wilson ([EMAIL PROTECTED]) wrote: > On Sat, Dec 08, 2001 at 08:12:48PM -0800, Mike Erickson wrote: > > A few times, I've been going through old mail in one of my mailboxes and > > noticed a mail with no subject. Opening it up reveals an entire email > > message, headers and all, in the body. I'm using sendmail, procmail, > > biff n and mbox format. Is this mutt-related? [...] > Now, of course, if you never use mailx, then I'm all wet and you have some > other problem. ^_^ Thanks for the response, but yeah, this is the case. I checked my system and mailx only exists (uninstalled) in the ports directory ;) I'm thinking this must be mutt, since it was old mail (thus not caused by new mail being written incorrectly) that got messed up, and mutt is the only program that touches my mailboxes after procmail writes to them. Hrm, if I figure this out, I'll let you all know, since it seems I'm not the only person suffering from it. mike msg21564/pgp0.pgp Description: PGP signature
Re: mailbox corruption
On Sat, Dec 08, 2001 at 08:12:48PM -0800, Mike Erickson wrote: > Hello, > > A few times, I've been going through old mail in one of my mailboxes and > noticed a mail with no subject. Opening it up reveals an entire email > message, headers and all, in the body. I'm using sendmail, procmail, > biff n and mbox format. Is this mutt-related? > There is just one time I noticed this and that was just with mail from one regular correspondant of mine. Her mail never appeared to have a Subject line in the index, but did in the mail message. She uses Outlook Express :( .. so I just never bothered to investigate it further ..assuming.. well you can guess what I was assuming. Then one day it stopped happening, and has never happened since. This does not help your problem of course, I didn't ask about it on the list at the time, I just put up with it. -- Regards Cliff
Re: mailbox corruption
On Sat, Dec 08, 2001 at 08:12:48PM -0800, Mike Erickson wrote: > A few times, I've been going through old mail in one of my mailboxes and > noticed a mail with no subject. Opening it up reveals an entire email > message, headers and all, in the body. I'm using sendmail, procmail, > biff n and mbox format. Is this mutt-related? No, more than likely it's mailx-related. Procmail escapes 'From' lines with that damn '>' symbol, and if you read the mbox with mailx, when it writes it back it treats it as a delimiter and assumes that's where the message body begins. Since it's usually the first or second line of the header, sure enough you're left with no message subject and the rest of the headers plus the real body in the body of the message. The funny thing is that mailx can't properly read a mbox that it's destroyed in this manner either. ^_^ You can get the mailbox back easily enough... go in and delete the added blank lines. I've been about to file a bug against the Debian mailx package for forever about this after I finally figured out what was corrupting my mbox file(s). Poking around in Google leads to the fact that it's a known problem with mailx on a variety of systems and distributions. Debian would call it an RC bug, I'm sure. Great, the Woody freeze is tomorrow and I'm contemplating filing an RC bug. Now, of course, if you never use mailx, then I'm all wet and you have some other problem. ^_^ -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] msg21335/pgp0.pgp Description: PGP signature
mailbox corruption
Hello, A few times, I've been going through old mail in one of my mailboxes and noticed a mail with no subject. Opening it up reveals an entire email message, headers and all, in the body. I'm using sendmail, procmail, biff n and mbox format. Is this mutt-related? I also get a lot of emails, so maybe this is a problem with procmail not locking files? `man procmailrc` gives me: :0 [flags] [ : [locallockfile] ] So I infer that if my :0 lines end with a : they are locking. Mine all do (the recipies that write to a file) so that shouldn't be the problem. Has anyone else had this happen to them? So far it's been fairly benign, but It's scaring me because I depend on my email so much. Also, just for completeness: Mutt 1.2.5i (2000-07-28) Copyright (C) 1996-2000 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: FreeBSD 4.3-RELEASE [using ncurses 5.1] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK -USE_FCNTL +USE_FLOCK +USE_IMAP -USE_GSS -USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS +COMPRESSED SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" -ISPELL To contact the developers, please mail to <[EMAIL PROTECTED]>. To report a bug, please use the muttbug utility. thanks for any help, mike
Re: mailbox corruption
On 2000-07-20 15:42:56 -0400, Michael Soulier wrote: > I still have those examples of mailbox corruption, > if anyone wants to look at them. I'd love to get it > fixed, as I can't seem to predict when it will happen, > or what course of events is necessary to cause it. Several reasons for this to happen should be fixed as of 1.2.4. All these problems were related to disks running full. Do you happen to have insufficient free space in /tmp? -- Thomas Roessler <[EMAIL PROTECTED]>
mailbox corruption
I still have those examples of mailbox corruption, if anyone wants to look at them. I'd love to get it fixed, as I can't seem to predict when it will happen, or what course of events is necessary to cause it. Mike -- Michael P. Soulier, 1Z22, SKY Tel: 613-765-4699 (ESN: 39-54699) Optical Networks, Nortel Networks, SDE Pegasus "...the word HACK is used as a verb to indicate a massive amount of nerd-like effort." -Harley Hahn, A Student's Guide to UNIX Nortel Linux User's Group Ottawa: (internal) http://nlug.ca.nortel.com:8080
Re: Results of corruption test on 1.2 (was: Re: mailbox corruption and mutt)
On Mon, Jun 12, 2000 at 09:17:48AM +0200, Thomas Roessler wrote: > On 2000-06-12 15:46:03 +1000, CaT wrote: > > > Which version of mutt should I try to see if I can > > reporduce this? I've noticed there have been > > official-looking patches about and wanna see if I can > > get this to happen again. > > I think we have already been reproducing what you > describe, and there are some patches already. So, with Yup. Saw the thread. > some luck, there'll be a sane 1.2.1 during this week. Grooovy. > Anyway, thanks for your help. No worries. Sorry about not providing more details but RL thwacked me during the week. :/ -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
Re: Results of corruption test on 1.2 (was: Re: mailbox corruption and mutt)
On 2000-06-12 15:46:03 +1000, CaT wrote: > Which version of mutt should I try to see if I can > reporduce this? I've noticed there have been > official-looking patches about and wanna see if I can > get this to happen again. I think we have already been reproducing what you describe, and there are some patches already. So, with some luck, there'll be a sane 1.2.1 during this week. Anyway, thanks for your help. -- http://www.guug.de/~roessler/
Re: Results of corruption test on 1.2 (was: Re: mailbox corruption and mutt)
On Mon, Jun 05, 2000 at 11:53:51PM +1000, CaT wrote: > On Mon, Jun 05, 2000 at 11:43:22AM +0200, Thomas Roessler wrote: > > On 2000-06-05 10:29:16 +1000, CaT wrote: > > > > > Before attempt: > > > > > -%-Mutt: /tmp/damien.work [Msgs:5492 New:12 Old:1176 Post:1 36M]---(reverse- > > > > > After attempt: > > > > > ---Mutt: /var/spool/mail/damien.work [Msgs:5038 New:9 Old:1074 Post:1 34M]-- > > > > What precisely did happen between these two versions of > > the mail folder? Please be a little bit more precise. ;-) > > Hehe. I'll try tomorrow with a step by step list of what I did > and what happened (well as close to this as I can get :). ATM > I'm dead tired. Bah. Didn't find the time last week. Sorry. 8( Which version of mutt should I try to see if I can reporduce this? I've noticed there have been official-looking patches about and wanna see if I can get this to happen again. -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
Re: mailbox corruption and mutt
On Mon, Jun 05, 2000 at 08:18:56PM +0200, clemensF wrote: > > CaT: > > > Local filesystem for all mailboxes. and erm.. disjunct? > > sorry, i could not find the word and threw in what came up. i mean, can > you guarante that no links, chrooted environments or whatever make > different mailboxes undifferent, i.e. the same file? Ahh. Yes. They're all very different and are seperated out by procmail. Each one has a different intended purpose and all have an inode count of 1. -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
Re: mailbox corruption and mutt
> CaT: > Local filesystem for all mailboxes. and erm.. disjunct? sorry, i could not find the word and threw in what came up. i mean, can you guarante that no links, chrooted environments or whatever make different mailboxes undifferent, i.e. the same file? -- clemens
Re: Results of corruption test on 1.2 (was: Re: mailbox corruption and mutt)
On Mon, Jun 05, 2000 at 11:43:22AM +0200, Thomas Roessler wrote: > On 2000-06-05 10:29:16 +1000, CaT wrote: > > > Before attempt: > > > -%-Mutt: /tmp/damien.work [Msgs:5492 New:12 Old:1176 Post:1 36M]---(reverse- > > > After attempt: > > > ---Mutt: /var/spool/mail/damien.work [Msgs:5038 New:9 Old:1074 Post:1 34M]-- > > What precisely did happen between these two versions of > the mail folder? Please be a little bit more precise. ;-) Hehe. I'll try tomorrow with a step by step list of what I did and what happened (well as close to this as I can get :). ATM I'm dead tired. > > I had both /tmp and /var/spool/mail filled up. I > > selected two msgs for deletion as well as read one > > document. It would not let me quit. > > This almost sounds like reasonable behaviour, as it sounds > like mutt had detected that it couldn't commit the changes > to the mail folder. Yup. But something wrong happened to it's internal picture of the mailbox I think. > Were there any messages about preserved temporary files? Nope. it counted up as it was parsing the maiblox during the save and then whammo, no status message at the bottom and the quit failed. I THINK though that something akin to a status message MAY have flashed instantaneously before my eyes though. > When a folder can't be written back, a temporary file > containing the folder which should have been written > should be left in $TMPDIR. None was left in /tmp and $TMPDIR is not set on my system. I just size sorted the contents and there was nothing there. the youngest tmp file left by mutt was from May 25 and is about 9k in size. It's contents is weird though: Status: O Content-Length: 118 Lines: 4 Status: O Content-Length: 196 Lines: 15 Status: O Content-Length: 1668 Lines: 47 Status: O Content-Length: 149886 Lines: 3372 Status: O Content-Length: 0 Lines: 0 Status: O Content-Length: 0 Lines: 0 Status: O Content-Length: 0 Lines: 0 etc... The file name is: /tmp/mutt.damien-nessie-263 -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
Re: Results of corruption test on 1.2 (was: Re: mailbox corruption and mutt)
On 2000-06-05 10:29:16 +1000, CaT wrote: > Before attempt: > -%-Mutt: /tmp/damien.work [Msgs:5492 New:12 Old:1176 Post:1 36M]---(reverse- > After attempt: > ---Mutt: /var/spool/mail/damien.work [Msgs:5038 New:9 Old:1074 Post:1 34M]-- What precisely did happen between these two versions of the mail folder? Please be a little bit more precise. ;-) > I had both /tmp and /var/spool/mail filled up. I > selected two msgs for deletion as well as read one > document. It would not let me quit. This almost sounds like reasonable behaviour, as it sounds like mutt had detected that it couldn't commit the changes to the mail folder. Were there any messages about preserved temporary files? When a folder can't be written back, a temporary file containing the folder which should have been written should be left in $TMPDIR. -- http://www.guug.de/~roessler/
Re: Results of corruption test on 1.2 (was: Re: mailbox corruption and mutt)
Hi CaT! On Mon, 05 Jun 2000, CaT wrote: > I had both /tmp and /var/spool/mail filled up. I selected two msgs for > deletion as well as read one document. It would not let me quit. I > trie dit multiple times. I freed up space on /var/spool/mail so that it > has 160meg free and it still would not let me quit. I freed up space > on /tmp so that it has 92meg free and it let me quit. > > 8( Would you run into a quota problem if you set tmpdir $HOME/tmp? That would get around the issue of somebody else filling up /tmp. -- _ _|_|_ ( ) *Anton Graham /v\ / <[EMAIL PROTECTED]> /( )X (m_m) GPG ID: 18F78541 Penguin Powered!
Results of corruption test on 1.2 (was: Re: mailbox corruption and mutt)
On Sun, Jun 04, 2000 at 07:29:53PM +0300, Mikko Hänninen wrote: > CaT <[EMAIL PROTECTED]> wrote on Sun, 04 Jun 2000: > > Ok.. NOW I'm using 1.2. Grr. Compiled 1.2, went to play > > with my bros on their nintendo, came back and forgot I > > didn't install :) > > And the result of trying to re-create the problem with 1.2 is ..? Before attempt: -%-Mutt: /tmp/damien.work [Msgs:5492 New:12 Old:1176 Post:1 36M]---(reverse- After attempt: ---Mutt: /var/spool/mail/damien.work [Msgs:5038 New:9 Old:1074 Post:1 34M]-- I had both /tmp and /var/spool/mail filled up. I selected two msgs for deletion as well as read one document. It would not let me quit. I trie dit multiple times. I freed up space on /var/spool/mail so that it has 160meg free and it still would not let me quit. I freed up space on /tmp so that it has 92meg free and it let me quit. 8( -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
Re: mailbox corruption and mutt
On Sun, Jun 04, 2000 at 09:52:48PM +0200, clemensF wrote: > > CaT: > > > I'm using several mutts but they're all on a different mailbox. > > mailboxes accessed by some nfs? really every mailbox disjunct? Local filesystem for all mailboxes. and erm.. disjunct? -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
Re: mailbox corruption and mutt
> CaT: > I'm using several mutts but they're all on a different mailbox. mailboxes accessed by some nfs? really every mailbox disjunct? -- clemens
Re: mailbox corruption and mutt
CaT <[EMAIL PROTECTED]> wrote on Sun, 04 Jun 2000: > Ok.. NOW I'm using 1.2. Grr. Compiled 1.2, went to play > with my bros on their nintendo, came back and forgot I > didn't install :) And the result of trying to re-create the problem with 1.2 is ..? Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / "I'm having an out of mind experience."
Re: mailbox corruption and mutt
On 2000-06-04 20:44:26 +1000, CaT wrote: > X-Mailer: Mutt 1.0i hmmm... > Well if you check my X-Mailer header now... :) -- http://www.guug.de/~roessler/
Re: mailbox corruption and mutt
On Sun, Jun 04, 2000 at 11:08:57AM +0200, Thomas Roessler wrote: > On 2000-06-04 16:32:44 +1000, CaT wrote: > > > for example this is one message in the mailbox that is > > currupt. Not that it consists of virtually missing > > headers and that it is two messages concatenated into > > one. And even then the message bodies are incomplete > > and the body of the first message does not belong to > > the mailing list the From_ field says it does. That > > body belongs with completly different messages. > > This sounds quite fascinating, and certainly should not > happen. > > However, I believe I put some more paranoia code for > out-of-space conditions into 1.2, so it would be really > nice if you could upgrade to that version and reproduce > the bug there. You may even have chances that someone > will fix the problem for you when it's in that code base. > http://www.guug.de/~roessler/ Ok.. NOW I'm using 1.2. Grr. Compiled 1.2, went to play with my bros on their nintendo, came back and forgot I didn't install :) -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
Re: mailbox corruption and mutt
On Sun, Jun 04, 2000 at 11:08:57AM +0200, Thomas Roessler wrote: > On 2000-06-04 16:32:44 +1000, CaT wrote: > > > for example this is one message in the mailbox that is > > currupt. Not that it consists of virtually missing > > headers and that it is two messages concatenated into > > one. And even then the message bodies are incomplete > > and the body of the first message does not belong to > > the mailing list the From_ field says it does. That > > body belongs with completly different messages. > > This sounds quite fascinating, and certainly should not > happen. Agreed. :) > However, I believe I put some more paranoia code for > out-of-space conditions into 1.2, so it would be really > nice if you could upgrade to that version and reproduce > the bug there. You may even have chances that someone > will fix the problem for you when it's in that code base. Well if you check my X-Mailer header now... :) Just upgraded to 1.2. :) -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
Re: mailbox corruption and mutt
On Sun, Jun 04, 2000 at 11:19:46AM +0200, clemensF wrote: > are you using several mutt windows in a gui or mbox formatted mailboxes > without locked access? I'm using several mutts but they're all on a different mailbox. -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
Re: mailbox corruption and mutt
> Thomas Roessler: > than maildir for large mailboxes. Just imagine a rather > traditional Unix file system design having to deal with > 7k5 files in _one_ directory... this might trouble the traditional linux (linear search) fs. -- clemens
Re: mailbox corruption and mutt
On 2000-06-03 23:42:17 -0700, Anton Graham wrote: > I would guess that your problem stems, in part, from > the fact that the mbox format is not really designed > for a 47 meg box with 7500+ messages. Personally, I have mbox folders with several 1e5 messages, and have not experienced any problems with them. I'm using ~/.tmp as my TMPDIR, though, so there is generally far more than enough free space in that directory. Actually, you may wish to notice that, depending on your file system implementation, mbox may be far more efficient than maildir for large mailboxes. Just imagine a rather traditional Unix file system design having to deal with 7k5 files in _one_ directory... -- http://www.guug.de/~roessler/
Re: mailbox corruption and mutt
On 2000-06-04 16:32:44 +1000, CaT wrote: > for example this is one message in the mailbox that is > currupt. Not that it consists of virtually missing > headers and that it is two messages concatenated into > one. And even then the message bodies are incomplete > and the body of the first message does not belong to > the mailing list the From_ field says it does. That > body belongs with completly different messages. This sounds quite fascinating, and certainly should not happen. However, I believe I put some more paranoia code for out-of-space conditions into 1.2, so it would be really nice if you could upgrade to that version and reproduce the bug there. You may even have chances that someone will fix the problem for you when it's in that code base. -- http://www.guug.de/~roessler/
Re: mailbox corruption and mutt
are you using several mutt windows in a gui or mbox formatted mailboxes without locked access? -- clemens
Re: mailbox corruption and mutt
On Sun, Jun 04, 2000 at 12:38:35PM +0530, Suresh Ramasubramanian wrote: > CaT proclaimed on mutt-users that: > > >Ok. Not to be faceatous(sp?) or anything... just being curious :) What > >will this prove/solve/whatnot? I may have missed out on a bit of info > >in that, from memory, if I clear /tmp then it eventually safes (albeit > >in an icky corrupted manner). > > > >Anyways, just trying to find out why I may be about to do something :) > > ---end quote--- > > I'm betting that this crashing is because your maildir is running out of > space, or your tmpdir is full of junk that needs to be cleared. It'd be /tmp from memory. This needs to be solved because it makes mutt potentially painful in a multi-user environment. For eg: User A runs mutt with a big mailbox User B runs an app that just filled up /tmp to near capacity User A tries to quit mutt. Waits patiently, putt gets to 99% and then fails silently. User B's usage of /tmp deminishes to sane levels User A goes 'Hrm. Bloody Heck' and tries again. This time mutt succeeds and overwrites his mailbox with a corrupt version User A comes back later on to find half his mailbox fragged and curses the name of mutt. User B parties in ignorance. ;) As for /var/spool/mail, it had the room (this is from distantish memory now... it's been a fortnight since I first made my report so I'm anout 98% confident). /tmp was rather closeish to full from memory. (around 30meg free at one time and 11meg at another time). -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
Re: mailbox corruption and mutt
Anton Graham proclaimed on mutt-users that: >I would guess that your problem stems, in part, from the fact that the >mbox format is not really designed for a 47 meg box with 7500+ >messages. I would seriously consider saving some of those messages in So which is the best one? Here at the Juno postmaster desk, we use mh folders, it works really well (with huge volumes of mail everyday). ---end quote--- -- Suresh Ramasubramanian | sureshr at staff.juno.com My theology, briefly, is that the universe was dictated but not signed. -- Christopher Morley
Re: mailbox corruption and mutt
On Sun, 04 Jun 2000, CaT wrote: > I don't suppose I have a hope in getting any sort of responce to this? > > It is kinda important and I'd be more then happy to help track down the > problem but at the moment I've gotten SFA responce to it which may mean > that noone really cares if mutt corrupts mailboxes. I would guess that your problem stems, in part, from the fact that the mbox format is not really designed for a 47 meg box with 7500+ messages. I would seriously consider saving some of those messages in other mailboxes. This would help alleviate this problem and undoubtedly make finding specific messages easier. Personally, I have a cron job that runs at midnight on the first of each month which moves all of my mail storage into an archive directory and compresses the boxes. This prevents overly large mailboxes. -- _ _|_|_ ( ) *Anton Graham /v\ / <[EMAIL PROTECTED]> /( )X (m_m) GPG ID: 18F78541 Penguin Powered!
Re: mailbox corruption and mutt
CaT proclaimed on mutt-users that: >Ok. Not to be faceatous(sp?) or anything... just being curious :) What >will this prove/solve/whatnot? I may have missed out on a bit of info >in that, from memory, if I clear /tmp then it eventually safes (albeit >in an icky corrupted manner). > >Anyways, just trying to find out why I may be about to do something :) ---end quote--- I'm betting that this crashing is because your maildir is running out of space, or your tmpdir is full of junk that needs to be cleared. -- Suresh Ramasubramanian | sureshr at staff.juno.com My theology, briefly, is that the universe was dictated but not signed. -- Christopher Morley
Re: mailbox corruption and mutt
On Sun, Jun 04, 2000 at 12:13:38PM +0530, Suresh Ramasubramanian wrote: > CaT proclaimed on mutt-users that: > > >Mutt does corrupt if it cannot recover from this situation without > >corrupting the mailbox. It's not that the mailbox is saved, intact > > It should _not_ find itself in such a situation. Tell you what - move Aye. But it does 8(. > your mailboxes to another partition and create symlinks. > > Something like this (btw, first change to single-user mode by logging in > as su. so nobody else uses the mail program at that time) Ok. Not to be faceatous(sp?) or anything... just being curious :) What will this prove/solve/whatnot? I may have missed out on a bit of info in that, from memory, if I clear /tmp then it eventually safes (albeit in an icky corrupted manner). Anyways, just trying to find out why I may be about to do something :) -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
Re: mailbox corruption and mutt
CaT proclaimed on mutt-users that: >Mutt does corrupt if it cannot recover from this situation without >corrupting the mailbox. It's not that the mailbox is saved, intact It should _not_ find itself in such a situation. Tell you what - move your mailboxes to another partition and create symlinks. Something like this (btw, first change to single-user mode by logging in as su. so nobody else uses the mail program at that time) #Copy the files from /var/spool/mail to /new1/mail #(new1 on a different partition) cp -rp /var/spool/mail /new1 #(-rp = recursive preserve) # use chown on each file, making everything # identical to the original directories. cp -rp /var/spool/mqueue /new1 chown username filename # Remove the original files cd /var/spool rm -rf mqueue rm -rf mail #soft links ln -s /var/spool/mqueue /new1/mqueue ln -s /var/spool/mail /new1/mail # reboot shutdown -r now -- Suresh Ramasubramanian | sureshr at staff.juno.com My theology, briefly, is that the universe was dictated but not signed. -- Christopher Morley
Re: mailbox corruption and mutt
On Sun, Jun 04, 2000 at 11:49:40AM +0530, Suresh Ramasubramanian wrote: > CaT proclaimed on mutt-users that: > > >I don't suppose I have a hope in getting any sort of responce to this? > > Let me see .. > > >It is kinda important and I'd be more then happy to help track down the > >problem but at the moment I've gotten SFA responce to it which may mean > >that noone really cares if mutt corrupts mailboxes. > > Short answer - mutt doesn't corrupt mailboxes. You are running out of > disk space, or have a flaky hdd, or your TMPDIR is in the wrong place. Mutt does corrupt if it cannot recover from this situation without corrupting the mailbox. It's not that the mailbox is saved, intact but shorter but rather the individual msg headers are totally rooted for most of the messages when mutt finds it cannot safe the mailbox. I'm not suffering from an amputation of the end of a mailbox. I'm suffering fromt he corruption of mailbox internals.ie the actual individual msgs get turned into bits and pieces. for example this is one message in the mailbox that is currupt. Not that it consists of virtually missing headers and that it is two messages concatenated into one. And even then the message bodies are incomplete and the body of the first message does not belong to the mailing list the From_ field says it does. That body belongs with completly different messages. --- message starts --- >From [EMAIL PROTECTED] Sat Mar 18 22:20:35 20 Status: RO Content-Length: 3004 Lines: 31 s On again! And it's not too late to join in!! >From [EMAIL PROTECTED] Sat Mar 18 Status: RO Content-Length: 14302 Lines: 434 am unsure why I need an account with you. I guess a technical --- message ends -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
Re: mailbox corruption and mutt
CaT proclaimed on mutt-users that: >I don't suppose I have a hope in getting any sort of responce to this? Let me see .. >It is kinda important and I'd be more then happy to help track down the >problem but at the moment I've gotten SFA responce to it which may mean >that noone really cares if mutt corrupts mailboxes. Short answer - mutt doesn't corrupt mailboxes. You are running out of disk space, or have a flaky hdd, or your TMPDIR is in the wrong place. Try this - go to /tmp and nuke mutt-* (which sometimes get left there when mutt crashes or dumps core). Run e2fsck on your hdd (assuming it is a linux box) - and read the howto first :) Free some space on the partition where your /var/spool/mail is -- Suresh Ramasubramanian | sureshr at staff.juno.com My theology, briefly, is that the universe was dictated but not signed. -- Christopher Morley
Re: mailbox corruption and mutt
I don't suppose I have a hope in getting any sort of responce to this? It is kinda important and I'd be more then happy to help track down the problem but at the moment I've gotten SFA responce to it which may mean that noone really cares if mutt corrupts mailboxes. On Tue, May 23, 2000 at 09:23:14PM +1000, CaT wrote: > On Tue, May 23, 2000 at 10:10:07AM +1000, CaT wrote: > > well I just had my mailbox corrupted for the second time by mutt 8( > > > > this happens when I try to quit, mutt finds there's not enough room > > in /tmp and so doesn't let me. What winds up happening is that once > > I do get a chance to quit properly (as opposed to exit) mutt saves > > the mailbox with a large chunk of messages with corrupt headers. :/ > > > > As you can guess, this rather sucks. > > > > Has this been previously reported and fixed? I could try and provide > > more info but I'll need to know what is required. > > > > My system is Linux 2.2.15pre18 (but it's happened with older versions > > previously), glibc 2.1.3 (but it happened with 2.1.2). The mailbox > > is 47meg in size with 7624 msgs. > > Forgot to add that it's Mutt 1.0i (for those who don't look at headers :) > > -- > CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null > > 'He had position, but I was determined to score.' > -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...' -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
Re: mailbox corruption and mutt
On Tue, May 23, 2000 at 10:10:07AM +1000, CaT wrote: > well I just had my mailbox corrupted for the second time by mutt 8( > > this happens when I try to quit, mutt finds there's not enough room > in /tmp and so doesn't let me. What winds up happening is that once > I do get a chance to quit properly (as opposed to exit) mutt saves > the mailbox with a large chunk of messages with corrupt headers. :/ > > As you can guess, this rather sucks. > > Has this been previously reported and fixed? I could try and provide > more info but I'll need to know what is required. > > My system is Linux 2.2.15pre18 (but it's happened with older versions > previously), glibc 2.1.3 (but it happened with 2.1.2). The mailbox > is 47meg in size with 7624 msgs. Forgot to add that it's Mutt 1.0i (for those who don't look at headers :) -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
mailbox corruption and mutt
well I just had my mailbox corrupted for the second time by mutt 8( this happens when I try to quit, mutt finds there's not enough room in /tmp and so doesn't let me. What winds up happening is that once I do get a chance to quit properly (as opposed to exit) mutt saves the mailbox with a large chunk of messages with corrupt headers. :/ As you can guess, this rather sucks. Has this been previously reported and fixed? I could try and provide more info but I'll need to know what is required. My system is Linux 2.2.15pre18 (but it's happened with older versions previously), glibc 2.1.3 (but it happened with 2.1.2). The mailbox is 47meg in size with 7624 msgs. -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
