FYI, I got rawlog working and it shows the same break in the raw logs as in the broken headers. Below is a snippet from the rawlog (names and other identifiers redacted). The offending sequence is always in the References headers section, and you can see the line breaks there that show this. So it sounds like this can't be an issue with Dovecot, am I right? I wish I could get this figured out. Such a headache.... *sigh*
Thanks!
========================================================================
poht IDLE
DONE
slwf LIST "" "INBOX"
36oi LSUB "" "*"
2by6 IDLE
DONE
p5dx SELECT "shared.IT"
uz85 FETCH 6 (UID)
f925 UID FETCH 1:51 (UID FLAGS)
kd5i IDLE
DONE
y9u7 UID FETCH 51 (UID FLAGS BODY.PEEK[])
qoyj IDLE
DONE
rfxa UID STORE 51 +FLAGS (\Deleted \Seen)
h8ly IDLE
DONE
fe4g EXPUNGE
fauq IDLE
DONE
1wa2 UID FETCH 49 (UID FLAGS BODY.PEEK[])
6403 IDLE
DONE
luq8 UID FETCH 50 (UID FLAGS BODY.PEEK[])
700u IDLE
DONE
jl6b APPEND "shared.IT" (\Seen \Answered) " 2-Nov-2010 11:46:19 -0700"
{12898938}
From: "User" User@xxx.com
To: "zzz, Roy",
"zzz, Mandred",
"zzz, Jerry"
Cc: "zzz, Johan",
"Bob zzz" bobw@xxx.com,
"Brandon zzz" brandonh@xxx.com,
"Mark zzz" MarkBe@xxx.com,
"Cassie zzz" CassieE@xxx.com,
"Erin zzz" erinb@xxx.com
References: B3457C1920D7A2438CCC19EF2A527293372B11@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A527293372D9A@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272933A2C3D@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272933A310E@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272933A3683@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272933A3B97@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272933D103B@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272933D192F@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272933D1B12@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272933FD341@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272933FD8F8@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272933FD9A0@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272933FDFDD@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272934C8927@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272934C8B46@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272934C8D76@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272934C8D7A@yyy027.yyy.local On Wed, Nov 3, 2010 at 1:32 PM, Timo Sirainen tss@iki.fi wrote: On 3.11.2010, at 19.53, Scott Goodwin wrote: Emails to one specific user in my organization (let's call him
Roy@Ocean.org)
is having his emails mangled when dragging certain items from his
Exchange
mailbox to the IMAP account. Is the client using SSL? If not, looking at the actual IMAP traffic would
be helpful. Best would be to look it at the Outlook machine, but I don't
know what Windows tools exist for that. You could also enable Dovecot's
rawlog, which works also with SSL enabled. If in the output you see the same
corruption then it's caused by Outlook (or some antivirus/firewall in the
middle). http://wiki.dovecot.org/Debugging/RawlogD7A2438CCC19EF2A5272934C8D95@yyy027.yyy.local>
B3457C1920D7A2438CCC19EF2A5272934C8DB6@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272934C8F0D@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272935008B5@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A527293500C27@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272935011BC@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A527293525B1D@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A527293525D81@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A527293526139@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A527293526416@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272935524A6@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272935524C9@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A527293589E1C@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272935BF6A9@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272935E7414@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272935E75E2@yyy027.yyy.local
B3457C1920D7A2438CCC19EF2A5272935E75E8@yyy027.yyy.local