similar to: AppleMail causes dovecot error: file mbox-rewrite.c: line 429 assertion failed

Feb 1 20:13:15 myhost imap(someuser): file mbox-rewrite.c: line 429 (mbox_write_header): assertion failed: (hdr_parsed_size.physical_size == hdr_size) I'm using Fedora Core 4, dovecot 0.99.14-4. Any idea? How to fix this problem? Thanks a lot, Cl?vis -- Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola Administrador de Redes - Secao de Informatica (SINFO) E-mail: mailto:clovis at

I've noticed a burst of about 12000 of these mbox-rewrite msgs in the log, spread over about 10 minutes. They are always for the same person (XXX'd out here), and have not occurred before or since. There's no evidence of device problems in the message log. Jan 10 17:46:43 ls1 imap-login: Login: XXX [::ffff:10.2.0.1] Jan 10 17:46:43 ls1 imap(XXX): file mbox-rewrite.c: line 429

Hi, I did a bit of digging into the assertions from mbox-rewrite.c (hdr_parsed_size.physical_size == hdr_size). Every time it happens, hdr_size is 0, while hdr_parsed_size.physical_size is non-zero (presumably the correct value). Does this help track it down? I can't manage to get hold of an mbox that causes this though. Another infrequent assertion that's popped up: file

Hi, Folks, I recently migrated from courier-imapd to dovecot when I migrated a machine from rh9 to fc5. I managed to hit a snag with the 1.0b8 version of dovecot that's currently in fc5. With AppleMail 1.3 I was seeing most of my incoming mail go missing. To make a long story short, AppleMail was applying mail filters inappropriately (walking right past a 'stop processing'

Hi, I am using dovecot-0.99.14-8.fc4 in Fedora Core release 4 (Stentz), and is appears this message: maillog -------- imap(testelabin): file mbox-rewrite.c: line 429 (mbox_write_header): assertion failed: (hdr_parsed_size.physical_size == hdr_size) When I try to have access a very great mailbox(mbox) (99 MB) via Webmail SquirrelMail. My quota of record is of 250 MB, some suggestion? Thanks a

2009/7/9 Adam Rosi-Kessel <adam at rosi-kessel.org>: > Adam Rosi-Kessel wrote, on 6/30/2009 11:14 AM: >> >> Conrad Parker wrote, on 6/30/2009 11:05 AM: >>>> >>>> http://adam.rosi-kessel.org/bugs/liboggz/484/other_corruption.ogg >>>> Yet also won't play or process properly with oggz or hogg tools. Any >>>> ideas whether this

Adam Rosi-Kessel wrote, on 6/19/2009 3:56 PM: > Conrad Parker wrote, on 6/18/2009 3:15 PM: >> Hopefully at some point the vorbis data in the file becomes valid. >> Perhaps we just need to know the original encoding settings to create >> a new file with valid codebooks and splice them together: oggz-dump -r >> should be ok for that, just take the first 3 packets of the

2009/6/30 Adam Rosi-Kessel <adam at rosi-kessel.org>: > Monty Montgomery wrote, on 6/25/2009 2:16 PM: >>> Is there any way to understand exactly how it is invalid? I can replicate >>> this corruption simply by adding large album art to any ogg file with the >>> latest release of MediaMonkey. >> The second page is corrupt. ?The basic structure looks

Adam Rosi-Kessel <adam at rosi-kessel.org> wrote: > So I've written a script to do the following: ... I have got lost. Did you manage to identify the rogue software that corrupted the files in the first place? In the greater scheme of things, fixing this (prevention) is more important than repairing the files (cure). Regards, Martin -- Martin J Leese E-mail: martin.leese

On Tue, Jul 14, 2009 at 9:48 AM, Adam Rosi-Kessel<adam at rosi-kessel.org> wrote: > The only issue I'm noticing is ogginfo reports: > > Warning: sequence number gap in stream 1. Got page 14 when expecting > page 2. Indicates missing data. > Warning: discontinuity in stream (1) I'd guess this is flagging the data that was overwritten by the bad tagging code. Some

