http://bugzilla.spamassassin.org/show_bug.cgi?id=3077
------- Additional Comments From [EMAIL PROTECTED] 2004-02-26 11:59 ------- Subject: Re: spamassassin -d is too damn slow -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > The report_safe format should *always* be an message/rfc822 attachment. > > It's foolproof, easy, and standard -- we should stick by it. > > Yeah, as long as we keep the detection of that markup the same, it > doesn't matter what the contents are. You're not suggesting removing support for report_safe 0? There is a sizeable group of people who prefer to simply mark up spam with some additional headers -- and with good reason IMO; I'm considering going back to that, given the inconvenience of developing rules from report_safe-1-encapsulated spam. It's quite useful for experienced users. > > Now, removing markup from non-marked-as-spam messages is always going to > > be a bit more up in the air, but I think we should also try to keep this > > as stable as possible from version to version. > > I think we've done pretty well at this, although we could standardize > more. For instance, we've pretty much claimed the X-Spam-* header space, > so removing the markup there is as easy as dropping all those headers. > Old (2.4x and before) did the whole X-Spam-Prev-* thing for content-type > and the like. I think we should continue to support that generically by > using the following algorithm and making subject/from/to rewriting put the > original in X-Spam-Prev format (as was already brought up on the list): > > 1) For each X-Spam-Prev-(.+) header in the message, delete $1 and rename > X-Spam-Prev-$1 to $1. > > 2) Delete all X-Spam-.* headers in the message > > It keeps things all standardized, removes us needing to load the configs > to figure out the rewrite RE, etc, etc. +1. - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Exmh CVS iD8DBQFAPlALQTcbUG5Y7woRAgVfAJ4mEtWWUtZOb6zDWd8HxTIckwVECwCgyvQU urAZdGPkgBfOVO1caEzHf0s= =Q7tz -----END PGP SIGNATURE----- ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
