At 18:06 7/01/2005, Dan Hollis wrote:
On Thu, 6 Jan 2005, Matt Kettler wrote: > At 07:27 PM 1/6/2005, Simon Byrnand wrote: > >- The "rewrite_subject" and "subject_tag" configuration options were > > deprecated and are now removed. Instead, using "rewrite_header Subject > > [your desired setting]". e.g. > > rewrite_subject 1 > > subject_tag ****SPAM(_SCORE_)**** > > becomes > > rewrite_header Subject ****SPAM(_SCORE_)**** > >What was the logic behind this unnecessary change ? > Flexibility. rewrite_header isn't just capable of rewiting the subject > line. It can rewrite other headers too.
I think he meant, why _remove_ the old syntax instead of supporting it _in addition to_ the new syntax?
Yes, thats what I meant.
I can't see any good reason not to support old syntax as backwards compatibility.
It would ease migrating to 3.0.x a great deal for many sites to support backwards compatibility. Instead, stuff breaks. This is why people are so hesitant to move to php5, perl6 etc. spamassassin should not follow these examples. -Dan
Some changes are an expectation of major new releases of software of course, but SpamAssassin seems to have had a few gratuitous ones over the past major couple of releases.... and a few silly little things like changing sa-learn --rebuild to sa-learn --sync etc.... I'm sure there were good reasons for it, but it still makes things difficult for people upgrading.
I still havn't even considered looking at Apache 2.0 for example due to the major changes and the fact that things such as php weren't available for it for some time. (I hate to think what the issues with going to php 5 might be :)
Regards, Simon
