I just figured out that the if an mbox file is modified (because a message was added
to that mailbox) both this file and the table_of_contents file have to be copied over to
the destination *.mbox folder for the changes to be seen in the destination machine;
if this is done Mail.app will not mark as unread all the messages in the mailbox.
However when these SAME FILES are propagated using unison, Mail.app does not
seem to recognize this fact and marks all the messages in the mailbox as unread, as if
only the mbox file was copied. Maybe the table_of_contents file has resource forks?.
--- In firstname.lastname@example.org, Jorge A Ahumada <jahumada@u...> wrote:
> OK, I have used on OS X for about a year with no complaints, but when I
> changed to 10.3 (Panther) I started having the following problem when
> using unison to sync my mail. The Mail.app uses the standard mbox
> folders used in the NeXT. When I sync ~/Library/Mail all the
> information transfered to the destination appear as unread messages
> when opening mail. It seems that Mail.app re-indexes everything as it
> opens the synced mboxes. If I straight "copy" an mbox to the
> destination the problem does not appear. So, unison is doing something
> that causes it to re-index mailboxes everytime.
> I have tried everything (supressing the table_of_contents file from
> being transferred, removing and adding different files, ignoring
> various 'dot' files...I JUST CAN't FIGURE IT OUT!!! PLEASE HELP!!!!
> using version 2.9.2, OS 10.3