Date problem after migration

[Scott M. Likens]

I'll put in my 10cents as it's not really on topic for this mailing list.

When converting from a qmail+courier IMAP solution to Zimbra *ugh* I had
a similar problem in this case Zimbra had a solution.

imapsync --ssl1 --ssl2 --host1 #HOST1# --host2 #HOST2# \
--authuser1 cyrus --password1 #PASSWORD1# --authuser2 cyrus \
--password2 #PASSWORD2# --authmech1 PLAIN --authmech2 PLAIN \
--subscribe --user1 #USER# --user2 #USER# \
--delete2 --expunge --expunge2 --syncinternaldates

Adding --syncinternaldates

Additionally I found using --user2 %USER%\tb

They added it to fix Thunderbird actually, but tied in with
syncinternaldates and the other portion the only annoyance was loosing
the unique identifier scheme (we had alot of pop3 users and there is no
central scheme for UIDL what so ever so the same message can be
re-downloaded 8000x)

Another thing if you're moving from a broken setup to a working setup
you may want to look at,

--useheader   <string> : Use this header to compare messages on both sides.
                         Ex: Message-ID or Subject or Date.

good old fashion regexp.

Off hand it's not very useful, but using --syncinternaldates is always
good to use I found.

Scott


Andrew Morgan wrote:
> On Tue, 9 Oct 2007, Guillaume Postaire wrote:
>
>   
>> Hi all,
>>
>> We just have done a migration from a very old Cyrus stand alone
>> installation to a new one with murder.
>>
>> During the migration everything went ok and no user complaint, so we
>> destroy our old mailbox.
>>
>> Shortly after that one of our user notice a huge problem with outlook
>> that we don't reproduce with thunderbird (put here whatever imap
>> compliant client). All the mail older than the migration have the date
>> of the migration in outlook. It seems that outlook don't use the header
>> date (wich are ok in the plain text storage) but another information
>> that come from cyrus.
>>
>> We try to analyse what happen and discover we forget to use "
>> --syncinternaldates" with imapsync. We simulate some migration and this
>> problem don't exist if we had this.
>>
>> How could we correct the date stored in cyrus ?
>>
>> Here is the command we use for migration
>> imapsync --ssl1 --ssl2 --host1 #HOST1# --host2 #HOST2# \
>> --authuser1 cyrus --password1 #PASSWORD1# --authuser2 cyrus \
>> --password2 #PASSWORD2# --authmech1 PLAIN --authmech2 PLAIN \
>> --subscribe --user1 #USER# --user2 #USER# \
>> --delete2 --expunge --expunge2
>>     
>
> We had the same problem here, but just told our users to suck it up.  :)
>
> I suppose you could create some script to read the Date: header from each 
> message and set the message file mtime to match.  You would probably need 
> to reconstruct the mailbox after that to pick up the change.
>
> Or, you can tell Outlook to sort on the Date: header rather than the 
> arrival time of the message.
>
>  	Andy
> ----
> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>
>
> !DSPAM:470bda5c77459552314630!
>
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20071009/ab5072e7/attachment-0001.html