[Bug 918705] New: alpine locking failure (against procmail) leads to mail corruption

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> In-Reply-To: Message-ID: <54E623B70200006F001594A6@suse.com> From: ... To: "Gerald Pfeifer" ==== 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 ) -- You are receiving this mail because: You are on the CC list for the bug.