Since we've installed the service pack 1 of Exchange 2007. A extra header information is added by the append IMAP command (when you move or copy a mail with an IMAP Client to the exchange server): "Received: from (192.168.1.1) by cas.domain.com (192.168.1.51) with IMAP; Tue, 18 Dec 2007 09:44:51 +0100" In Outlook, the displayed date is now the copy/move date instead of the received date... We are migrating from an IMAP server to Exchange 2007 using an imap to imap copy and we want to keep the date of the message. This occurs in SP1 only. Is it a bug? a new behavior? Is there a parameter? ... Thanks for your answers
Hi Daniel. we are having the same problem. We would like to migrate to MSX 2007 SP1 by using the IMAP Protocol to import the data. As MSX effectively alters the date information by adding headers, this way is effectively blocked for us. We haven't found a way to configure this, either. We would dearly like to have a parameter or hotfix to have this behaviour stopped. Sebastian "Daniel G." wrote: > Since we've installed the service pack 1 of Exchange 2007. A extra header > information is added by the append IMAP command (when you move or copy a mail > with an IMAP Client to the exchange server): > "Received: from (192.168.1.1) by cas.domain.com (192.168.1.51) with IMAP; > Tue, 18 Dec 2007 09:44:51 +0100" > > In Outlook, the displayed date is now the copy/move date instead of the > received date... > > We are migrating from an IMAP server to Exchange 2007 using an imap to imap > copy and we want to keep the date of the message. > > This occurs in SP1 only. > > Is it a bug? a new behavior? Is there a parameter? ... > > Thanks for your answers
On Wed, 19 Dec 2007 02:01:01 -0800, Sebastian Eberhard wrote: >Hi Daniel. >we are having the same problem. >We would like to migrate to MSX 2007 SP1 by using the IMAP Protocol to >import the data. As MSX effectively alters the date information by adding >headers, this way is effectively blocked for us. > >We haven't found a way to configure this, either. We would dearly like to >have a parameter or hotfix to have this behaviour stopped. I've asked about this. If I hear anything back, I will post here. >Sebastian > >"Daniel G." wrote: > >> Since we've installed the service pack 1 of Exchange 2007. A extra header >> information is added by the append IMAP command (when you move or copy a mail >> with an IMAP Client to the exchange server): >> "Received: from (192.168.1.1) by cas.domain.com (192.168.1.51) with IMAP; >> Tue, 18 Dec 2007 09:44:51 +0100" >> >> In Outlook, the displayed date is now the copy/move date instead of the >> received date... >> >> We are migrating from an IMAP server to Exchange 2007 using an imap to imap >> copy and we want to keep the date of the message. >> >> This occurs in SP1 only. >> >> Is it a bug? a new behavior? Is there a parameter? ... >> >> Thanks for your answers
We've got an open support case with PSS. I'll let you know if I get an answer. Sebastian
Hi, our case has ascertained that this feature has come up with Exchange 2007 SP1. The Microsoft Support has confirmed that this feature is by design. We have opened a critical design change request via our TAM to have this behaviour changed. However, it's now up to the Exchange group in Redmond to implement a fix or reject the request. Andy, we would be glad if you would use your ties with Microsoft to promote this request. I think many people in a migration scenario would benefit from this. We internally discussed the alternative to install a CAS Server without SP1 and use that one only for the IMAP4 protocol. However, we are not certain about the repercussions of a mixed SP1/non SP1 Exchange environment. Bye, Sebastian
Hi Sebastian, I've had news from Microsoft: This is a new feature implemented as a bug fix... All messages incoming to the server must have a time stamp. Now the IMAP server from Microsoft Exchange is the only one IMAP server wich fix this well know bug... ;-) I need to migrate about 10'000 mailboxes from IMAP server to Exchange 2007 and I'm trying to ask Microsoft to have a parameter to disable this new feature. If you have more news... Daniel
Hi Sebastian, ... > We internally discussed the alternative to install a CAS Server without SP1 > and use that one only for the IMAP4 protocol. However, we are not certain > about the repercussions of a mixed SP1/non SP1 Exchange environment. ... We would like to install a new server with CAS and Mailbox role without SP1 for the migration. Do you have any information about mixed SP1/non SP1 Exchange environment? Did you already install a CAS server without SP1? Thanks for your answer. Daniel Gougerot
On Dec 21 2007, 4:43 pm, Daniel G. wrote: > Hi Sebastian, > > I've had news from Microsoft: > > This is a new feature implemented as a bug fix... All messages incoming to > the server must have a time stamp. Now the IMAP server from Microsoft > Exchange is the only one IMAP server wich fix this well know bug... ;-) OK, message incoming need a time stamp. But the procedure I used gave it a time stamp according the APPEND method in RFC2060. It seems that exchange simply ignores the given time stamp and replaced it with the current time and date of moment the APPEND took place. What's going on? According to RFC2060: 6.3.11. APPEND Command Arguments: mailbox name OPTIONAL flag parenthesized list OPTIONAL date/time string message literal If a date_time is specified, the internal date SHOULD be set in the resulting message; otherwise, the internal date of the resulting message is set to the current date and time by default. Any thoughts?
