Jim wrote: >>> Upgraded from rc2, and now the X-Spam-Level and X-Spam-Status headers do >>> not get added unless I set this variable to 1. >>> >>> In all previous versions I've used, the reverse was true.
Theo Van Dinter wrote: >> always_add_headers doesn't affect X-Spam-Level and X-Spam-Status. >> They're both added by default to all messages, unless your configuration >> disables them. > I can't agree with that as stated, because: > > 1. http://www.spamassassin.org/doc/Mail_SpamAssassin_Conf.html claims that > always_add_headers affects exactly these headers; always_add_headers only affected ham messages. spam messages have always had those headers added. The "all" basically meant "add them to ham as well". The default has always been 1, so by default *all* messages get the headers. So, if someone changes the setting to 0, then it removes the headers, but only from ham. This is true in both 2.60-rc4 and previous 2.5x versions. Previous 2.60-rc versions had somewhat different behavior from previous 2.5x releases which is fixed (as much as it can be) in 2.60-rc4. > 2. toggling this variable on my account does in fact turn these headers on > and off when I send myself mails and look at the headers. Yes, Theo is correct though. The default setting is 1, not 0. > However, I have found what was causing me problems. I am using a > plugin for SquirrelMail which edits these options in the MySQL DB, and > if it doesn't find always_add_headers as an @GLOBAL rule, and if the > user doesn't already have a pref (in the DB) which sets it to 1, it > defaults to setting it to 0. Which really is a bug IMHO, and I will > notify the author. ;) That is a bug, then. Daniel ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
