Thanks again, Jakob, and sorry for the confusion. I'm subscribing the backports team to this, to see whether they consider this important enough to get fixed in dapper.To do that, we would have to either:
1) get a backport of the version currently in feisty (1.4). This will make it available for any Dapper users who have enabled the backports repository or 2) make a Stable Release Update, based on your patch. This will make it available to all users. The rules for Stable Release Updates are pretty strict (see https://wiki.ubuntu.com/StableReleaseUpdates): Stable release updates will, in general, only be issued in order to fix high-impact bugs. Examples of such bugs include: * Bugs which may, under realistic circumstances, directly cause a security vulnerability * Bugs which represent severe regressions from the previous release of Ubuntu * Bugs which may, under realistic circumstances, directly cause a loss of user data ** Changed in: spamprobe (Ubuntu) Status: Rejected => Unconfirmed -- Spamprobe segfaults on bad mime input https://launchpad.net/bugs/85033 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
