Occurrences of this issue became more common starting on 8/13/2013 when Salesforce's inbound email infrastructure was upgraded increasing the concurrency of emails passed along to the Force.com platform. The likelihood of encountering this error increases with the concurrency of emails received and automation that runs for each email received. Please see the details below for additional information.