[BlueOnyx:01295] Re: Updated CMU available (fix for 0 byte mbox after import)

[Roman Bürkle]

Hi Michael,

new week, new tries, and you did a faboulous job, it worked out. All
mboxes recovered without any zero-sizes :)

Greets
Roman

On Mon, 2009-05-25 at 04:29 +0200, Michael Stauber wrote:
> Hi all,
> 
> I just released a new CMU RPM to the BlueOnyx YUM repository:
> 
> 5106R-cmu-2.66-0BQ30.centos5.noarch.rpm
> 
> You can grab it with "yum update".
> 
> It fixes the problem where - after an import - users randomly had lost all
> emails from their mailbox.
> 
> This affected all ...
> 
>         BlueOnyx to BlueOnyx
>         BlueQuartz to BlueOnyx
>         RaQ550 to BlueOnyx
>         BlueQuartz to BlueQuartz
>         RaQ550 to BlueQuartz
> 
> ... migrations.
> 
> In fact that problem already existed in the original BlueQuartz CMU (and still
> does) - except in some really ancient versions of it.
> 
> On BlueOnyx and BlueQuartz the mailbox of a user resides in ~username/mbox -
> which typically translates to something obscure like this:
> 
>         /home/.sites/28/site1/.users/40/testuser/mbox
> 
> When you run cmuExport, then the mailbox (mbox) is packed up into private-
> username.tar.gz - alongside with other files from that users home directory.
> Additionally CMU will include a copy of "mbox" as "cmu-mailspool".
> 
> And exactly there CMU did wrong in the past:
> 
> It didn't take our "/home/.sites/28/site1/.users/40/testuser/mbox" and stored
> it as "cmu-mailspool" into the export. No, it used "/var/spool/mail/username"
> instead. Which doesn't exist or which is empty on BlueQuartz and/or BlueOnyx.
> 
> Upon restore cmuImport *always* used "cmu-mailspool" from private-
> username.tar.gz and copied it to "~usename/mbox". Once that's done, it'll
> delete "cmu-mailspool", as it's no longer needed.
> 
> To fix this issues extra checks were added that make sure that CMU copies the
> right mailbox file to "cmu-mailspool". Additional checks also make sure that
> CMU will not copy a 0 byte sizes "cmu-mailspool" over an already existing
> "mbox" file upon cmuImport.
> 
> This works fine even if you import with CMU and use sets of data that were
> exported with the broken previous versions of CMU from either BlueQuartz or
> BlueOnyx. Because if your "bad" CMU created an empty "cmu-mailspool" in the
> export, then it will just restore the good "mbox" file that it finds in that
> export, which contains all your emails.
> 
> Further fixes to CMU include better cross-platform support for Rickard Osser's
> BlueApp.
> 
> Code changes:
> http://devel.blueonyx.it/trac/changeset?old_path=%2F&old=266&new_path=%2F&new=268
> 
> --
> With best regards
> 
> Michael Stauber
> 
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at blueonyx.it
> http://www.blueonyx.it/mailman/listinfo/blueonyx