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). -- You are receiving this mail because: You are on the CC list for the bug.