This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients BreamoreBoy, ajaksu2, barry, r.david.murray, rndblnch
Date 2012-05-27.20:53:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1338152028.42.0.671032618424.issue1672568@psf.upfronthosting.co.za>
In-reply-to
Content
Hmm.  Thinking about it, though, that might not work if there are other errors in the message, many of which are more benign.  Probably the raise_on_defect control is a little too coarse.

I've been thinking that we need a way to set the policy on an already existing message, which would make this work more usefully.  But that's a different issue.
History
Date User Action Args
2012-05-27 20:53:48r.david.murraysetrecipients: + r.david.murray, barry, rndblnch, ajaksu2, BreamoreBoy
2012-05-27 20:53:48r.david.murraysetmessageid: <1338152028.42.0.671032618424.issue1672568@psf.upfronthosting.co.za>
2012-05-27 20:53:47r.david.murraylinkissue1672568 messages
2012-05-27 20:53:47r.david.murraycreate