Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 429100

Summary:	Thunderbird IMAP with Dovecot gives "Invalid Messageset" Error
Product:	Red Hat Enterprise Linux 4	Reporter:	David Tonhofer <bughunt>
Component:	dovecot	Assignee:	Michal Hlavinka <mhlavink>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	4.6	CC:	dhorak
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-09-22 14:51:15 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Tonhofer 2008-01-17 10:33:15 UTC

Description of problem:

I have been bitten by the problem described in link below, rather quickly after
installation of dovecot I must say. 

I use dovecot and Thunderbird. Thunderbird accesses mail through SSL-ed IMAP.
MTA is postfix. We have mbox format (gonna be changed soon). 

So, at 

http://blog.tcg.com/tcg/2007/02/dovecot_invalid.html

we read:

"Though working for a long time, while trying to read their mail, two of our
Thunderbird IMAP users suddenly received the error: "The current command did not
succeed.  The mail server responded: Invalid messageset: -2147483648:*."

A bit of research revealed that Dovecot versions 0.99.13 and earlier have an
interesting bug in which the X-UID header for emails can get too large, and
therefore cannot be processed by Dovecot."

This is difficult to reproduce, but the fix is in. Suppose the user is
"mail-0214", then we just need to filter the X-UID and X-IMAPbase headers out of
the INBOX (or some other affected mbox file), then something similar to this
will help:

cp mail-0214 mail-0214.bak
/etc/rc.d/init.d/dovecot stop
cat mail-0214.bak  | grep -v '^X-UID: ' | grep -v "^X-IMAPbase: " > mail-0214.new
/bin/cp mail-0214.new mail-0214
chmod 600 mail-0214 && chown mail-0214:mail mail-0214
/bin/rm -rf mbox_mail-0214/.imap/INBOX
/etc/rc.d/init.d/dovecot start

Comment 1 David Tonhofer 2008-01-20 21:11:46 UTC

Happens often. I will "upgrade" to a self-compiled dovecot-1.0.10 to see whether
that fixes the problem.

Apparently this is more a Thunderbird than a dovecot problem.

Comment 2 Dan Horák 2008-06-10 07:55:54 UTC

Did you the upgrade? We have a workaround in bug #449125, which seems to be
exactly the same problem as you have.

Comment 3 David Tonhofer 2008-09-17 08:31:12 UTC

Yes, the upgrade to dovecot-1.0.10 worked well, no problems encountered. At some point, the machine running this will be upgrade RH4 -> RH5, we will see what the dovecot with RH5 does.

Comment 4 Dan Horák 2008-09-18 07:50:08 UTC

But be careful because since RHEL 5.2 we have dovecot 1.0.7 and I don't think it is possible to go from 1.0.10 back to 1.0.7.

Comment 5 Michal Hlavinka 2008-09-22 14:51:15 UTC


*** This bug has been marked as a duplicate of bug 449125 ***