http://bugzilla.suse.com/show_bug.cgi?id=918705
Bug ID: 918705 Summary: alpine locking failure (against procmail) leads to mail corruption Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: gp@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: ---
This is something I started to see a bit ago, and since it now happened twice today I figured I'd report it.
When I obtain mail via fetchmail, using procmail as the delivery agent, occasionally I get corrupted mails like the following (in mbox format):
==== snip ====
From gp Thu Feb 19 18:56:54 2015
Mime-Version: 1.0 Date: Thu, 19 Feb 2015 18:56:00 +0100 Subject: AW: Re: Your help needed: Fwd: Comment opportunity: Software Status: RO X-Status: X-Keywords: X-UID: 9310
definedstorage Subject: AW: Re: Your help needed: Fwd: Comment opportunity: Software
definedstorage References: 54E302D90200006F00158C8B@suse.com 54E2D72A0200002B000A1B55@suse.com 54E339FA0200006F00158DBD@suse.com 54E2D7DE0200002B000A1B68@suse.com alpine.LSU.2.11.1502191739290.2252@ghan.fvgr In-Reply-To: alpine.LSU.2.11.1502191739290.2252@ghan.fvgr Message-ID: 54E623B70200006F001594A6@suse.com From: ... To: "Gerald Pfeifer" gp@suse.com ==== snap ====
This does not happen daily, and I believe it happens especially when I have been offline for several hours and a few dozen e-mails are delivered at once (though this specific case was not that).
The same configuration had been working for years without ever showing this problem, and it looks like looking on the Alpine side (or procmail, though less likely I guess, since it essentially only reads :0 INBOX )
http://bugzilla.suse.com/show_bug.cgi?id=918705
Gerald Pfeifer gp@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(gp@suse.com) |
--- Comment #7 from Gerald Pfeifer gp@suse.com --- I had a single corruption since reporting this and adjusting my procmail rules, so this is not rampant, but apparently still there appears to be a bit of an issue.
A few days ago I updated to Alpine 2.20, let's see whether I run into this with that version at all?
http://bugzilla.suse.com/show_bug.cgi?id=918705
--- Comment #8 from Gerald Pfeifer gp@suse.com --- Unfortunately this is still happening. I had at least three occurrences the last week, usually after I had been offline for several (peak) hours and then received a lot of mails -- which is a strong indication that we are looking at locking issues.
For reference, here is the current procmail rule I am using:
:0: INBOX
And here is one of those mails as it landed in my inbox:
From gp Mon May 11 11:47:44 2015 Mime-Version: 1.0 X-Mailer: GroupWise 2014 SP1 Date: Mon, 11 May 2015 16:59:08 +0200 Subject: RE: Panel at Summit (was: SUSE Overview session for MF sellers at Status: RO X-Status: X-Keywords: X-UID: 9497
Summit) Subject: RE: Panel at Summit (was: SUSE Overview session for MF sellers at
Summit) References: 55411433020000380015F956@suse.com alpine.LSU.2.20.1504300133211.1897@ghan.fvgr 55411B23020000380015F961@suse.com alpine.LSU.2.20.1505110152180.2744@ghan.fvgr In-Reply-To: alpine.LSU.2.20.1505110152180.2744@ghan.fvgr Message-ID: 55506EC90200003800161308@suse.com From: ... To: "Gerald Pfeifer" gp@suse.com
Observe how the multi-line Subject: header is duplicated, and the four headers (Status, X-Status, X-Keywords, X-UID) that Alpine adds are in between.
http://bugzilla.suse.com/show_bug.cgi?id=918705 http://bugzilla.suse.com/show_bug.cgi?id=918705#c12
Richard Biener rguenther@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |rguenther@suse.com Resolution|FIXED |---
--- Comment #12 from Richard Biener rguenther@suse.com --- I'm now experiencing this regularly multiple times a day. This is with Leap 42.2 which has alpine-2.20-11.32.x86_64 and procmail-3.22-268.23.x86_64.
Somehow this is a more recent issue (since the last 10 days?) but neither alpine nor procmail changed inbetween.
Note that the mboxen I use reside on NFS storage and I am running 4.4.87-18.29-default (so I guess it happens since the power outage which triggered a reboot...). Which means it somehow didn't happen with 4.4.74-18.20 which should have been the kernel running before.
Documentation tells me that procmail uses fcntl style locking (in addition to lockfiles?).
Yes, all affected mboxen are configured as incoming folders for alpine.
Usually apline closes the folders with an access error but I have now twice seen corrupted display of mails from within alpine (second mail displayed within first, spaced by what seems to be a block of zero bytes).
https://bugzilla.suse.com/show_bug.cgi?id=918705 https://bugzilla.suse.com/show_bug.cgi?id=918705#c13
--- Comment #13 from Reinhard Max max@suse.com --- @Gerad @Richard As this bug has been rotting for quite a while and alpine has seen several upgrades since, I'd like to hear if these corruptions are still happening to you?
https://bugzilla.suse.com/show_bug.cgi?id=918705 https://bugzilla.suse.com/show_bug.cgi?id=918705#c14
--- Comment #14 from Richard Biener rguenther@suse.com --- (In reply to Reinhard Max from comment #13)
@Gerad @Richard As this bug has been rotting for quite a while and alpine has seen several upgrades since, I'd like to hear if these corruptions are still happening to you?
I'm no longer using procmail but moved to imap & sieve, sorry.
https://bugzilla.suse.com/show_bug.cgi?id=918705 https://bugzilla.suse.com/show_bug.cgi?id=918705#c15
--- Comment #15 from Gerald Pfeifer gp@suse.com --- I do not recall running into this issue (and I have the originally reproducing situations still taking place such as a swath of e-mails being locally delivered at once) for years (plural).
So from my perspective, whatever it was, it's gone.
https://bugzilla.suse.com/show_bug.cgi?id=918705 https://bugzilla.suse.com/show_bug.cgi?id=918705#c16
Reinhard Max max@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED
--- Comment #16 from Reinhard Max max@suse.com --- Thanks for the quick response, closing as FIXED, then.
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com