hi, we migrate from exchange to dovecot. we do it with imapsync. first we try to do it with --syncinternaldates, but this fails on many messages with invalid date, so we drop this option. unfortunately after this those users who use outlook see the received date as the date we do the migration in stead of the real received date. other clients eg webmail, thunderbird etc sees the right date. so my question what can i do? it's a dovecot bug or outlook and if outlook's bug is there any workaround fro this? thanks in advance. -- Levente "Si vis pacem para bellum!"
On Sun, 2007-10-14 at 11:53 +0200, Farkas Levente wrote:> hi, > we migrate from exchange to dovecot. we do it with imapsync. first we > try to do it with --syncinternaldates, but this fails on many messages > with invalid date, so we drop this option. unfortunately after this > those users who use outlook see the received date as the date we do the > migration in stead of the real received date. other clients eg webmail, > thunderbird etc sees the right date. so my question what can i do? it's > a dovecot bug or outlook and if outlook's bug is there any workaround > fro this?The clients use either Date: header or IMAP INTERNALDATE. In some clients it's configurable which one to use. I prefer INTERNALDATE myself. So the only solution would be to sync the internaldates as well. What do you mean messages have invalid dates? As long as imapsync uses a properly formatted date for APPEND, it shouldn't fail. Although I did some fixes related to this in v1.0.1. If exchange returns INTERNALDATEs with invalid format, imapsync could figure this out itself and just not use it then. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20071021/2caec111/attachment-0002.bin>
Timo Sirainen wrote:> On Sun, 2007-10-14 at 11:53 +0200, Farkas Levente wrote: >> hi, >> we migrate from exchange to dovecot. we do it with imapsync. first we >> try to do it with --syncinternaldates, but this fails on many messages >> with invalid date, so we drop this option. unfortunately after this >> those users who use outlook see the received date as the date we do the >> migration in stead of the real received date. other clients eg webmail, >> thunderbird etc sees the right date. so my question what can i do? it's >> a dovecot bug or outlook and if outlook's bug is there any workaround >> fro this? > > The clients use either Date: header or IMAP INTERNALDATE. In some > clients it's configurable which one to use. I prefer INTERNALDATE > myself. > > So the only solution would be to sync the internaldates as well. What do > you mean messages have invalid dates? As long as imapsync uses a > properly formatted date for APPEND, it shouldn't fail. Although I did > some fixes related to this in v1.0.1. > > If exchange returns INTERNALDATEs with invalid format, imapsync could > figure this out itself and just not use it then.probably that's the problem. what internaldate in dovecot, the file's modify date in the maildir? i'd be nice if i can somehow set internaldate to the date field with dovecot (actually i already wrote a shell script but it's not the beast solution). -- Levente "Si vis pacem para bellum!"