Re: Is report_safe broken?
Greetings, again. spamassassin --lint runs clean. I re-entered the line by hand and deleted the original so that shouldn't be an issue. I also reviewed the configuration file location list and there are no other local.cf files or user_prefs files in the list of directories. Thanx! -Michael Matt Kettler mkettler...@verizon.net 3/31/2010 7:44 PM On 3/31/2010 12:34 PM, Michael Weber wrote: Greetings! I upgraded SA from version 3.2.5 to 3.3.1 this morning. Since that time all of the emails that are marked as spam are being converted to attachments. One other oddity. If you look close at the rewrite_header Subject line, you will count three %'s after the word SPAM. This is a change I made to test if SA was reading this config file at all. It is. My email subject lines went from %%SPAM%% to %%SPAM%%% just as expected, but the required score stayed at 5.0 and didn't change to 50.0. I re-checked the report_safe setting in the local.cf file and it is still set to zero as it was before. I also checked for another cf file changing that parameter but there are no other cf files that mention it. (Or .pre files for that matter.) The user_prefs file in the home directory has nothing that is not commented out and has not been changed from the default. I am calling spamc from a postfix filter line in master.cf, but that hasn't been changed since before the upgrade. As always, what am I missing? That should work fine. Did you run spamassassin --lint, to see if SA can parse the configuration files? (this should run with no output, but if there's a parse error, it will complain) SA could be tripping on an illegal character and skipping several lines of your config file... Given it's taking the rewrite_header option, it's obvious you've got the right local.cf and restarted spamd, etc, so there's something else amiss. TIA! Here is my /etc/mail/spamassassin/local.cf file: === rewrite_header Subject %%SPAM%%% (_SCORE_) add_header all Level _STARS(X)_ # required_score 5.0 required_score 50.0 report_safe 0 ok_locales en # ok_languages en # Use Bayesian classifier (default: 1) # use_bayes 1 # Bayesian classifier auto-learning (default: 1) # bayes_auto_learn 0 E-MAIL CONFIDENTIALITY NOTICE: This communication and any associated file(s) may contain privileged, confidential or proprietary information or be protected from disclosure under law (Confidential Information). Any use or disclosure of this Confidential Information, or taking any action in reliance thereon, by any individual/entity other than the intended recipient(s) is strictly prohibited. This Confidential Information is intended solely for the use of the individual(s) addressed. If you are not an intended recipient, you have received this Confidential Information in error and have an obligation to promptly inform the sender and permanently destroy, in its entirety, this Confidential Information (and all copies thereof). E-mail is handled in the strictest of confidence by Allied National, however, unless sent encrypted, it is not a secure communication method and may have been intercepted, edited or altered during transmission and therefore is not guaranteed.
Re: Is report_safe broken?
On 2010/04/01 11:38 AM, Michael Weber wrote: spamassassin --lint runs clean. I re-entered the line by hand and deleted the original so that shouldn't be an issue. I also reviewed the configuration file location list and there are no other local.cf files or user_prefs files in the list of directories. A little off-the-wall, but... I recall that recently other options in local.cf were sensitive to the order in the file they were placed. Maybe try moving required_score and report_safe to the top of local.cf, above rewrite_header and add_header. -- /Jason smime.p7s Description: S/MIME Cryptographic Signature
Re: Is report_safe broken?
I tried all the things that were mentioned without any luck. So, I got out my sledgehammer. I removed SA from my system and deleted every SA directory, reinstalled 3.3.1 from the RPM's I had just created, ran sa-update, and copied over the old local.cf file. It now works. I'm not sure where the problem was, but it's gone and that's what matters. Perhaps someone could re-create the problem and see if it's an install script issue or an old file that isn't being re-written when the update is run? My history is doing continual updates from SA version 1.something so there's no telling what might have been left over. Thanx, all! -Michael Matt Kettler mkettler...@verizon.net 3/31/2010 7:44 PM On 3/31/2010 12:34 PM, Michael Weber wrote: Greetings! I upgraded SA from version 3.2.5 to 3.3.1 this morning. Since that time all of the emails that are marked as spam are being converted to attachments. One other oddity. If you look close at the rewrite_header Subject line, you will count three %'s after the word SPAM. This is a change I made to test if SA was reading this config file at all. It is. My email subject lines went from %%SPAM%% to %%SPAM%%% just as expected, but the required score stayed at 5.0 and didn't change to 50.0. I re-checked the report_safe setting in the local.cf file and it is still set to zero as it was before. I also checked for another cf file changing that parameter but there are no other cf files that mention it. (Or .pre files for that matter.) The user_prefs file in the home directory has nothing that is not commented out and has not been changed from the default. I am calling spamc from a postfix filter line in master.cf, but that hasn't been changed since before the upgrade. As always, what am I missing? That should work fine. Did you run spamassassin --lint, to see if SA can parse the configuration files? (this should run with no output, but if there's a parse error, it will complain) SA could be tripping on an illegal character and skipping several lines of your config file... Given it's taking the rewrite_header option, it's obvious you've got the right local.cf and restarted spamd, etc, so there's something else amiss. TIA! Here is my /etc/mail/spamassassin/local.cf file: === rewrite_header Subject %%SPAM%%% (_SCORE_) add_header all Level _STARS(X)_ # required_score 5.0 required_score 50.0 report_safe 0 ok_locales en # ok_languages en # Use Bayesian classifier (default: 1) # use_bayes 1 # Bayesian classifier auto-learning (default: 1) # bayes_auto_learn 0 E-MAIL CONFIDENTIALITY NOTICE: This communication and any associated file(s) may contain privileged, confidential or proprietary information or be protected from disclosure under law (Confidential Information). Any use or disclosure of this Confidential Information, or taking any action in reliance thereon, by any individual/entity other than the intended recipient(s) is strictly prohibited. This Confidential Information is intended solely for the use of the individual(s) addressed. If you are not an intended recipient, you have received this Confidential Information in error and have an obligation to promptly inform the sender and permanently destroy, in its entirety, this Confidential Information (and all copies thereof). E-mail is handled in the strictest of confidence by Allied National, however, unless sent encrypted, it is not a secure communication method and may have been intercepted, edited or altered during transmission and therefore is not guaranteed.
Re: Is report_safe broken?
On 4/1/2010 11:38 AM, Michael Weber wrote: eetings, again. spamassassin --lint runs clean. I re-entered the line by hand and deleted the original so that shouldn't be an issue. I also reviewed the configuration file location list and there are no other local.cf files or user_prefs files in the list of directories. Have you tried redirecting a message file through spamassassin on the command-line to see if that works correctly? ie: spamassassin sample-spam.txt
Is report_safe broken?
Greetings! I upgraded SA from version 3.2.5 to 3.3.1 this morning. Since that time all of the emails that are marked as spam are being converted to attachments. One other oddity. If you look close at the rewrite_header Subject line, you will count three %'s after the word SPAM. This is a change I made to test if SA was reading this config file at all. It is. My email subject lines went from %%SPAM%% to %%SPAM%%% just as expected, but the required score stayed at 5.0 and didn't change to 50.0. I re-checked the report_safe setting in the local.cf file and it is still set to zero as it was before. I also checked for another cf file changing that parameter but there are no other cf files that mention it. (Or .pre files for that matter.) The user_prefs file in the home directory has nothing that is not commented out and has not been changed from the default. I am calling spamc from a postfix filter line in master.cf, but that hasn't been changed since before the upgrade. As always, what am I missing? TIA! Here is my /etc/mail/spamassassin/local.cf file: === rewrite_header Subject %%SPAM%%% (_SCORE_) add_header all Level _STARS(X)_ # required_score 5.0 required_score 50.0 report_safe 0 ok_locales en # ok_languages en # Use Bayesian classifier (default: 1) # use_bayes 1 # Bayesian classifier auto-learning (default: 1) # bayes_auto_learn 0 Michael Weber Network Administrator Allied National, Inc. 4551 W . 107th St. Suite 100 Overland Park, KS 66207 913-945-4313 is my direct number E-MAIL CONFIDENTIALITY NOTICE: This communication and any associated file(s) may contain privileged, confidential or proprietary information or be protected from disclosure under law (Confidential Information). Any use or disclosure of this Confidential Information, or taking any action in reliance thereon, by any individual/entity other than the intended recipient(s) is strictly prohibited. This Confidential Information is intended solely for the use of the individual(s) addressed. If you are not an intended recipient, you have received this Confidential Information in error and have an obligation to promptly inform the sender and permanently destroy, in its entirety, this Confidential Information (and all copies thereof). E-mail is handled in the strictest of confidence by Allied National, however, unless sent encrypted, it is not a secure communication method and may have been intercepted, edited or altered during transmission and therefore is not guaranteed.
Re: Is report_safe broken?
On 3/31/2010 12:34 PM, Michael Weber wrote: Greetings! I upgraded SA from version 3.2.5 to 3.3.1 this morning. Since that time all of the emails that are marked as spam are being converted to attachments. One other oddity. If you look close at the rewrite_header Subject line, you will count three %'s after the word SPAM. This is a change I made to test if SA was reading this config file at all. It is. My email subject lines went from %%SPAM%% to %%SPAM%%% just as expected, but the required score stayed at 5.0 and didn't change to 50.0. I re-checked the report_safe setting in the local.cf file and it is still set to zero as it was before. I also checked for another cf file changing that parameter but there are no other cf files that mention it. (Or .pre files for that matter.) The user_prefs file in the home directory has nothing that is not commented out and has not been changed from the default. I am calling spamc from a postfix filter line in master.cf, but that hasn't been changed since before the upgrade. As always, what am I missing? That should work fine. Did you run spamassassin --lint, to see if SA can parse the configuration files? (this should run with no output, but if there's a parse error, it will complain) SA could be tripping on an illegal character and skipping several lines of your config file... Given it's taking the rewrite_header option, it's obvious you've got the right local.cf and restarted spamd, etc, so there's something else amiss. TIA! Here is my /etc/mail/spamassassin/local.cf file: === rewrite_header Subject %%SPAM%%% (_SCORE_) add_header all Level _STARS(X)_ # required_score 5.0 required_score 50.0 report_safe 0 ok_locales en # ok_languages en # Use Bayesian classifier (default: 1) # use_bayes 1 # Bayesian classifier auto-learning (default: 1) # bayes_auto_learn 0
