Thank you Simon for your verification. I have verified all releases (Lucid, Precise, Trusty, Utopic). For Lucid, I used a VM, as I couldn't get LXC networking to work with it. For the others, I used LXC.
In each VM or container, I enabled proposed, installed spamassassin, ran my test case and verified that it said "Not affected". I also noticed that my test script doesn't check the exit status of spamassassin, so I checked every "output" file manually to verify that spamassassin is still working correctly with the other checks. Utopic needed some special manual treatment due to bug 1355343 meaning that I couldn't cat to the end of sources.list to enable proposed. ** Tags removed: verification-needed ** Tags added: verification-done verification-done-lucid verification-done-utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412830 Title: [AHBL] spamassassin is returning false positives by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1412830/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
