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
)