On Sun, 2010-01-10 at 15:16 -0500, Justin Piszcz wrote:

Jan 2 09:33:25 l1 dovecot: IMAP(user): Next message unexpectedly corrupted in mbox file /home/user/Mailbox at 10599

If this doesn't keep happening, I think you should just ignore it. There's not much that can be done about it unless I can figure out a way to reproduce it..

Did dovecot 1.2.9 include this patch: http://www.dovecot.org/list/dovecot-cvs/2009-December/015177.html

So now one sees the message, whereas before, no message was shown?

Right.

Justin Piszcz ha scritto:

Package: dovecot-imapd Version: 1.2.9-1 Distribution: Debian Testing x86_64

Problem: See below.

..

Looking further I found this (which is when the problem began to appear in the logs):

First time: Jan 2 09:33:25 l1 dovecot: IMAP(user): Next message unexpectedly corrupted in mbox file /home/user/Mailbox at 10599

Due to:

2010-01-02 05:00:29 configure dovecot-common 1:1.2.9-1 1:1.2.9-1 2010-01-02 05:00:29 status unpacked dovecot-common 1:1.2.9-1 2010-01-02 05:00:29 status unpacked dovecot-common 1:1.2.9-1 2010-01-02 05:00:29 status unpacked dovecot-common 1:1.2.9-1 2010-01-02 05:00:29 status unpacked dovecot-common 1:1.2.9-1 2010-01-02 05:00:29 status unpacked dovecot-common 1:1.2.9-1 2010-01-02 05:00:29 status unpacked dovecot-common 1:1.2.9-1 2010-01-02 05:00:29 status half-configured dovecot-common 1:1.2.9-1 2010-01-02 05:00:31 status installed dovecot-common 1:1.2.9-1

2010-01-02 05:00:38 configure dovecot-imapd 1:1.2.9-1 1:1.2.9-1 2010-01-02 05:00:38 status unpacked dovecot-imapd 1:1.2.9-1 2010-01-02 05:00:38 status half-configured dovecot-imapd 1:1.2.9-1 2010-01-02 05:00:38 status installed dovecot-imapd 1:1.2.9-1

During an apt-get dist-upgrade..

Did dovecot 1.2.9 include this patch: http://www.dovecot.org/list/dovecot-cvs/2009-December/015177.html

So now one sees the message, whereas before, no message was shown? Nothing to be concerned about?

Justin.

On Fri, 8 Jan 2010, Justin Piszcz wrote:

...

Hi,

t> I am seeing this on one of my servers:

...

Jan 8 10:08:58 l1 dovecot: IMuser(user): Next message unexpectedly corrupted in mbox file /home/user/Mailbox at 10558

I have never seen this before, and google yields no results except when this warning was added to the source code here: http://www.dovecot.org/list/dovecot-cvs/2009-December/015177.html

The user has deleted all of the mail in the Mailbox but the problem persists.

Any ideas?

Justin.

Hi Justin, Does the problem persist? Does it cause glitches for the user? Does it cause some corruptions or it's just a line in your log? Is it reproducible?

I think it is some kind of corruption of the mailbox, but I found weird it persists after the deletion of all email. May be you should expunge deleted messages from the mailbox.

Kind regards, Marco

--

| Marco Nenciarini | Debian/GNU Linux Developer - Plug Member | | mnencia@prato.linux.it | http://www.prato.linux.it/~mnencia |

Key fingerprint = FED9 69C7 9E67 21F5 7D95 5270 6864 730D F095 E5E4

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Fri, 5 Feb 2010, Justin Piszcz wrote:

I believe it is due to a lock/race condition with the Mailbox format, when you have alpine open (accessing the Mailbox) and an external client, e.g. Outlook

You are accessing the same mailbox locally with (Al)Pine and externally via Dovecot? Then you have to stop doing so and configure Pine to use IMAP, too, or configure Dovecot to use the same locking mechanism, which probably does not work with shared filesystems.

See: http://wiki.dovecot.org/MboxLocking

or thunderbird. Yes, when both clients access the mailbox it usually locks up Outlook or alpine.. I suppose the maildir format may be the better option but alpine has issue with that format.?

Alpine does not support local access to Maildir.

If you prefer local access to the mailbox, switch to mutt, which supports Maildir. There is no locking problem with Maildir.

Regards,

Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBS2/Yo7+Vh58GPL/cAQIgqQf/VE/9mAHMTt7VFNGJYkWrPuY/urcHeQTR vanNrUjG15h6vcR7Xd73OUBjy/uj2ranuodHVaVFRD06nPxia0kld93VBiVISAXK Q98LlSYQJmEW1Y29yl0a9UZUFizZl7MLYDo81WzkgErApSlNMcq9k+A599W8jl7S ITsly3MYavAU47h6+YKUsF8apT9dPhnYFcueqZJRcnkBBhNRaG8l1BCJZwrxXe9X GGgAVsaL/EJS7+lszRh7bk5GTx/5Onx/m+i/2/yZFqpNcn/OSVIJd7SHDULuU+u2 +Gjkj0C+yOxkiluo1lAmldNpY5LDUNjHAmt044/VngIKQLGf6ewDCw== =wAgL -----END PGP SIGNATURE-----

Hi,

I have not tried that, will try it and get back to you. (dovecot.index*) files. Thanks!

Justin.

On Sun, 24 Jan 2010, Timo Sirainen wrote:

On Fri, 2010-01-08 at 10:12 -0500, Justin Piszcz wrote:

...

I am seeing this on one of my servers: Jan 8 10:08:58 l1 dovecot: IMuser(user): Next message unexpectedly corrupted in mbox file /home/user/Mailbox at 10558

I have never seen this before, and google yields no results except when this warning was added to the source code here: http://www.dovecot.org/list/dovecot-cvs/2009-December/015177.html

The user has deleted all of the mail in the Mailbox but the problem persists.

Oh, you can reproduce it easily? If all mails were deleted, I'd think the offset at least changes? What about if you delete dovecot.index* files?