Re: Confused by new version of spamassassin
On 11/26/14, Paul Gardiner li...@glidos.net wrote: On 25/11/2014 09:57, Reindl Harald wrote: Am 25.11.2014 um 10:40 schrieb Paul Gardiner: I drive spamassassin using spampd. I've just swapped from using opensuse 13.1 to 13.2. That's taken me from spamassassin 3.3.2 to 3.4.0. I have two confusing changes. 1) The really problematic one is that I no longer see X-Spam-Level and X-Spam-Status headers in the processed mail. I do still have X-Spam-Checker-Version. I was using status to trigger rejection, so now effectively I have no filtering. 2) The confusing one: I used to have many .cf files in /usr/share/spamassassin/. I now have none you need to call sa-update after a version change since the rules are always below a versioned folder Gah! That was it. Silly me. I didn't restart spampd after the update. At least, I assume that's it because I just restarted spampd and it has all magically started working again. Thanks again everyone for all your help. Cheers, Paul. I'm still a little unsure as to why sa-update hadn't been called before. I seem to have a daily cron job that is supposed to call it, but still I do at least have filtering now. such a mes, i suggest you use amavisd instead
Confused by new version of spamassassin
Hi, I drive spamassassin using spampd. I've just swapped from using opensuse 13.1 to 13.2. That's taken me from spamassassin 3.3.2 to 3.4.0. I have two confusing changes. 1) The really problematic one is that I no longer see X-Spam-Level and X-Spam-Status headers in the processed mail. I do still have X-Spam-Checker-Version. I was using status to trigger rejection, so now effectively I have no filtering. 2) The confusing one: I used to have many .cf files in /usr/share/spamassassin/. I now have none. As you can probably tell, I don't really know much about spamassassin. I've to some degree been using it out of the box and having it just work. I realise the change could be down to opensuse packaging, but I thought someone here might know best where the problem lies. (I wondered if perhaps now spamassassin requires a cronjob to download and update the rules) Any advice gratefully received. Cheers, Paul.
Re: Confused by new version of spamassassin
Am 25.11.2014 um 10:40 schrieb Paul Gardiner: I drive spamassassin using spampd. I've just swapped from using opensuse 13.1 to 13.2. That's taken me from spamassassin 3.3.2 to 3.4.0. I have two confusing changes. 1) The really problematic one is that I no longer see X-Spam-Level and X-Spam-Status headers in the processed mail. I do still have X-Spam-Checker-Version. I was using status to trigger rejection, so now effectively I have no filtering. 2) The confusing one: I used to have many .cf files in /usr/share/spamassassin/. I now have none you need to call sa-update after a version change since the rules are always below a versioned folder signature.asc Description: OpenPGP digital signature
Re: Confused by new version of spamassassin
On 25/11/2014 09:57, Reindl Harald wrote: Am 25.11.2014 um 10:40 schrieb Paul Gardiner: I drive spamassassin using spampd. I've just swapped from using opensuse 13.1 to 13.2. That's taken me from spamassassin 3.3.2 to 3.4.0. I have two confusing changes. 1) The really problematic one is that I no longer see X-Spam-Level and X-Spam-Status headers in the processed mail. I do still have X-Spam-Checker-Version. I was using status to trigger rejection, so now effectively I have no filtering. 2) The confusing one: I used to have many .cf files in /usr/share/spamassassin/. I now have none you need to call sa-update after a version change since the rules are always below a versioned folder Thanks for the suggestion, but it doesn't looked to have helped. sa-update ran without error, but problem 1 persists, and I still don't see the old .cf files I used to have. Cheers, Paul.
Re: Confused by new version of spamassassin
Am 25.11.2014 um 11:31 schrieb Paul Gardiner: On 25/11/2014 09:57, Reindl Harald wrote: Am 25.11.2014 um 10:40 schrieb Paul Gardiner: I drive spamassassin using spampd. I've just swapped from using opensuse 13.1 to 13.2. That's taken me from spamassassin 3.3.2 to 3.4.0. I have two confusing changes. 1) The really problematic one is that I no longer see X-Spam-Level and X-Spam-Status headers in the processed mail. I do still have X-Spam-Checker-Version. I was using status to trigger rejection, so now effectively I have no filtering. 2) The confusing one: I used to have many .cf files in /usr/share/spamassassin/. I now have none you need to call sa-update after a version change since the rules are always below a versioned folder Thanks for the suggestion, but it doesn't looked to have helped. sa-update ran without error, but problem 1 persists, and I still don't see the old .cf files I used to have. your *custom* configs belongs to /etc/mail/spamassassin/ and not /usr/share/ or /var/lib/ the with sa-update maintained rules (hence you must not touch them) are below /var/lib/spamassassin/3.004000/ at least on my setups signature.asc Description: OpenPGP digital signature
Re: Confused by new version of spamassassin
On 11/25/2014 11:31 AM, Paul Gardiner wrote: On 25/11/2014 09:57, Reindl Harald wrote: Am 25.11.2014 um 10:40 schrieb Paul Gardiner: I drive spamassassin using spampd. I've just swapped from using opensuse 13.1 to 13.2. That's taken me from spamassassin 3.3.2 to 3.4.0. I have two confusing changes. 1) The really problematic one is that I no longer see X-Spam-Level and X-Spam-Status headers in the processed mail. I do still have X-Spam-Checker-Version. I was using status to trigger rejection, so now effectively I have no filtering. 2) The confusing one: I used to have many .cf files in /usr/share/spamassassin/. I now have none you need to call sa-update after a version change since the rules are always below a versioned folder Thanks for the suggestion, but it doesn't looked to have helped. sa-update ran without error, but problem 1 persists, and I still don't see the old .cf files I used to have. use locate or spamassassin --lint -D rules that shows where the files are being loaded from
Re: Confused by new version of spamassassin
On 25/11/2014 10:37, Reindl Harald wrote: Am 25.11.2014 um 11:31 schrieb Paul Gardiner: On 25/11/2014 09:57, Reindl Harald wrote: Am 25.11.2014 um 10:40 schrieb Paul Gardiner: I drive spamassassin using spampd. I've just swapped from using opensuse 13.1 to 13.2. That's taken me from spamassassin 3.3.2 to 3.4.0. I have two confusing changes. 1) The really problematic one is that I no longer see X-Spam-Level and X-Spam-Status headers in the processed mail. I do still have X-Spam-Checker-Version. I was using status to trigger rejection, so now effectively I have no filtering. 2) The confusing one: I used to have many .cf files in /usr/share/spamassassin/. I now have none you need to call sa-update after a version change since the rules are always below a versioned folder Thanks for the suggestion, but it doesn't looked to have helped. sa-update ran without error, but problem 1 persists, and I still don't see the old .cf files I used to have. your *custom* configs belongs to /etc/mail/spamassassin/ and not /usr/share/ or /var/lib/ the with sa-update maintained rules (hence you must not touch them) are below /var/lib/spamassassin/3.004000/ at least on my setups Yeah, I see them now. Thanks (also to Axb). Ok that explains my confusion there. Any thoughts on problem 1 (i.e., that I no longer have a X-Spam-Status line in the processed email)? That's the one that is really giving me problems. Is that a config option? Cheers, Paul.
Re: Confused by new version of spamassassin
How are you calling spamassassin? On 25/11/2014 20:53, Paul Gardiner wrote: I drive spamassassin using spampd. I've just swapped from using opensuse 13.1 to 13.2. That's taken me from spamassassin 3.3.2 to 3.4.0. I have two confusing changes. 1) The really problematic one is that I no longer see X-Spam-Level and X-Spam-Status headers in the processed mail. I do still have X-Spam-Checker-Version. I was using status to trigger rejection, so now effectively I have no filtering. 2) The confusing one: I used to have many .cf files in /usr/share/spamassassin/. I now have none
Re: Confused by new version of spamassassin
I'm using spampd as follows: spampd --port=10025 --relayhost=127.0.0.1:25 --user=paul --group=users --homedir=/home/paul/.spamassassin --tagall --children=5 --maxsize=512 --log-rules-hit I may also be using a newer version of spampd than when this previously worked for me. My mail is being passed through spampd. I can see it in the logs and I am getting one header added to my mail (just giving the spamassassin version). On 25/11/2014 11:29, Noel Butler wrote: How are you calling spamassassin? On 25/11/2014 20:53, Paul Gardiner wrote: I drive spamassassin using spampd. I've just swapped from using opensuse 13.1 to 13.2. That's taken me from spamassassin 3.3.2 to 3.4.0. I have two confusing changes. 1) The really problematic one is that I no longer see X-Spam-Level and X-Spam-Status headers in the processed mail. I do still have X-Spam-Checker-Version. I was using status to trigger rejection, so now effectively I have no filtering. 2) The confusing one: I used to have many .cf files in /usr/share/spamassassin/. I now have none
Re: Confused by new version of spamassassin
On 11/25/2014 12:50 PM, Paul Gardiner wrote: I'm using spampd as follows: spampd --port=10025 --relayhost=127.0.0.1:25 --user=paul --group=users --homedir=/home/paul/.spamassassin --tagall --children=5 --maxsize=512 --log-rules-hit This is hardly a SA issue... Suggest you check the spampd docs... http://www.worlddesign.com/Content/rd/mta/spampd/spampd.html I'd bet you're missing options in your command line... I may also be using a newer version of spampd than when this previously worked for me. My mail is being passed through spampd. I can see it in the logs and I am getting one header added to my mail (just giving the spamassassin version). On 25/11/2014 11:29, Noel Butler wrote: How are you calling spamassassin? On 25/11/2014 20:53, Paul Gardiner wrote: I drive spamassassin using spampd. I've just swapped from using opensuse 13.1 to 13.2. That's taken me from spamassassin 3.3.2 to 3.4.0. I have two confusing changes. 1) The really problematic one is that I no longer see X-Spam-Level and X-Spam-Status headers in the processed mail. I do still have X-Spam-Checker-Version. I was using status to trigger rejection, so now effectively I have no filtering. 2) The confusing one: I used to have many .cf files in /usr/share/spamassassin/. I now have none
Re: Confused by new version of spamassassin
On 25/11/2014 12:13, Axb wrote: On 11/25/2014 12:50 PM, Paul Gardiner wrote: I'm using spampd as follows: spampd --port=10025 --relayhost=127.0.0.1:25 --user=paul --group=users --homedir=/home/paul/.spamassassin --tagall --children=5 --maxsize=512 --log-rules-hit This is hardly a SA issue... Suggest you check the spampd docs... http://www.worlddesign.com/Content/rd/mta/spampd/spampd.html I'd bet you're missing options in your command line... Ok thanks. I was thinking you guys produce spampd as well because it was part of the same opensuse package, but I guess it's just the packager put them together for convenience. Thanks for your time. It helps a lot just to know that the change of spampd version is the more likely cause of my problems. Probably spampd has become more configurable and as you say I need another option on the command line, although I didn't before. Cheers, Paul.
Re: Confused by new version of spamassassin
On 25/11/2014 12:39, Paul Gardiner wrote: On 25/11/2014 12:13, Axb wrote: On 11/25/2014 12:50 PM, Paul Gardiner wrote: I'm using spampd as follows: spampd --port=10025 --relayhost=127.0.0.1:25 --user=paul --group=users --homedir=/home/paul/.spamassassin --tagall --children=5 --maxsize=512 --log-rules-hit This is hardly a SA issue... Suggest you check the spampd docs... http://www.worlddesign.com/Content/rd/mta/spampd/spampd.html I'd bet you're missing options in your command line... Ok thanks. I was thinking you guys produce spampd as well because it was part of the same opensuse package, but I guess it's just the packager put them together for convenience. Thanks for your time. It helps a lot just to know that the change of spampd version is the more likely cause of my problems. Probably spampd has become more configurable and as you say I need another option on the command line, although I didn't before. Actually, just so that I'm sure of what you are saying: is that it is spampd's responsibility to add X-Spam-Status that I'm now not seeing or is it spamassassin's responsibility, but spampd is not requesting it, or is maybe suppressing it in some way. Cheers, Paul.
Re: Confused by new version of spamassassin
2014-11-25 13:52, Paul Gardiner wrote: On 25/11/2014 12:39, Paul Gardiner wrote: On 25/11/2014 12:13, Axb wrote: On 11/25/2014 12:50 PM, Paul Gardiner wrote: I'm using spampd as follows: spampd --port=10025 --relayhost=127.0.0.1:25 --user=paul --group=users --homedir=/home/paul/.spamassassin --tagall --children=5 --maxsize=512 --log-rules-hit This is hardly a SA issue... Suggest you check the spampd docs... http://www.worlddesign.com/Content/rd/mta/spampd/spampd.html I'd bet you're missing options in your command line... Ok thanks. I was thinking you guys produce spampd as well because it was part of the same opensuse package, but I guess it's just the packager put them together for convenience. Thanks for your time. It helps a lot just to know that the change of spampd version is the more likely cause of my problems. Probably spampd has become more configurable and as you say I need another option on the command line, although I didn't before. Actually, just so that I'm sure of what you are saying: is that it is spampd's responsibility to add X-Spam-Status that I'm now not seeing or is it spamassassin's responsibility, but spampd is not requesting it, or is maybe suppressing it in some way. Glancing at its code, spampd pulls a rewritten message from SpamAssassin, which should include the X-Spam-Status header field by default. The X-Spam-Status in this setup is added by the rule: add_header all Status _YESNO_, score=_SCORE_ required=_REQD_ tests=_TESTS_ autolearn=_AUTOLEARN_ version=_VERSION_ in a default SpamAssassin config file 10_default_prefs.cf. The 'add_header' option can be overruled by your local configuration (by a 'clear_headers') option. Missing 10_default_prefs.cf would have the same effect (like being installed in a directory where SpamAssassin/spampd isn't using), so make sure the spampd is configuring SpamAssassin to use correct directories for rules. Mark
Re: Confused by new version of spamassassin
On 25/11/2014 13:09, Mark Martinec wrote: 2014-11-25 13:52, Paul Gardiner wrote: On 25/11/2014 12:39, Paul Gardiner wrote: On 25/11/2014 12:13, Axb wrote: On 11/25/2014 12:50 PM, Paul Gardiner wrote: I'm using spampd as follows: spampd --port=10025 --relayhost=127.0.0.1:25 --user=paul --group=users --homedir=/home/paul/.spamassassin --tagall --children=5 --maxsize=512 --log-rules-hit This is hardly a SA issue... Suggest you check the spampd docs... http://www.worlddesign.com/Content/rd/mta/spampd/spampd.html I'd bet you're missing options in your command line... Ok thanks. I was thinking you guys produce spampd as well because it was part of the same opensuse package, but I guess it's just the packager put them together for convenience. Thanks for your time. It helps a lot just to know that the change of spampd version is the more likely cause of my problems. Probably spampd has become more configurable and as you say I need another option on the command line, although I didn't before. Actually, just so that I'm sure of what you are saying: is that it is spampd's responsibility to add X-Spam-Status that I'm now not seeing or is it spamassassin's responsibility, but spampd is not requesting it, or is maybe suppressing it in some way. Glancing at its code, spampd pulls a rewritten message from SpamAssassin, which should include the X-Spam-Status header field by default. The X-Spam-Status in this setup is added by the rule: add_header all Status _YESNO_, score=_SCORE_ required=_REQD_ tests=_TESTS_ autolearn=_AUTOLEARN_ version=_VERSION_ in a default SpamAssassin config file 10_default_prefs.cf. The 'add_header' option can be overruled by your local configuration (by a 'clear_headers') option. Missing 10_default_prefs.cf would have the same effect (like being installed in a directory where SpamAssassin/spampd isn't using), so make sure the spampd is configuring SpamAssassin to use correct directories for rules. That rule is present, and the problem is definitely with spampd because I just piped a message through spamassassin from the command line and all the headers were added. Struggling to see how spampd is messing it up though. I can't see anywhere that it sets or overrides the rules directory. I'm sort of surprised that's even possible. Cheers, Paul.
Re: Confused by new version of spamassassin
Am 25.11.2014 um 15:22 schrieb Paul Gardiner:
That rule is present, and the problem is definitely with spampd
because I just piped a message through spamassassin from the command
line and all the headers were added. Struggling to see how spampd
is messing it up though. I can't see anywhere that it sets or
overrides the rules directory. I'm sort of surprised that's even
possible.
check all permissions and under what user it is running!
i added ExecStartPre to make sure before spamd is started all rules
are wolrd readable because repeatly after sa-update a parent folder was
not readable for the sa-milt user
[Service]
Environment=TMPDIR=/tmp
PermissionsStartOnly=true
ExecStartPre=/usr/bin/find /var/lib/spamassassin/ -type d -exec
/bin/chmod 0755 {} \;
ExecStartPre=/usr/bin/find /var/lib/spamassassin/ -type f -exec
/bin/chmod 0644 {} \;
ExecStart=/usr/bin/spamd -c -H --max-children=25 --min-children=10
--min-spare=5 --max-spare=15 --port=10028
ExecReload=/usr/bin/kill -HUP $MAINPID
Environment=LANG=en_GB.UTF-8
User=sa-milt
Group=sa-milt
Nice=15
StandardOutput=null
StandardError=null
SyslogFacility=mail
Restart=always
RestartSec=1
signature.asc
Description: OpenPGP digital signature
Re: Confused by new version of spamassassin
On 25/11/2014 14:58, Reindl Harald wrote: Am 25.11.2014 um 15:22 schrieb Paul Gardiner: That rule is present, and the problem is definitely with spampd because I just piped a message through spamassassin from the command line and all the headers were added. Struggling to see how spampd is messing it up though. I can't see anywhere that it sets or overrides the rules directory. I'm sort of surprised that's even possible. check all permissions and under what user it is running! Thanks for the suggestion, but that doesn't seem to be the cause in my case.
Re: Confused by new version of spamassassin
On 25/11/2014 09:57, Reindl Harald wrote: Am 25.11.2014 um 10:40 schrieb Paul Gardiner: I drive spamassassin using spampd. I've just swapped from using opensuse 13.1 to 13.2. That's taken me from spamassassin 3.3.2 to 3.4.0. I have two confusing changes. 1) The really problematic one is that I no longer see X-Spam-Level and X-Spam-Status headers in the processed mail. I do still have X-Spam-Checker-Version. I was using status to trigger rejection, so now effectively I have no filtering. 2) The confusing one: I used to have many .cf files in /usr/share/spamassassin/. I now have none you need to call sa-update after a version change since the rules are always below a versioned folder Gah! That was it. Silly me. I didn't restart spampd after the update. At least, I assume that's it because I just restarted spampd and it has all magically started working again. Thanks again everyone for all your help. Cheers, Paul. I'm still a little unsure as to why sa-update hadn't been called before. I seem to have a daily cron job that is supposed to call it, but still I do at least have filtering now.