Hi, (I was discussing this with Adam earlier today, and he has also mailed vorbis at xiph.org about this issue in March). This sounds like it needs a new tool specifically for fixing broken Ogg files. Suggestions so far (tried by Adam, or suggested to him in email/IRC): * oggz-sort, hogg sort These rewrite the file, sorting the pages by presentation time. This usually fixes muxing problems,

Adam Rosi-Kessel wrote, on 6/30/2009 11:14 AM: > Conrad Parker wrote, on 6/30/2009 11:05 AM: >>> http://adam.rosi-kessel.org/bugs/liboggz/484/other_corruption.ogg >>> Yet also won't play or process properly with oggz or hogg tools. Any >>> ideas whether this is the same or different root cause? (In all of these >>> cases, I'm reasonably certain that

2009/6/18 Adam Rosi-Kessel <adam at rosi-kessel.org>: > On Thu, Jun 18, 2009 at 11:12:30PM +0900, Conrad Parker wrote: >> yow, that's pretty badly corrupted, the vorbis codebooks (usually the >> third packet) is completely gone. It looks like you'd need to throw >> away the first 16 packets, start with fresh headers, and copy in the >> rest of the data

2009/6/18 Adam Rosi-Kessel <adam at rosi-kessel.org>: > Ivo Emanuel Gon?alves wrote, on 6/18/2009 6:14 AM: >> >> On 6/18/09, Conrad Parker<conrad at metadecks.org> ?wrote: >>> >>> This sounds like it needs a new tool specifically for fixing broken >>> Ogg files. >> >> I see two solutions: >> >> 1) the new vcut which I

Please cc me on replies. My employer recently upgraded to W2K3. I have no control over the employer's set up and limited access to information. Under the old server, everything was working fine. Now I can't mount the shared drive anymore. I'm running Debian sid; samba 3.0.6-3. ################################################ # mount shared_drive cli_negprot: SMB signing is

2009/7/18 Adam Rosi-Kessel <adam at rosi-kessel.org>: > On Fri, Jul 17, 2009 at 12:48:27PM -0700, Ralph Giles wrote: >> > In my ongoing quest to restore corrupted ogg files, I'm trying to find >> > an easy way to identify the setup header without having to actually >> > decode it. I understand that it starts with [packet_type] = 5 and then >> > the

On Sat, Jul 18, 2009 at 10:23:21AM +0900, Conrad Parker wrote: > 2009/7/18 Adam Rosi-Kessel <adam at rosi-kessel.org>: > > On Fri, Jul 17, 2009 at 12:48:27PM -0700, Ralph Giles wrote: > >> > In my ongoing quest to restore corrupted ogg files, I'm trying to find > >> > an easy way to identify the setup header without having to actually > >> >

Martin Leese wrote, on 7/15/2009 3:29 PM: > Adam Rosi-Kessel<adam at rosi-kessel.org> wrote: > >> So I've written a script to do the following: > ... > > I have got lost. Did you manage to identify the > rogue software that corrupted the files in the > first place? In the greater scheme of things, > fixing this (prevention) is more important than >

Adam Rosi-Kessel <adam at rosi-kessel.org> wrote: > I finally got something like an explanation from the Mediamonkey > developers. Here is their explanation as to why MM corrupted my files: > > > the problem was caused by the fact that Vorbis library uses alloca() > > function on several places, which allocates memory on stack. We > > changed it to alloc() and

Hi. I have two questions that don't appear to be answered anywhere: - Many of my users use a fetchmail ssh tunnel to get their mail. Typically this looks like poll 140.247.60.120 with proto imap: plugin "ssh -2 %h /usr/sbin/imapd" auth ssh; uw-imapd provides a binary /usr/sbin/imapd that can be used for an ssh-imap tunnel. I found /usr/lib/dovecot/imap (in