I think this is what you asked for.On Thu, 2015-07-16 at 15:03 -0400, Alan Gagne wrote:No joy. So I repeated these steps but also removed everything under (./.cache/evolution/mail/1378488851 9580 27 dw-agagne/folders.db).Hi, could you repeat the cache cleanup again, then run evolution with EWS debugging on: $ EWS_DEBUG=2 evolution &>log.txt and once the folder summary is fetched, select the offending message and view it, see that it shows a different From, then close evolution and search for that message in the log (for the first and the secondFrom addresses/names), please? As you can reproduce that reliably, Isuspect that some EWS properties on the server have stored one From, while the other properties the other From. That would be visible in the log. Data from the debug log file. Date: Fri, 17 Jul 2015 09:43:11 +0000 From: DB_Alert pod32 <xxx xxx list xxxxx com> CC: <eng xxx xxx xxxxx com> Message-ID: <1508412758 8641 1437126191952 JavaMail oracle blade0-4> Subject: EM Event: Critical:aagi_aagi2 - Metrics "Global Cache Average CR Get Time" is at 3.27 <t:From> <t:Mailbox> <t:Name>DB_Alert pod36</t:Name> <t:EmailAddress>xxx xxx list xxxxx com</t:EmailAddress> <t:RoutingType>SMTP</t:RoutingType> <t:MailboxType>OneOff</t:MailboxType> </t:Mailbox> </t:From> <t:InternetMessageId><1508412758 8641 1437126191952 JavaMail oracle blade0-4></t:InternetMessageId> |