Dale, > I was wondering why I was having problems with the modified subject. > > I tried the 2.3.2 conf file and it appeared to work so I diff'ed it > and this is what I came up with.
There was no difference in amavisd.conf between amavisd-new-2.3.2 and 2.3.3-pre2 (nor in amavisd.conf-sample for these variables). > @@ -1572,10 +1572,10 @@ > -#\$sa_spam_modifies_subj = 1; # in @spam_modifies_subj_maps, default > is true > +#\$sa_spam_modifies_subj = 1; # in @sa_spam_modifies_subj_maps, > default is true > [EMAIL PROTECTED] = ( [qw( [EMAIL PROTECTED] . )] ); > [EMAIL PROTECTED] = ( [qw( [EMAIL PROTECTED] . )] ); You are reporting a change that was documented in amavisd-new-2.3.2 release notes: - replaced nonexistent variable @sa_spam_modifies_subj_maps by @spam_modifies_subj_maps in commented-out example in amavisd.conf-sample; noticed by Joachim Schoenberg; And, you did a diff in reverse (newer to older). Mark ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
