Hi.

This is basically the same as Debian bugs #690741, #633799 and #691469.
I used severity critical, as the mboxo format causes irrecoverable
mail corruption, which is unknown to most users.


The details of the problem, what happens and how it can be easily
solved are to be found in the upstream bug report.
to #690741, #633799 and #691469):

If ustream _shouldn't_ want to fix this (i.e. by moving to a non-corrupting
mbox format) or if it cannot be done in time for wheezy (which is likely),
we should appropriately warn our users, e.g. via:
- NEWS entry
- package description
- a debconf warning dialogoue with priority high (but Osamu Aoki has indicated
  that this may violate the Debian policy).

But even when it's fixed, I think we should use appropriate ways (NEWS file)
to warn our users that ever since, this issue has existed and their mails
are likely affected.


To get some numbers,... in my own mail archive (about 3,4 million mails)
~17000 mails are corrupted from this issue.


Best wishes,
Chris.

severity 692331 important
thanks

As per the discussion on the upstream bug, this is hardly RC,
downgrading.


Cheers,

Michael

What exactly are you referring to? Upstream has not really brought up
sane arguments, IIRC.
Well, same as in #690741 I personally think that any data corruption
that touches the "core data" of a program, deserves the highest
severity.... therefore delegating the discussion on the appropriate
severity to [0].


Cheers,
Chris.




[0] http://lists.debian.org/debian-devel/2012/11/msg00675.html